This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts.
discards e6642887e2 156: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 458dd7b102 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards be400f748f 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 745157b2bb 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards bff6587258 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 19daf70a0d 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards f998a44bb4 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards fabc38f055 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c7c43222e5 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards c72b3fd615 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 66aa6cc9a7 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 13a3ed9b09 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 869980f383 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards b0ce9dbb18 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards cfeed4b04f 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 77b84c3f3f 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 8da668b1db 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 03575b6f04 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 07c603652f 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 5fed665a44 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards b9a844fa99 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 600b764813 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 8d95d35a57 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards ccd1638ce1 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 93438b9c2a 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 7766264f22 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards f41b90fcad 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 3f850322cf 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 17f7ffa703 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 10c0ddfb76 127: force: #27: : Failure after baseline build: no new commits discards c904d9de0b 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 8194030617 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards da8177236d 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards a0806db5eb 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards afaf0dc544 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards ffc5ee220e 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards f2ef9661cb 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 9b6bbb4981 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 7265f37b55 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards e1544d76db 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 3002ec5453 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 880732ed37 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 0371a8931a 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 2854340a65 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards b83db5910e 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 7e01a2ab78 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 83c706c4db 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards c5e9951817 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 4d8d563c72 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 6c37ddfd60 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 47ffad9fce 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards 0308df5762 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards a9be5a176e 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards a2266db8fb 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards 7b59e630d4 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 9d2be6d000 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards c0886bb82f 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards ce9177290a 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 666586606c 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards a6d5a11c0b 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards 066d0075be 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards e640aacf67 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards 5af73d1cee 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 130a28157d 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 5e0fe2a06a 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards 7e1c4b62cb 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 73d6e1c750 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 4aed0f8558 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards eae76f6a56 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 5aa6ad7cb8 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 437de53b48 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 480f5960a3 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 53208d9885 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards d811150fc6 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 8c57a2e5bc 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards 41bc3fe1c1 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 8bc6f1b25e 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards e68e2b8b68 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 3ed811f7b7 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 3cdc746995 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards 03e1e4f177 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards e7d2636347 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards 6000a6edf3 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 25a07b2c6e 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 5ab7250c2c 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 1e6ba49c94 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards 6bcb415830 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards c17ea8cbc4 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards b152ccad18 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards 0cc246b876 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards b99f8337f8 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards 5394fbbe02 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards 27b10f9c81 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 7f73a60c37 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards afd17c636d 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 00f1f1a303 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards 36de91fa4d 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards 98b95a65e0 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards e88acbef88 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 157fd8cf85 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 52745ea31e 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 50cc070981 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new b27c57c35b 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 84247627e2 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 81ce7c29bd 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new 824b0fb5f4 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 860e32f6b9 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new 14ec7d4d4b 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 63c11a3d0e 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new b08a259bc7 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new 6c957bd299 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new 3fe0ba0fa1 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new 11e65685b0 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 83ccfbdba2 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 34a67fefae 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 04c348e56d 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new 22d0b2db9a 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new bc3aedfa48 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 39fe987515 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 5293793d2e 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 26405019db 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new 044a68dac4 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new a1113e7fbe 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 3733ae46c7 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new d49dae964e 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new a9cafcef93 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new ce65a516d5 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 3dd4c171c4 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 5b41eac842 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 6a22bef658 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 63f2cf509a 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new 2fe94d9002 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new dcad555cc3 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 9f1cd343b8 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 9822dd7074 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new 415883f9d6 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 671f46f1a1 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new e7dad896f1 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new ae5c47cdac 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 94c7aa8e39 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 9d0d24c15a 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new c4277365de 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new be3637b4ed 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new ff14f2ee9f 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new d4e6d42624 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new 2b116172d6 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 5641c1942c 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new a803fe2238 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new c418700408 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new ea47594c35 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new 1600dd552a 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new df2a671cc3 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new 81ae9f4f74 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 46ec3bfb6e 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new cc4867516a 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new c50e6bd015 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 0af76677fb 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 19971e4295 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new b8322bca1a 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 18631e20c9 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 1e56b88f11 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 5ab0458295 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 1930812bd4 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 2f194aa76f 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new ac2d12a11d 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 2f8f8cd364 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 32e452c916 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new cc2703097b 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 9073753eea 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new e2705604f4 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new aad54bd9fb 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 5d09ac5e9e 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new ce46f409ab 127: force: #27: : Failure after baseline build: no new commits new c14ea84c3e 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 79eb1347f0 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 166620149c 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 49acbed38f 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new 95ab6b2e13 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new af023365af 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 0c81b24697 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new aa2e70b17f 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new b0f2d88663 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 444a561b98 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new c8ce71449b 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 002972b9a9 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new d2fa4ab96d 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 945d60f953 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 097332713a 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 21c5a31896 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new a37ca7d8b0 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new 9b977533e6 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new b6c54ccaf1 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new f3c15a4b8d 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 6faec1fc17 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new ceec3014c7 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 635e868c6a 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 0d27253812 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 604cbb2c99 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 085ee88eb1 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 508a70f4d4 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 7987962a28 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 95b5f0bb8e 156: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 7a4d2f19a8 157: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...]
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (e6642887e2) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...]
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2288 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2472 -> 2404 bytes 03-build_abe-binutils/console.log.xz | Bin 35488 -> 35612 bytes 04-build_abe-gcc/console.log.xz | Bin 203048 -> 204032 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8548 -> 8660 bytes 07-build_abe-glibc/console.log.xz | Bin 241204 -> 242564 bytes 08-build_abe-gdb/console.log.xz | Bin 34716 -> 34936 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3868 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3196 -> 3324 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1272 -> 1196 bytes 11-check_regression/results.compare | 8 ++--- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 64 +++++++++++++++++----------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 ++--- manifest.sh | 27 +++++++------- results | 2 +- sumfiles/gdb.log.xz | Bin 14440 -> 14432 bytes sumfiles/gdb.sum | 4 +-- sumfiles/xfails.xfail | 2 ++ 24 files changed, 62 insertions(+), 67 deletions(-)