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_build/master-arm in repository toolchain/ci/base-artifacts.
discards 4e53d6e4bff 216: onsuccess: #21: 6: Success after binutils/gcc/linux/gd [...] discards bc31b8dc4e2 215: onsuccess: #20: 6: Success after binutils/gcc/linux/gl [...] discards 1cb0fb29a98 214: onsuccess: #19: 6: Success after binutils/gcc/linux/gd [...] discards 1660f94fdcc 213: onsuccess: #18: 6: Success after binutils/gcc/linux/gl [...] discards 4ef344820b6 212: onsuccess: #17: 6: Success after binutils/gcc/linux/gl [...] discards 51ba539d75b 211: onsuccess: #12: 6: Success after binutils/gcc/linux/gl [...] discards 9e3be332745 210: onsuccess: #11: 6: Success after binutils/gcc/linux/gd [...] discards 7e0b834b6f3 209: onsuccess: #10: 6: Success after binutils/gcc/linux/gd [...] discards 70288cb1d80 208: onsuccess: #9: 6: Success after binutils/gcc/linux/gli [...] discards 4d8c7e97b0c 207: onsuccess: #8: 6: Success after binutils/gcc/linux/gli [...] discards 8e9f73453c5 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gdb [...] discards 375a557dff3 205: onsuccess: #6: 6: Success after binutils/gcc/linux/gli [...] discards 8c7e4f16956 204: onsuccess: #5: 6: Success after binutils/gcc/linux/gli [...] discards d7a6ba5baa6 203: onsuccess: #4: 6: Success after binutils/gcc/linux/gli [...] discards 15d538b8155 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gdb [...] discards db8e548d9cd 201: onsuccess: #2: 6: Success after binutils/gcc/linux/gli [...] discards cbe844671a6 200: onsuccess: #1: 6: Success after binutils/gcc/linux/gli [...] discards 7f802f483f6 199: onsuccess: #630: 6: Success after binutils/gcc/linux/g [...] discards 14c697a0230 198: onsuccess: #629: 6: Success after binutils/gcc/linux/g [...] discards 898e6e39a09 197: onsuccess: #628: 6: Success after binutils/gcc/linux/g [...] discards fe76af328e0 196: onsuccess: #621: 6: Success after binutils/gcc/linux/g [...] discards 9a4f87a6383 195: onsuccess: #620: 6: Success after binutils/gcc/linux/g [...] discards 4443b2f3f4b 194: onsuccess: #619: 6: Success after binutils/gcc/linux/g [...] discards c9dc0a68ac5 193: onsuccess: #618: 6: Success after binutils/gcc/linux/g [...] discards c3b76a8cfbb 192: onsuccess: #617: 6: Success after binutils/gcc/linux/g [...] discards 35d6ac846ef 191: onsuccess: #615: 6: Success after binutils/gcc/linux/g [...] discards 8fba6b31261 190: onsuccess: #614: 6: Success after binutils/gcc/linux/g [...] discards 47b7bdb4598 189: onsuccess: #613: 6: Success after binutils/gcc/linux/g [...] discards 4f7079a9835 188: onsuccess: #612: 6: Success after binutils/gcc/linux/g [...] discards 5a2b39bb67d 187: onsuccess: #611: 6: Success after binutils/gcc/linux/g [...] discards 16c18bc34a7 186: onsuccess: #610: 6: Success after binutils/gcc/linux/g [...] discards d5c6dcead64 185: onsuccess: #609: 6: Success after binutils/gcc/linux/g [...] discards 4f4354e5ce2 184: onsuccess: #608: 6: Success after binutils/gcc/linux/g [...] discards 95a2e388f3d 183: onsuccess: #607: 6: Success after binutils/gcc/linux/g [...] discards cd23e597c4e 182: onsuccess: #606: 6: Success after binutils/gcc/linux/g [...] discards 73320fea10a 181: onsuccess: #605: 6: Success after binutils/gcc/linux/g [...] discards 0e63288f7c8 180: onsuccess: #604: 6: Success after binutils/gcc/linux/g [...] discards 964e782edf2 179: onsuccess: #603: 6: Success after binutils/gcc/linux/g [...] discards 8d3b0d48a28 178: onsuccess: #602: 6: Success after binutils/gcc/linux/g [...] discards 557722fee76 177: onsuccess: #601: 6: Success after binutils/gcc/linux/g [...] discards 18fb7206528 176: onsuccess: #600: 6: Success after binutils/gcc/linux/g [...] discards 2e04d48a1cc 175: onsuccess: #599: 6: Success after binutils/gcc/linux/g [...] discards f6f7ce8ed59 174: onsuccess: #598: 6: Success after binutils/gcc/linux/g [...] discards 470f7c79e2e 173: onsuccess: #597: 6: Success after binutils/gcc/linux/g [...] discards 7fb4234cc60 172: onsuccess: #596: 6: Success after binutils/gcc/linux/g [...] discards 31a14aa004e 171: onsuccess: #595: 6: Success after binutils/gcc/linux/g [...] discards 0260059bcb9 170: onsuccess: #594: 6: Success after binutils/gcc/linux/g [...] discards 5b71fab686b 169: onsuccess: #593: 6: Success after binutils/gcc/linux/g [...] discards 4258555af3e 168: onsuccess: #591: 6: Success after binutils/gcc/linux/g [...] discards caf60aebad7 167: onsuccess: #590: 6: Success after binutils/gcc/linux/g [...] discards 92101c3a0b1 166: onsuccess: #589: 6: Success after binutils/gcc/linux/g [...] discards 9a50224d1a3 165: onsuccess: #588: 6: Success after binutils/gcc/linux/g [...] discards 430ba29ddb3 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/g [...] discards fc68f02be9f 163: onsuccess: #586: 6: Success after binutils/gcc/linux/g [...] discards 3bdd098c9d5 162: onsuccess: #579: 6: Success after gcc: 11 commits discards 185121c88ee 161: onsuccess: #578: 6: Success after binutils: 15 commits discards 0bdaa8c294e 160: onsuccess: #576: 6: Success after binutils/gcc/linux/g [...] discards 9b94df41635 159: onsuccess: #575: 6: Success after binutils/gcc/linux/g [...] discards a3a8c214130 158: onsuccess: #574: 6: Success after binutils/gcc/linux/g [...] discards 5ef7ec86d0d 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits discards e0ff2a58ba7 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 [...] discards ea37eed5c5e 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 [...] discards 1fe8039573d 154: onsuccess: #570: 6: Success after binutils/gcc/linux/g [...] discards d4f247a7277 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 [...] discards 3a299cd49fd 152: onsuccess: #568: 6: Success after binutils/gcc/linux/g [...] discards 50d2dd7a398 151: onsuccess: #567: 6: Success after binutils/gcc/linux/g [...] discards d0b0b42ad48 150: onsuccess: #566: 6: Success after binutils/gcc/linux/g [...] discards 7bb4059feaf 149: onsuccess: #565: 6: Success after binutils/gcc/linux/g [...] discards dcb6c9aa6ea 148: onsuccess: #564: 6: Success after binutils/gcc/linux/g [...] discards d9ddfab427f 147: onsuccess: #563: 6: Success after binutils/gcc/linux/g [...] discards 0d8aed15e71 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 [...] discards dcd3e1e5cc6 145: onsuccess: #561: 6: Success after binutils/gcc/linux/g [...] discards 4b12e8769f7 144: onsuccess: #560: 6: Success after binutils/gcc/linux/g [...] discards 89b464fe10f 143: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] discards 425c53ccf07 142: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] discards 12662e4c613 141: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] discards c0a11a6fd91 140: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] discards 5668ee0ac88 139: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] discards 3817a5d2de7 138: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] discards 9f0a8318877 137: onsuccess: #553: 6: Success after binutils/gcc/linux/g [...] discards c68dd82e2fa 136: onsuccess: #551: 6: Success after binutils/gcc/linux/g [...] discards c9b46018311 135: onsuccess: #550: 6: Success after binutils/gcc/linux/g [...] discards 6d2cd812eb1 134: onsuccess: #544: 6: Success after binutils: 18 commits discards 5794e1d99ab 133: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] discards c1905f38192 132: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] discards e61fef6ea1b 131: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] discards 6922a11f316 130: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] discards f767c888e33 129: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] discards 62d417f5de5 128: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] discards 7251fd0da62 127: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] discards 35b83c2530e 126: onsuccess: #535: 6: Success after binutils/gcc/linux/g [...] discards 719f9853320 125: onsuccess: #534: 6: Success after binutils/gcc/linux/g [...] discards ed1cb748854 124: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] discards 5610c0ce372 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 [...] discards fafc7ba7403 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 [...] discards 45ec5f3f804 121: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] discards 8c4ebbcde0d 120: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] discards fa7e203e53d 119: onsuccess: #528: 6: Success after binutils/gcc/linux/g [...] discards 75f599f37c5 118: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] discards 7c657d47f7b 117: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] discards f4dd02198d5 116: onsuccess: #525: 6: Success after binutils/gcc/linux/g [...] new 46e9280d706 116: onsuccess: #525: 6: Success after binutils/gcc/linux/g [...] new d3bb34decf0 117: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] new 8f75a797f74 118: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] new d547639cb50 119: onsuccess: #528: 6: Success after binutils/gcc/linux/g [...] new 01dccb58570 120: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] new f36494f75f3 121: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] new e6a00e72b74 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 [...] new 4b4c75ade8d 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 [...] new c82b2c212d0 124: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] new 05f08189930 125: onsuccess: #534: 6: Success after binutils/gcc/linux/g [...] new 700eb817a3b 126: onsuccess: #535: 6: Success after binutils/gcc/linux/g [...] new bd39e5d0080 127: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] new 789d27bacd0 128: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new d1147798425 129: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] new 2ce69a14473 130: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] new 79c8daa28d2 131: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] new 6a74a741cd5 132: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] new c88a8e5168b 133: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] new 6e6d55bd5b0 134: onsuccess: #544: 6: Success after binutils: 18 commits new db5d89b1302 135: onsuccess: #550: 6: Success after binutils/gcc/linux/g [...] new 26e83000927 136: onsuccess: #551: 6: Success after binutils/gcc/linux/g [...] new f34b0fcc978 137: onsuccess: #553: 6: Success after binutils/gcc/linux/g [...] new 1a91b0c2b9d 138: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] new adb94461187 139: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] new 091a83cff64 140: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] new 350688e7884 141: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] new c54d608fe34 142: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] new 0667fca682b 143: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] new 165bc14427a 144: onsuccess: #560: 6: Success after binutils/gcc/linux/g [...] new d7d166f8482 145: onsuccess: #561: 6: Success after binutils/gcc/linux/g [...] new 14099bf97cd 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 [...] new 017bd9891d8 147: onsuccess: #563: 6: Success after binutils/gcc/linux/g [...] new 63ddc5ae175 148: onsuccess: #564: 6: Success after binutils/gcc/linux/g [...] new 0a8323f541a 149: onsuccess: #565: 6: Success after binutils/gcc/linux/g [...] new 83f844489bb 150: onsuccess: #566: 6: Success after binutils/gcc/linux/g [...] new fcd4d091826 151: onsuccess: #567: 6: Success after binutils/gcc/linux/g [...] new 747e14e4eb9 152: onsuccess: #568: 6: Success after binutils/gcc/linux/g [...] new 9d1b3990109 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 [...] new 3c965ee2d46 154: onsuccess: #570: 6: Success after binutils/gcc/linux/g [...] new 8926a36d853 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 [...] new 70556766f32 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 [...] new 17ce13f5f81 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits new d4817a6bd7a 158: onsuccess: #574: 6: Success after binutils/gcc/linux/g [...] new 3991bb29938 159: onsuccess: #575: 6: Success after binutils/gcc/linux/g [...] new c24295a7d80 160: onsuccess: #576: 6: Success after binutils/gcc/linux/g [...] new bceb934a56c 161: onsuccess: #578: 6: Success after binutils: 15 commits new b5e85d21b34 162: onsuccess: #579: 6: Success after gcc: 11 commits new 139cbf48ca4 163: onsuccess: #586: 6: Success after binutils/gcc/linux/g [...] new 09a9bcd26d8 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/g [...] new 67fc194a32f 165: onsuccess: #588: 6: Success after binutils/gcc/linux/g [...] new 8e84f78efcb 166: onsuccess: #589: 6: Success after binutils/gcc/linux/g [...] new 3b7ba6879d0 167: onsuccess: #590: 6: Success after binutils/gcc/linux/g [...] new 99c6c78ad49 168: onsuccess: #591: 6: Success after binutils/gcc/linux/g [...] new 5cd5abd51d6 169: onsuccess: #593: 6: Success after binutils/gcc/linux/g [...] new fb0b9e4047e 170: onsuccess: #594: 6: Success after binutils/gcc/linux/g [...] new 46e03030ba5 171: onsuccess: #595: 6: Success after binutils/gcc/linux/g [...] new c5df30f50f7 172: onsuccess: #596: 6: Success after binutils/gcc/linux/g [...] new 0915e591128 173: onsuccess: #597: 6: Success after binutils/gcc/linux/g [...] new 77144cc16e1 174: onsuccess: #598: 6: Success after binutils/gcc/linux/g [...] new 05de682e085 175: onsuccess: #599: 6: Success after binutils/gcc/linux/g [...] new 5b1ef5c3508 176: onsuccess: #600: 6: Success after binutils/gcc/linux/g [...] new 01636f233c9 177: onsuccess: #601: 6: Success after binutils/gcc/linux/g [...] new 283f0f50f8c 178: onsuccess: #602: 6: Success after binutils/gcc/linux/g [...] new 3954fcc44cf 179: onsuccess: #603: 6: Success after binutils/gcc/linux/g [...] new 0160167de16 180: onsuccess: #604: 6: Success after binutils/gcc/linux/g [...] new 44ca1a6d782 181: onsuccess: #605: 6: Success after binutils/gcc/linux/g [...] new f9626230014 182: onsuccess: #606: 6: Success after binutils/gcc/linux/g [...] new a47c2ffb9c1 183: onsuccess: #607: 6: Success after binutils/gcc/linux/g [...] new 7bc00fd5998 184: onsuccess: #608: 6: Success after binutils/gcc/linux/g [...] new 434741caf81 185: onsuccess: #609: 6: Success after binutils/gcc/linux/g [...] new 2cf501e3220 186: onsuccess: #610: 6: Success after binutils/gcc/linux/g [...] new d5911726593 187: onsuccess: #611: 6: Success after binutils/gcc/linux/g [...] new 17764adb8d7 188: onsuccess: #612: 6: Success after binutils/gcc/linux/g [...] new fdc55c71866 189: onsuccess: #613: 6: Success after binutils/gcc/linux/g [...] new eca66888d40 190: onsuccess: #614: 6: Success after binutils/gcc/linux/g [...] new bcdbced374a 191: onsuccess: #615: 6: Success after binutils/gcc/linux/g [...] new fb5ad98abf3 192: onsuccess: #617: 6: Success after binutils/gcc/linux/g [...] new 6437b4316fc 193: onsuccess: #618: 6: Success after binutils/gcc/linux/g [...] new 469da4e16a9 194: onsuccess: #619: 6: Success after binutils/gcc/linux/g [...] new ab5c47c43db 195: onsuccess: #620: 6: Success after binutils/gcc/linux/g [...] new 90fb5247fea 196: onsuccess: #621: 6: Success after binutils/gcc/linux/g [...] new 60d0acc22c5 197: onsuccess: #628: 6: Success after binutils/gcc/linux/g [...] new 119a3dba4e8 198: onsuccess: #629: 6: Success after binutils/gcc/linux/g [...] new cf64ee8d4d7 199: onsuccess: #630: 6: Success after binutils/gcc/linux/g [...] new 9c0fade8f06 200: onsuccess: #1: 6: Success after binutils/gcc/linux/gli [...] new 8aabad6491b 201: onsuccess: #2: 6: Success after binutils/gcc/linux/gli [...] new 9b25ba929b2 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gdb [...] new f75867d47c6 203: onsuccess: #4: 6: Success after binutils/gcc/linux/gli [...] new 2b428cc609f 204: onsuccess: #5: 6: Success after binutils/gcc/linux/gli [...] new a02a38eab95 205: onsuccess: #6: 6: Success after binutils/gcc/linux/gli [...] new 925d3e9e239 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gdb [...] new 67e096ac8c6 207: onsuccess: #8: 6: Success after binutils/gcc/linux/gli [...] new 15ccb72f7cb 208: onsuccess: #9: 6: Success after binutils/gcc/linux/gli [...] new 06afa454614 209: onsuccess: #10: 6: Success after binutils/gcc/linux/gd [...] new 5204f0e97ba 210: onsuccess: #11: 6: Success after binutils/gcc/linux/gd [...] new cfd814e80f5 211: onsuccess: #12: 6: Success after binutils/gcc/linux/gl [...] new 42d12d871bf 212: onsuccess: #17: 6: Success after binutils/gcc/linux/gl [...] new 88d91df88c7 213: onsuccess: #18: 6: Success after binutils/gcc/linux/gl [...] new f56291ca974 214: onsuccess: #19: 6: Success after binutils/gcc/linux/gd [...] new e2a12efb621 215: onsuccess: #20: 6: Success after binutils/gcc/linux/gl [...] new dab3d965aca 216: onsuccess: #21: 6: Success after binutils/gcc/linux/gd [...] new 5bf1d8ce9fa 217: onsuccess: #22: 6: 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 (4e53d6e4bff) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...]
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 1740 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 52748 -> 52556 bytes 05-build_abe-gcc/console.log.xz | Bin 239668 -> 238396 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8912 -> 8256 bytes 08-build_abe-glibc/console.log.xz | Bin 236064 -> 235928 bytes 09-build_abe-gdb/console.log.xz | Bin 50132 -> 50872 bytes 10-check_regression/console.log.xz | Bin 3924 -> 4520 bytes 11-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/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++++++--------------- 20 files changed, 50 insertions(+), 50 deletions(-)