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 4626d16f738 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards 06ecf44f3f0 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 35025b59233 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards 8ab46266780 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards bd4c30c3181 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 7923797783a 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 586d22fe7d1 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards a3a1d9ba5fe 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 94daede4c58 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 3c6b9840309 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 220cefe553f 213: force: #24: 1: Success after binutils: 2 commits discards 4896a6d75e6 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 152dff81384 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 84b72fb7f43 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards fd1ef5fd68c 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 35187d2bf3a 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 97ecd7f9848 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 698557bfe8a 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 775c706ebf7 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 4932faf0dd5 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 6b877b66a17 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 117b4d00f31 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 19342c8a6f0 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 1572bcea162 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 62021b58b8f 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards d5e8af8c846 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards c50309ec710 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards ad57eb7c3c3 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 72666dd60f7 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards b3da2da63cc 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 6a4f4c96446 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 6baf49253ae 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards cdfba5f6117 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 4605876647e 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 0b27b22f631 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 70e011a7b51 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 5521be91a13 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 2b4d6cb2739 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 0f569368f48 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 01506c42583 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 2ab3cf0352a 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 32f431af4fb 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 73e5cddae2a 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 2cb5ed2d536 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 9534f33546e 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 37d5d4b43a7 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards e2790c8c6b9 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 5aa31bda826 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 8571f065f6c 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 1e617cf27e7 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards acf2b9582bf 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 44c09d4b046 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 3467607ea1d 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 8d582963588 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards c64524b0b26 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards 10fd75113df 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 573504e6923 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards ee8cfe47f4a 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 31adc5dd73e 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards d910196ba4b 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 78c010cbb84 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 0ba063e4657 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards bece5555eed 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards aacea6428c0 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 57a64c1c538 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards c6b55ad2ad9 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards a667ce39fdb 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards de508a73476 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards bdae1ecae35 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 8c9093373c4 154: onsuccess: #583: 1: Success after linux: 10 commits discards 3cda7542bae 153: onsuccess: #582: 1: Success after glibc: 9 commits discards c22841ccfd8 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 7ac4db277e0 151: onsuccess: #579: 1: Success after binutils: 21 commits discards eed03bc0b9c 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards f9d3f2502ba 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 2c23563dbca 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 7c475f14474 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards a773d7d380a 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 13402546c23 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards 346c61c64c7 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 5127bd6c027 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards e93021cf7ee 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards 07b3bc7eb84 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards 0a5c393a572 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards d92534d25b2 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 24ab0087545 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 21be797c55e 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards e5f27bedcf9 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 52f4b5ca218 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 5f848c372e6 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 692b70af525 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 02786792005 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards 2933226f838 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 4a44d6a37e6 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards a09f618083f 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 07160585463 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 672f792b587 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 013a5b890b8 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 2834049b3ab 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 23647290b07 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 0668065cb28 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 25ab7569d76 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 90250007c52 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 62bed478396 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 138671374e2 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 6ee4fc3a04e 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new bb9c62a6c4c 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 71b7f21085e 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 744e203a80d 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 7d0893bbac9 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new bc3b925115b 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 74fc8743d84 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 3dd710690de 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 3c9c7715688 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 78c4f1724ca 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new 08a47bf4492 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new a8c972ee72a 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new d1f492e7d2c 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 87cf7180334 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 4436732f31e 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 5e9366b0882 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new 3fa78004dba 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 2ad7da9f590 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new 0706c646c4f 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 0154808c99c 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 7938b1f6e81 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 2a459b8d4f5 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new c61eec475d9 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 011869b2c93 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new b3f42837dec 151: onsuccess: #579: 1: Success after binutils: 21 commits new 9b5d2c2fd42 152: onsuccess: #580: 1: Success after gcc: 6 commits new 4a3608a5f7c 153: onsuccess: #582: 1: Success after glibc: 9 commits new f513abaa8ce 154: onsuccess: #583: 1: Success after linux: 10 commits new e7ddc0b23a2 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new c95384e4598 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 645a4008df6 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new f0332349264 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 27ee9d36bba 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 48ddadb0ed9 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 4fe09abb27d 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 60f82db9d88 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 792ee35b355 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 1b1d7fb8ce9 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new ad0422ecbaa 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 0f0b919feb9 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new c579b961eb6 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 6232fd277c6 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 1a477a49510 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new d94d0aeb39f 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 9eddfd39ddd 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 715ad62e860 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 2a383ce7d63 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 5fcda87e548 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 61021529859 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 24b12e56aac 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 7b2c2f0287a 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 774fea3289c 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new a2ac6ef0254 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 1e6173f3d5e 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 5a2385cbf8f 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 81c35e9cb5d 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new e7664c6d5ea 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new b7e1e3e9ecb 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 6a6d35eeffb 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new d19be75ab55 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new f2097d43df6 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 0431bf53177 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 0fce29f22bd 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 75cd95183fa 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new f56519cd726 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 74c197c7925 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 81a6a750edf 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new ef437e502b8 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new b70c475cd80 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new df1b0c8cbb3 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new c6df95719a4 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new b4eeaf6479b 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new a3461b40f3e 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 1af25d32717 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 5b91515217d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 953a9245171 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 14ee8a66fa2 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 47903e39a86 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 2acd6a27bf1 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 4b206db628b 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 44ec2f00c6d 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new a46264c60cd 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 5b9045f25fe 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 421968cc761 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 1b5c43b657d 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new e36e698e38c 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new aee48df7a9c 213: force: #24: 1: Success after binutils: 2 commits new 82a469643e6 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 63194b20a1c 215: onsuccess: #26: 1: Success after binutils: 10 commits new baa01446980 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 71e29687880 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 42ce2a08865 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 5108fd30f06 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new c3110642623 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new c3c1d40c5e6 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new 724bc278b32 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new a899c835aaa 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 0e2dc599d1f 224: onsuccess: #36: 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 (4626d16f738) \ 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 2040 -> 2016 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 48896 -> 49032 bytes 04-build_abe-gcc/console.log.xz | Bin 236096 -> 236612 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8880 -> 8440 bytes 07-build_abe-glibc/console.log.xz | Bin 232504 -> 233124 bytes 08-build_abe-gdb/console.log.xz | Bin 47108 -> 47100 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3772 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2112 -> 2108 bytes 11-check_regression/console.log.xz | Bin 4776 -> 4200 bytes 11-check_regression/results.compare | 10 +++---- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 42 ++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++------------ sumfiles/binutils.log.xz | Bin 62848 -> 62152 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100604 -> 100596 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132200 -> 132248 bytes sumfiles/ld.sum | 4 +-- 28 files changed, 58 insertions(+), 58 deletions(-)