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 f449011b4c6 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 2fff4d463d2 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 931d738cf54 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 85bd1f6478a 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 29f0c75ed2f 212: force: #24: 1: Success after binutils: 2 commits discards ce6809770bd 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards c423d989f6a 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 8ae06ef963a 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards daffc477129 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 2ecc2c6c078 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards fa9074a7aa9 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards f987b629b4d 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 565bcca7aad 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards c845bc4301a 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards b366c1239e0 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards a7433ddcf23 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards fdd6a58ef19 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards ceb7c1e3cd9 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 071a40f8e53 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 0b9cc3ba592 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 96e23bda678 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 40116ddac97 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 39316cc251a 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 720afc686d0 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 0c1272e8f05 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 58fad1c6361 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 4edf23447b8 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards c13beb0a482 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards edd01b48cfd 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards d82e6a41576 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 7e23baa069d 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 6e32ca20af4 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 6f7d97d3117 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 252654c198f 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards dffcbb41b59 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 111acde9af3 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards f20c4a5d724 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards dd710b7627f 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 1e343b6c020 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 795e739f0b6 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards a171caff91d 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards ce898fc2603 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards 77320e6c5fd 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards eab11a33ed1 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards c6e8478f880 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards f5e217144c7 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 4199e09cf0c 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 11eb7700d30 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 4483ddf145d 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards a806ae4b6ff 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 9e9ede05776 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards 1d03142f52c 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 91743060a62 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 033b90367a2 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards d9623fda1d7 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 72a4eed47ab 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards f1a803b6d5a 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 203b04db372 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 05e404020b4 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 32bbaa3ff2f 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards 77c427fdfc5 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 6d6074b3245 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 4ebb71e446e 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 0ea6271083c 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 781c42b2e65 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards 4ee024a6e53 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 6c58167028d 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 87c657bd1a5 149: onsuccess: #684: 1: Success after linux: 10 commits discards 058574d1b9f 148: onsuccess: #683: 1: Success after glibc: 9 commits discards aa26d104b04 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 3d17d636c45 146: onsuccess: #680: 1: Success after binutils: 20 commits discards dbbda113059 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 3c0f639295c 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 3798b6892ec 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards a9289c06d3d 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 45cd974570c 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 74bada3ef7e 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 26c81971263 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 43558d777b5 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 36b9a329344 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 57672e4b1e1 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 19b2460a34c 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 24984ed33a3 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 50b38fd671d 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 14eed913429 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 597dc838e3c 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards dc88882b6e4 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards c2edf3c0df3 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 4454e637cdd 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 5c0f52dafc5 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 4d9b4290a06 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 7e6f4ef30c7 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 75b803ec916 124: onsuccess: #657: 1: Success after glibc: 2 commits discards d44e02968ad 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 9e5f0d37403 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards c287b4460dc 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 55784028e70 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 4e6af8f7435 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 093510d0d63 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 98c412b0f43 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 6a382941ab0 116: onsuccess: #647: 1: Success after linux: 3 commits new 219e681622b 116: onsuccess: #647: 1: Success after linux: 3 commits new ef96c8cf97d 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new b0f972d4e6d 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 9915516ff11 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 01835fb520f 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new aee708bb663 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 7d012b71f8a 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new e65b2ce7ef4 123: onsuccess: #655: 1: Success after binutils: 22 commits new 52281e8c090 124: onsuccess: #657: 1: Success after glibc: 2 commits new af866fc37f5 125: onsuccess: #658: 1: Success after linux: 3224 commits new e3a2bcacd6f 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new d5e6879e7ab 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 6db6c793ecb 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new f87f48cc26d 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 2387e7ece9d 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 3151c019f1a 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 377fe0eabbc 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new ea35e0a1a4f 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 69437c375d1 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 819c92be357 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 4c69af23a49 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new a88627d0897 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new 827a55100c9 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 0c7480450a7 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 0486b8a2d74 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 26cea8c3c8b 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 4b6337d39a4 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 66946f7634e 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 0f6d4bbdf9c 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 940cfd06329 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new 29add306075 146: onsuccess: #680: 1: Success after binutils: 20 commits new 3a173db8930 147: onsuccess: #681: 1: Success after gcc: 6 commits new a226781b670 148: onsuccess: #683: 1: Success after glibc: 9 commits new 1585631af91 149: onsuccess: #684: 1: Success after linux: 10 commits new 63956c691a3 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new 86c0bb03a9e 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 3ba01d58221 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 53aef1da200 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 1839e7aef78 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new d50d4b5362a 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new f43e9481e09 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new c7401599a15 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 393985b1eed 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 2700d713e89 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 1c8f360c26b 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 31316713d13 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 93cbc78b6b1 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new a4c268c9f42 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 72fc56fa006 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 87a810fe608 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new 268ee384c06 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 4f083506b6d 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 1743e2cc443 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 1e938b519d2 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 14ff0da6744 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 3c5e6176312 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new b2f42529ac4 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new f54f84e7a58 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new 7601c2f2176 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new b1b3a38321c 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 8ad42dc07d6 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new e2fe21a22c4 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new f7a79dcd125 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 443e71bdb72 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 810884c6ef6 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 25f8d034fc4 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 52d664fa071 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 46b49397f02 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 3e3af519b5f 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 25aed00ec19 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new e537d4db67c 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new c45a2347da7 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new e92571a37e3 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new 4bf63f121ff 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new b836f1c9cf4 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 17db1c7d1e0 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 55aaaa849b2 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 21fed43a5a5 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new a11f3d05509 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 6fb733f849b 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 8eeb695dcff 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 7e50db61040 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new f21068e2d51 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new b08a9ac19c7 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new eb455fd50b6 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new e29bafaa814 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 3da70713184 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 6c0300a028a 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 6fd351aa5e1 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 28021986832 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new a82fdd6eaf9 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new c755be5d2f2 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new e0c5be9f747 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new c132efc54b8 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new c36f4db8b89 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 7ff51e6703e 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new f112e53e833 212: force: #24: 1: Success after binutils: 2 commits new 480f646c8fa 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new d96378e29c7 214: onsuccess: #26: 1: Success after binutils: 12 commits new 58de53d9774 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new dba39fdb826 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 50d527d5199 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...]

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 (f449011b4c6) \ 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 1748 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 35312 -> 34864 bytes 04-build_abe-gcc/console.log.xz | Bin 203940 -> 202864 bytes 06-build_abe-linux/console.log.xz | Bin 8200 -> 8392 bytes 07-build_abe-glibc/console.log.xz | Bin 242252 -> 241760 bytes 08-build_abe-gdb/console.log.xz | Bin 34916 -> 34492 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3780 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2344 -> 2096 bytes 11-check_regression/console.log.xz | Bin 4816 -> 4732 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 4 +-- 12-update_baseline/console.log | 52 ++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++---------- sumfiles/binutils.log.xz | Bin 62632 -> 62964 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83968 -> 83984 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122464 -> 122500 bytes sumfiles/ld.sum | 4 +-- 28 files changed, 60 insertions(+), 60 deletions(-)