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 71e6100893 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 229f26600a 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 021e47ca4d 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards c7d54d9605 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards f84ef61dd9 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 7e5e9bf38d 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards c14415c231 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 9ee92e712d 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards d770a714f3 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 9c481ffa82 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards b33e45053a 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 1b038df1c2 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 09ded43ca6 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards a520c167d5 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 4df74dbb8d 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 75ac4895e6 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards fdad228d2d 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards b3c9f19106 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 73a94fc0b0 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 60cbac2ed6 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 288728e749 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 92c3f12ddd 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards fcac3ec321 212: force: #24: 1: Success after binutils: 2 commits discards 3c926352d3 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 1a1703f6e9 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 8279a8f572 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 7300c6649b 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 81daf39637 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 30c667a8c7 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 222535023c 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 567e87da45 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards a1de534faf 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 338345dda2 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 4e65e185e3 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards bcd38e9926 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards f677eb1e28 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards fd3452af6b 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards a3ad283aea 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 2670bf60dd 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards e07e7072d0 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 983e8ba0bf 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards b31011f99c 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 554eb2d7fc 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 16853e785a 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 1737c54d9b 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards a7ff15aa5d 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards 36cb9464d3 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 7609459d55 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards 726a6bab5d 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards 3f114c0091 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards 9771d40812 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards 57ed24eb30 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards c344cbffce 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards bbeac33a39 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 5cbee6e9f8 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards 206bcd0faf 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards 1a47deca55 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards 37fc376a39 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards 2d2005ce69 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards 7844f631d4 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards 524646a565 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards 5f21c74d6a 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards c2e32796ff 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards aab7abb49d 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards abb3dbbbe7 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards d3aca0252e 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards edbf9f6d15 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards 36c8fd75ae 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards 177bf1aebf 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards cef6187cc7 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards d12ff2ee7d 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards 2348da3e62 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards 7ff1603441 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards add85d3e73 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards c78e30963a 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards ae4b55a761 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards acdabc632e 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 958a12c756 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards f2db3a38f5 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards 3922444950 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards fb1dd3785d 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards fd94f10d8d 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards e012adbb91 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards 32f4f645fc 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards 7ba30ebbb8 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards 6f025eded7 149: onsuccess: #684: 1: Success after linux: 10 commits discards afe064de43 148: onsuccess: #683: 1: Success after glibc: 9 commits discards eb5821b6c3 147: onsuccess: #681: 1: Success after gcc: 6 commits discards e9cc97cd33 146: onsuccess: #680: 1: Success after binutils: 20 commits discards d126ee297d 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards 76c4628e80 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 047908f089 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 17c510591c 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 5026006869 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards 904461f0a6 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards d26177f8ea 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards 5c27634e5a 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards 03c2e78815 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards 4ca7c133f9 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 258830793a 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards a273cdd4ca 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new 8cfe511f24 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new 09ee7943f0 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new d307019b1f 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new f67080ef01 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new 186ce70ad6 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new df3aee080a 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new be361f010d 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new d4bd6b71c3 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 6fc185780e 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new db57f7ac3b 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new 7b19fb4512 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 6318ff6591 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new 41f7112f4b 146: onsuccess: #680: 1: Success after binutils: 20 commits new bc9d4afc61 147: onsuccess: #681: 1: Success after gcc: 6 commits new 09eb0de98b 148: onsuccess: #683: 1: Success after glibc: 9 commits new b9c5c71865 149: onsuccess: #684: 1: Success after linux: 10 commits new ec4fe24b13 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new e0596ec056 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new d0b72f29db 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 8417802626 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new afa06c120c 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new 9c7031bf66 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new cbc5b3c84e 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new b1a0148d99 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new 18c0972c30 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new ef2336fccb 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new 8321381eab 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new 1d4b00b1a8 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new 6be5d22292 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new c1ee38208e 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new 83a68efcea 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new cb77e6b621 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new e55dd74475 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new 6e6e5d22da 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new 365c72775b 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new baf1384bb7 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new 8f1642b9d5 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 8b54380c1a 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new 473f467884 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new c29910b3ea 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new 1dd1df7898 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new 4063258417 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new c32c5cf7c7 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new df76ff4450 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new 7b9af1a163 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new 85e4ace65d 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new 108f7a1599 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new 07ec11c3c4 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new 12c8ff2545 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new 23b4e45a41 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new a284204e09 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new 04b33f584b 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 39ae7bfb70 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new 3c442a8305 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new 6dd8e84bbf 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new 98490eec25 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new 065c5ad4ff 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new a4637598a2 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 329ed444b8 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 78bf0e405e 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 8d51c4e24e 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 009e698a99 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new bd32ee9ca2 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 434ddb9e25 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 98d8ee0c0e 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new e15f8a32e2 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new bf389ea298 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 6cd51a29c2 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new b1314cf83a 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new cf235d3eae 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 8fb515bd4d 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new ee8cf57058 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 6d3757dffa 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new f903d9ff34 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 74220b0b70 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 4023c85818 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new b5e48ce663 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 39411568c5 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new a7680c633e 212: force: #24: 1: Success after binutils: 2 commits new 50f0f4b169 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new dedf5e186c 214: onsuccess: #26: 1: Success after binutils: 12 commits new 2574c00f99 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new e2cd0c0ea4 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new f6d27b1ed7 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new ba73c2aab5 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new ad39f6f308 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 9aa40467e0 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new f84bf478f8 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 6e06c80341 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new ab5c98c988 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 71bb010805 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 679c08a755 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 576e577885 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 69594e2523 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 8051ea0c4d 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new d9340b0c2e 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 1d7c746190 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 4814186244 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 1636b12719 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 51ab3197fb 233: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 5f9594eb9f 234: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 24c24dfc0e 235: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...]
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 (71e6100893) \ 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 2228 -> 2056 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 35104 -> 35020 bytes 04-build_abe-gcc/console.log.xz | Bin 203348 -> 203444 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8280 -> 8808 bytes 07-build_abe-glibc/console.log.xz | Bin 240552 -> 240840 bytes 08-build_abe-gdb/console.log.xz | Bin 34704 -> 34780 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3852 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2300 -> 2164 bytes 11-check_regression/console.log.xz | Bin 4360 -> 4764 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 +- mail/changes-list-long.txt | 36 +++++++++++++---------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 ++++++++++----------- manifest.sh | 38 ++++++++++++------------- sumfiles/binutils.log.xz | Bin 63144 -> 62644 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150832 -> 151136 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122620 -> 122680 bytes sumfiles/ld.sum | 4 +-- 30 files changed, 98 insertions(+), 92 deletions(-)