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-arm in repository toolchain/ci/base-artifacts.

discards 08f60e6c604 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 1f08d4cbb3b 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards e6adc707ddb 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards d41676000af 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 9b29085c40a 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 08dd9c0f12a 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards cabc2a86e3d 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 1d9d11cf787 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 0b5372159a5 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards dfa9dd72614 213: force: #24: 1: Success after binutils: 2 commits discards ab04ca8a516 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 759ec01ad7b 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 091f2f99d40 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 0712680f46f 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards c5b546f311a 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards b7b128b0555 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards f2b352d615a 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 9783ea9dce1 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 3db8a712e9a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards df895c58edf 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 9b930d3db0c 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards b6b447c2a0f 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 691243284b8 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 60a0182967a 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards cbe89cb88f0 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards f8aa72d09e3 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards ce14ce09c21 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 3773945b4bf 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards ed0824b3714 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards c9e59029167 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 40b8a4f6295 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 93bb28ab77c 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 88eed3f7712 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards e94a1172c75 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 239457b96ce 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 1330428cf73 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 2440c9f8dd0 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 26260d29267 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 9a1b71ebd4e 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 5c2fd9d0f13 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards e55033fdd7a 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 23bf08464a7 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards bb81cce30db 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 3810245df9d 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 65745f2a93b 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 2113090bced 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 9fc9507143c 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards aa1de8d372e 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 79d773e140d 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards a2423dbcdae 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 904ffac2406 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards f95333f00e6 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards dc953d0ad90 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 28ed8528d59 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards 42b847f0b53 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 4340f0967f1 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards c102c6ba9c6 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards d7d785cd3fc 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 1acb79c926f 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 59aed8c4eda 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 6521e172dc4 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 4e92d8663e0 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 09bfcdd57d9 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 435dd5bb4db 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards f7f0ae60846 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards a37c6a4b517 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 63053ad6467 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 9708880603e 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 80393dbad5f 154: onsuccess: #583: 1: Success after linux: 10 commits discards 1dd21f97b58 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 77eec787681 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 30dfabda209 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 9d7cf3dbcf5 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 5d75e5a369e 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards ed367d697dd 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 2d81dc4e90f 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 5cdc50b9159 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards a2a8c5ca30e 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards c39f4b3efbd 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 1a5e24621da 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 1155aa9d555 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards c9ff0fb4f8a 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards 3529959db1b 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards c17a1a2fa69 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards a5025355670 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 5d651f6817c 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards b09d9c841b6 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards ec64951a99c 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards c848c94a621 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards b25e96be598 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards d836dfbd113 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards f4e35278848 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 339d899f51b 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 3b09d9668c4 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 0e5e5ed22a7 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 71475966f94 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 8e42dadbfae 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 2ad302b56e2 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 4c81558ab81 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 72a9788faa5 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards fee64090761 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 4c9cc932922 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 0668065cb28 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 23647290b07 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 2834049b3ab 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 013a5b890b8 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 672f792b587 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 07160585463 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new a09f618083f 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 4a44d6a37e6 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 2933226f838 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new 02786792005 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 692b70af525 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 5f848c372e6 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 52f4b5ca218 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new e5f27bedcf9 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new 21be797c55e 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 24ab0087545 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new d92534d25b2 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 0a5c393a572 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 07b3bc7eb84 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new e93021cf7ee 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new 5127bd6c027 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 346c61c64c7 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new 13402546c23 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new a773d7d380a 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 7c475f14474 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 2c23563dbca 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new f9d3f2502ba 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new eed03bc0b9c 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 7ac4db277e0 151: onsuccess: #579: 1: Success after binutils: 21 commits new c22841ccfd8 152: onsuccess: #580: 1: Success after gcc: 6 commits new 3cda7542bae 153: onsuccess: #582: 1: Success after glibc: 9 commits new 8c9093373c4 154: onsuccess: #583: 1: Success after linux: 10 commits new bdae1ecae35 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new de508a73476 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new a667ce39fdb 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new c6b55ad2ad9 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 57a64c1c538 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new aacea6428c0 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new bece5555eed 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 0ba063e4657 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 78c010cbb84 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new d910196ba4b 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 31adc5dd73e 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new ee8cfe47f4a 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 573504e6923 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 10fd75113df 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new c64524b0b26 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new 8d582963588 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 3467607ea1d 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 44c09d4b046 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new acf2b9582bf 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 1e617cf27e7 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 8571f065f6c 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 5aa31bda826 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new e2790c8c6b9 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 37d5d4b43a7 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 9534f33546e 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 2cb5ed2d536 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 73e5cddae2a 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 32f431af4fb 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 2ab3cf0352a 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new 01506c42583 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 0f569368f48 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 2b4d6cb2739 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 5521be91a13 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 70e011a7b51 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 0b27b22f631 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 4605876647e 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new cdfba5f6117 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 6baf49253ae 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 6a4f4c96446 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new b3da2da63cc 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 72666dd60f7 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new ad57eb7c3c3 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new c50309ec710 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new d5e8af8c846 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 62021b58b8f 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 1572bcea162 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 19342c8a6f0 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 117b4d00f31 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 6b877b66a17 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 4932faf0dd5 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 775c706ebf7 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 698557bfe8a 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 97ecd7f9848 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 35187d2bf3a 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new fd1ef5fd68c 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 84b72fb7f43 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 152dff81384 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 4896a6d75e6 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 220cefe553f 213: force: #24: 1: Success after binutils: 2 commits new 3c6b9840309 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 94daede4c58 215: onsuccess: #26: 1: Success after binutils: 10 commits new a3a1d9ba5fe 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 586d22fe7d1 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 7923797783a 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new bd4c30c3181 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 8ab46266780 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new 35025b59233 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new 06ecf44f3f0 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new 4626d16f738 223: onsuccess: #35: 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 (08f60e6c604) \ 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 2068 -> 2040 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 49012 -> 48896 bytes 04-build_abe-gcc/console.log.xz | Bin 235364 -> 236096 bytes 06-build_abe-linux/console.log.xz | Bin 8424 -> 8880 bytes 07-build_abe-glibc/console.log.xz | Bin 232916 -> 232504 bytes 08-build_abe-gdb/console.log.xz | Bin 47276 -> 47108 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3824 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2108 -> 2112 bytes 11-check_regression/console.log.xz | Bin 4816 -> 4776 bytes 11-check_regression/jira-body.txt | 1 - 11-check_regression/mail-body.txt | 2 +- 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 4 +- 12-update_baseline/console.log | 68 ++++++++++++++--------------- 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 | 1 - mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++-------- sumfiles/binutils.log.xz | Bin 62388 -> 62848 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100612 -> 100604 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 132236 -> 132200 bytes sumfiles/ld.sum | 4 +- 30 files changed, 68 insertions(+), 70 deletions(-) delete mode 100644 11-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt