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_check_binutils/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 24c24dfc0e 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 5f9594eb9f 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 51ab3197fb 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 1636b12719 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 4814186244 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 1d7c746190 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards d9340b0c2e 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 8051ea0c4d 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 69594e2523 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 576e577885 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 679c08a755 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 71bb010805 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards ab5c98c988 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 6e06c80341 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards f84bf478f8 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 9aa40467e0 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards ad39f6f308 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards ba73c2aab5 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards f6d27b1ed7 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards e2cd0c0ea4 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 2574c00f99 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards dedf5e186c 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 50f0f4b169 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards a7680c633e 212: force: #24: 1: Success after binutils: 2 commits discards 39411568c5 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards b5e48ce663 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 4023c85818 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 74220b0b70 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards f903d9ff34 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 6d3757dffa 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards ee8cf57058 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 8fb515bd4d 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards cf235d3eae 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards b1314cf83a 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 6cd51a29c2 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards bf389ea298 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards e15f8a32e2 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 98d8ee0c0e 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 434ddb9e25 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards bd32ee9ca2 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 009e698a99 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 8d51c4e24e 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 78bf0e405e 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 329ed444b8 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards a4637598a2 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 065c5ad4ff 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards 98490eec25 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards 6dd8e84bbf 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 3c442a8305 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards 39ae7bfb70 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards 04b33f584b 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards a284204e09 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards 23b4e45a41 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards 12c8ff2545 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards 07ec11c3c4 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 108f7a1599 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards 85e4ace65d 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards 7b9af1a163 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards df76ff4450 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards c32c5cf7c7 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards 4063258417 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards 1dd1df7898 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards c29910b3ea 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards 473f467884 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards 8b54380c1a 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards 8f1642b9d5 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards baf1384bb7 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards 365c72775b 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards 6e6e5d22da 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards e55dd74475 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards cb77e6b621 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards 83a68efcea 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards c1ee38208e 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards 6be5d22292 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards 1d4b00b1a8 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards 8321381eab 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards ef2336fccb 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards 18c0972c30 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards b1a0148d99 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards cbc5b3c84e 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 9c7031bf66 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards afa06c120c 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards 8417802626 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards d0b72f29db 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards e0596ec056 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards ec4fe24b13 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards b9c5c71865 149: onsuccess: #684: 1: Success after linux: 10 commits discards 09eb0de98b 148: onsuccess: #683: 1: Success after glibc: 9 commits discards bc9d4afc61 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 41f7112f4b 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 6318ff6591 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards 7b19fb4512 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards db57f7ac3b 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 6fc185780e 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards d4bd6b71c3 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards be361f010d 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards df3aee080a 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards 186ce70ad6 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards f67080ef01 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards d307019b1f 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 09ee7943f0 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new fc7cc85ba4 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new e1e1c152a3 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new c06352fb3d 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new a65327ce82 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new f05f94eec8 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 4c319ab127 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new 6b9fe71de6 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new c12d3ff642 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 0e973f11b9 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new ea64eb35db 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 70fe859fa2 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new 2eef105e5f 146: onsuccess: #680: 1: Success after binutils: 20 commits new deb4a257f8 147: onsuccess: #681: 1: Success after gcc: 6 commits new 4ed1a0021c 148: onsuccess: #683: 1: Success after glibc: 9 commits new 0b2050186d 149: onsuccess: #684: 1: Success after linux: 10 commits new eac3faa33e 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new 486649266e 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new 5d97ea730a 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 232ae8acce 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new bdb6296152 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 499bd50457 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new 759057d2be 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new df7cf33956 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new b2c469a1bb 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new c23dab6e7d 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new b23e3f8044 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new 632ba4f534 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new 886711c380 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new 39ee74a07f 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new 9654234ec4 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new b9bb0a14ef 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new bf20a91352 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new 37e30c7b35 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new 26d9ca635d 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new 3b5c038135 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new cda5cfb59b 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new d65e0918d5 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new 5b6943146d 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new c10dd0e3df 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new 3e1274eb2a 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new 3070399db5 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new b30d2be1db 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new 94dc412c10 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new 974ad2f935 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new 251d91cfad 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 1b10154b72 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new 99e459642d 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new 993cf8d74a 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new b9e487231e 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new 8652142a6a 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new c6f923498a 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 18e57d036a 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new 7cf44f2035 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new 6394d3a57d 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new 0a86654243 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new f573dc2b79 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new eb53ba66ed 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new fe17cebc27 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 685f8fc2ed 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 47b218c06e 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 636ba9f0ce 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new d0baf564c9 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new b27e1506c1 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new bcacd35fe8 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 47a2fdfc2c 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new afb6b0611a 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new c6e25aa6ce 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new d9579300f0 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 2cbb211665 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 62b32b0202 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 317fbc700a 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new b2726c447c 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new bc8a2be263 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 866c9edcca 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 811b89577a 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 8f0019c4c6 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new a5f45cbb59 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 98ece758f8 212: force: #24: 1: Success after binutils: 2 commits new 31c9929e9f 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new a5bd7ffe1b 214: onsuccess: #26: 1: Success after binutils: 12 commits new 13b95ad87b 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 73de99aba6 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new c049589fbb 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 932b295415 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 90bc9e1b3e 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new e040b4f72e 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new a5046c0889 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 45a94e9650 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 5ff944b468 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 2c8fc44b52 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 1b1653998b 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 9bddb0c7a0 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 196e1c7940 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 10474bbe1a 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new bbf7752d99 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new bef36ec874 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 1c1a80f95d 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 5626579092 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new df5789f70d 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 9302b6bec5 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 340a4c53dc 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new c080d761f7 236: onsuccess: #53: 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 (24c24dfc0e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...]
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 2056 -> 2228 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2488 bytes 03-build_abe-binutils/console.log.xz | Bin 35020 -> 35516 bytes 04-build_abe-gcc/console.log.xz | Bin 203444 -> 203716 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8808 -> 8584 bytes 07-build_abe-glibc/console.log.xz | Bin 240840 -> 241260 bytes 08-build_abe-gdb/console.log.xz | Bin 34780 -> 35168 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3872 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2164 -> 2712 bytes 11-check_regression/console.log.xz | Bin 4764 -> 1980 bytes 11-check_regression/results.compare | 10 +++---- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 44 ++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 3 ++ mail/changes-list-long.txt | 22 --------------- mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 34 ---------------------- mail/short-diag.txt | 1 - manifest.sh | 40 +++++++++++++------------- sumfiles/binutils.log.xz | Bin 62644 -> 62896 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 151136 -> 150736 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122680 -> 122648 bytes sumfiles/ld.sum | 4 +-- 33 files changed, 66 insertions(+), 118 deletions(-) create mode 100755 jenkins/notify.sh delete mode 100644 mail/changes-list-long.txt delete mode 100644 mail/changes-list-short.txt create mode 100644 mail/check-regression-status.txt delete mode 100644 mail/last_good.sh delete mode 100644 mail/short-diag.txt