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 0e2dc599d1f 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards a899c835aaa 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards 724bc278b32 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards c3c1d40c5e6 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards c3110642623 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards 5108fd30f06 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 42ce2a08865 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 71e29687880 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards baa01446980 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 63194b20a1c 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 82a469643e6 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards aee48df7a9c 213: force: #24: 1: Success after binutils: 2 commits discards e36e698e38c 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 1b5c43b657d 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 421968cc761 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 5b9045f25fe 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards a46264c60cd 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 44ec2f00c6d 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 4b206db628b 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 2acd6a27bf1 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 47903e39a86 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 14ee8a66fa2 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 953a9245171 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 5b91515217d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 1af25d32717 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards a3461b40f3e 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards b4eeaf6479b 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards c6df95719a4 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards df1b0c8cbb3 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards b70c475cd80 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards ef437e502b8 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 81a6a750edf 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 74c197c7925 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards f56519cd726 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 75cd95183fa 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 0fce29f22bd 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 0431bf53177 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards f2097d43df6 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards d19be75ab55 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 6a6d35eeffb 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards b7e1e3e9ecb 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards e7664c6d5ea 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 81c35e9cb5d 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 5a2385cbf8f 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 1e6173f3d5e 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards a2ac6ef0254 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 774fea3289c 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 7b2c2f0287a 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 24b12e56aac 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 61021529859 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 5fcda87e548 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 2a383ce7d63 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 715ad62e860 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 9eddfd39ddd 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards d94d0aeb39f 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 1a477a49510 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards 6232fd277c6 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards c579b961eb6 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 0f0b919feb9 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards ad0422ecbaa 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 1b1d7fb8ce9 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 792ee35b355 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 60f82db9d88 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 4fe09abb27d 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 48ddadb0ed9 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 27ee9d36bba 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards f0332349264 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 645a4008df6 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards c95384e4598 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards e7ddc0b23a2 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards f513abaa8ce 154: onsuccess: #583: 1: Success after linux: 10 commits discards 4a3608a5f7c 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 9b5d2c2fd42 152: onsuccess: #580: 1: Success after gcc: 6 commits discards b3f42837dec 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 011869b2c93 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards c61eec475d9 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 2a459b8d4f5 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 7938b1f6e81 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 0154808c99c 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 0706c646c4f 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards 2ad7da9f590 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 3fa78004dba 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 5e9366b0882 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards 4436732f31e 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards 87cf7180334 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards d1f492e7d2c 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards a8c972ee72a 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 08a47bf4492 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 78c4f1724ca 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 3c9c7715688 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 3dd710690de 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 74fc8743d84 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards bc3b925115b 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards 7d0893bbac9 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 744e203a80d 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 71b7f21085e 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards bb9c62a6c4c 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 6ee4fc3a04e 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 138671374e2 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 62bed478396 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 90250007c52 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 34ff8f27633 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new f8163456920 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 4118a2fbbf0 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new db0f4b65b4f 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new bf520751515 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new cac31d6d0f0 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new a56d47a2820 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new dfa6203caf6 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new dc39a07aa5a 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new b70487e3484 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 4d08fb001f8 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 849012064ce 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 29a095e6508 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new 6985e658271 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new e195d26c5e2 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new ffb96f9a68a 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new b08bc811a92 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 8a53ac14075 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 43a86f83ad4 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new 47296f76f9c 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 5b8e467fce1 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new 3bd6a69fa6d 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new f440ce404e2 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new b1038832119 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new d41699ed3fe 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 1868bb33056 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 7db8b9bb6be 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new e920c1cc496 151: onsuccess: #579: 1: Success after binutils: 21 commits new f5d36616412 152: onsuccess: #580: 1: Success after gcc: 6 commits new c98b221f7ae 153: onsuccess: #582: 1: Success after glibc: 9 commits new c4b8e9fb473 154: onsuccess: #583: 1: Success after linux: 10 commits new 19725c120b4 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 4c84cbea1e6 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 8502a51ca25 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 6b6148c4e93 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new d238359ceb2 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new a72c37768c8 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 6d4799bfb04 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 9171d98d587 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 2d03c275c41 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new dbccb7d2d31 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new df1852878ba 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new d846fb669e6 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 63ee5523329 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 2d65d5f72f4 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 6ab2d437780 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new bb08355eb2a 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 316ad7212d7 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 5fe592ad1d2 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 13013d2176a 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new b0f6f66e05c 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new ca4db11a2cf 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new 50fc7e4fa7d 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new e1a82094bb6 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 08e63cde32a 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 67efe43084a 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 75b8aa189c0 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new fcb6e3f75d2 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new eb13f76e4bc 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 81c25312f88 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new db8d2c2b2aa 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 1848bd322a0 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 5c7f361d7a4 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new ffb770b289d 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new e0d81739b3e 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new e249198e8f3 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 0f0c12f4e1d 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 28485cae472 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 3bb249388dd 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new e0d002adbe9 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 304d8d76e47 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 39a28929987 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new e26c42988dd 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new ab6a3c626fd 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 0bee5c84d07 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new f3dbd8a2f01 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new cea762d6818 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 0296183b580 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new e33bd7bf36a 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new ba2ef3a1f40 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 4256cb14ceb 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 48f49d12c54 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 1a297e6c81c 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 762560471fb 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 32998204a32 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new c84d05ecba0 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 9928df3e255 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 6b5ebb209c3 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new b7f32f6bae3 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 4cc6c2fa961 213: force: #24: 1: Success after binutils: 2 commits new a7c3d4bc702 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 5916421ca0b 215: onsuccess: #26: 1: Success after binutils: 10 commits new 1b8edf47feb 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 7e274c34e31 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new f9daa76f4a5 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 74f8659a90e 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 32a6c01a1ff 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new 377f50faaea 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new 4579b80f9ab 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new ed7f73a8fbc 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 969343d39d7 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new a418d5e57d6 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...]

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 (0e2dc599d1f) \ 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 2016 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 49032 -> 48404 bytes 04-build_abe-gcc/console.log.xz | Bin 236612 -> 235688 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8440 -> 8204 bytes 07-build_abe-glibc/console.log.xz | Bin 233124 -> 234696 bytes 08-build_abe-gdb/console.log.xz | Bin 47100 -> 46652 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3764 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2108 -> 2120 bytes 11-check_regression/console.log.xz | Bin 4200 -> 4800 bytes 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 40 ++++++++++++++--------------- 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/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++++++------------- sumfiles/binutils.log.xz | Bin 62152 -> 62376 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100596 -> 100648 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132248 -> 132196 bytes sumfiles/ld.sum | 4 +-- 29 files changed, 58 insertions(+), 58 deletions(-)