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 3b22680a8b 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 787810f7e9 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards bb93255b7e 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 9b56920c33 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 54853b1f76 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards f10cc2ebfd 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d23a270f86 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards db96c4c850 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards 781060aded 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards ce0cf31489 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards c6f9ea49d0 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards bdba1a34e3 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards 7a2a23e986 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards c31d1a66e1 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 66e8f934db 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards deb55763b3 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 441ee2e8eb 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards bfdcbee50e 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards ab23c8b058 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 543eae9725 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 4e3657caf8 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 6e32405ceb 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 78dd74651c 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards ed5cdca2ef 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 00a1371302 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards 4295540714 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 871b33b18b 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 0d9d99efc7 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards bba96cd0ef 127: force: #27: : Failure after baseline build: no new commits discards 4e88ed7485 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 1fee0dda4e 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards d083b009a2 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards e47ad6fa77 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards a69c13956e 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 04ebc0dc7c 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards f47a7bac69 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards dbb0b32245 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 7171dfa583 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 8b593e6ad7 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards c501165294 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 9a760b2e0e 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 4f5b7af083 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 8b9890124f 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 558ed251e0 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 7a8371153d 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 3b4e35c273 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 46867f819e 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards b7e9dd8cb3 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 43bde4adba 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards fd1aa3ad6b 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards 238456e2ac 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 1fd30647b5 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards a7a08f80d4 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards cef4f57c46 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 99b5de7151 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards ecd735c43c 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 6d8187dd59 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 2d72b594a8 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards d77ca16f99 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards d5fa1b195f 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 2b40aa2a11 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards c7061a2a2d 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 6f6f9763f5 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards a15f0c1b87 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards 562f60d14c 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 9be3c8d91d 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 0525b8af1d 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards 889e2a58ca 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 8935c03f6a 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards b9d10954b0 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 6f30745cd2 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards edca9b948c 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 4656f19f60 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 39dd9e8f3a 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards 6a9a17258a 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 2e7aeb6e19 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 454dcfa884 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards c4c443385a 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 05b1b507b7 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards 373654c8ce 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 2ff376f12f 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards e45dfede3e 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 11c77c04d6 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 2b91489146 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 5ab14927b5 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards e4e9e962a5 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards 303ef14f87 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 331e565e69 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards 5359b11468 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 2f2c01b2e6 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards 9eb0deb09c 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards 5ab3f2e51c 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 89bbea0f8a 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 614468d6b0 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards db74053877 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards 41239cb5fd 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards 7aa34b9087 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards 640ccab5fe 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 25778184cb 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 0c7d762ba1 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards b1841a1c15 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new 96479ea407 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new 52745ea31e 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 157fd8cf85 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new e88acbef88 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 98b95a65e0 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new 36de91fa4d 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 00f1f1a303 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new afd17c636d 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 7f73a60c37 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 27b10f9c81 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new 5394fbbe02 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new b99f8337f8 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new 0cc246b876 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new b152ccad18 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new c17ea8cbc4 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 6bcb415830 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new 1e6ba49c94 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 5ab7250c2c 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 25a07b2c6e 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 6000a6edf3 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new e7d2636347 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new 03e1e4f177 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new 3cdc746995 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 3ed811f7b7 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new e68e2b8b68 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 8bc6f1b25e 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 41bc3fe1c1 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 8c57a2e5bc 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new d811150fc6 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 53208d9885 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 480f5960a3 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new 437de53b48 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 5aa6ad7cb8 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new eae76f6a56 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 4aed0f8558 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new 73d6e1c750 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 7e1c4b62cb 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 5e0fe2a06a 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new 130a28157d 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 5af73d1cee 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new e640aacf67 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 066d0075be 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new a6d5a11c0b 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 666586606c 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new ce9177290a 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new c0886bb82f 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 9d2be6d000 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new 7b59e630d4 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new a2266db8fb 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new a9be5a176e 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new 0308df5762 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 47ffad9fce 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new 6c37ddfd60 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 4d8d563c72 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new c5e9951817 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 83c706c4db 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 7e01a2ab78 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new b83db5910e 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 2854340a65 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 0371a8931a 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 880732ed37 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 3002ec5453 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new e1544d76db 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 7265f37b55 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 9b6bbb4981 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new f2ef9661cb 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new ffc5ee220e 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new afaf0dc544 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new a0806db5eb 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new da8177236d 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 8194030617 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new c904d9de0b 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 10c0ddfb76 127: force: #27: : Failure after baseline build: no new commits new 17f7ffa703 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 3f850322cf 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new f41b90fcad 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 7766264f22 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new 93438b9c2a 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new ccd1638ce1 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 8d95d35a57 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new 600b764813 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new b9a844fa99 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 5fed665a44 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 07c603652f 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 03575b6f04 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 8da668b1db 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 77b84c3f3f 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new cfeed4b04f 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new b0ce9dbb18 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 869980f383 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new 13a3ed9b09 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 66aa6cc9a7 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new c72b3fd615 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new c7c43222e5 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new fabc38f055 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new f998a44bb4 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 19daf70a0d 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new bff6587258 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 745157b2bb 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new be400f748f 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 458dd7b102 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new e6642887e2 156: onsuccess: #68: 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 (3b22680a8b) \ 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 2196 -> 2288 bytes 02-prepare_abe/console.log.xz | Bin 2428 -> 2472 bytes 03-build_abe-binutils/console.log.xz | Bin 35828 -> 35488 bytes 04-build_abe-gcc/console.log.xz | Bin 203380 -> 203048 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8288 -> 8548 bytes 07-build_abe-glibc/console.log.xz | Bin 241564 -> 241204 bytes 08-build_abe-gdb/console.log.xz | Bin 35196 -> 34716 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3916 -> 3844 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3760 -> 3196 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 548 -> 1272 bytes 11-check_regression/results.compare | 7 ++++ 11-check_regression/results.compare2 | 42 ++++++++++++++++++++++ 12-update_baseline/console.log | 64 +++++++++++++++++----------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 7 ++++ manifest.sh | 34 +++++++++--------- sumfiles/gdb.log.xz | Bin 14440 -> 14440 bytes sumfiles/gdb.sum | 4 +-- 25 files changed, 114 insertions(+), 58 deletions(-) create mode 100644 11-check_regression/results.compare create mode 100644 11-check_regression/results.compare2 create mode 100644 mail/results.compare