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 494e997eea9 215: onsuccess: #20: 6: Success after binutils/gcc/linux/gl [...] discards 8770e65f202 214: onsuccess: #19: 6: Success after binutils/gcc/linux/gd [...] discards bafe4bd2375 213: onsuccess: #18: 6: Success after binutils/gcc/linux/gl [...] discards 7b39e86518b 212: onsuccess: #17: 6: Success after binutils/gcc/linux/gl [...] discards dbf9a373983 211: onsuccess: #12: 6: Success after binutils/gcc/linux/gl [...] discards 7837b22ee6c 210: onsuccess: #11: 6: Success after binutils/gcc/linux/gd [...] discards af7bc5cb568 209: onsuccess: #10: 6: Success after binutils/gcc/linux/gd [...] discards 1753014400d 208: onsuccess: #9: 6: Success after binutils/gcc/linux/gli [...] discards d5a5a1e66e4 207: onsuccess: #8: 6: Success after binutils/gcc/linux/gli [...] discards 3f12e871f05 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gdb [...] discards 2587ee08a79 205: onsuccess: #6: 6: Success after binutils/gcc/linux/gli [...] discards 7749e228982 204: onsuccess: #5: 6: Success after binutils/gcc/linux/gli [...] discards 161f4a5d783 203: onsuccess: #4: 6: Success after binutils/gcc/linux/gli [...] discards 87c47749d0d 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gdb [...] discards 1fd00d61296 201: onsuccess: #2: 6: Success after binutils/gcc/linux/gli [...] discards 5cf8c65b945 200: onsuccess: #1: 6: Success after binutils/gcc/linux/gli [...] discards 191801cef15 199: onsuccess: #630: 6: Success after binutils/gcc/linux/g [...] discards b0402d41fdf 198: onsuccess: #629: 6: Success after binutils/gcc/linux/g [...] discards 5ffa99ae526 197: onsuccess: #628: 6: Success after binutils/gcc/linux/g [...] discards 85a0988b3d3 196: onsuccess: #621: 6: Success after binutils/gcc/linux/g [...] discards 107208cfa55 195: onsuccess: #620: 6: Success after binutils/gcc/linux/g [...] discards de1b0fd8fc8 194: onsuccess: #619: 6: Success after binutils/gcc/linux/g [...] discards d98845cdb53 193: onsuccess: #618: 6: Success after binutils/gcc/linux/g [...] discards 7ce0b3caff7 192: onsuccess: #617: 6: Success after binutils/gcc/linux/g [...] discards 79932b8dac7 191: onsuccess: #615: 6: Success after binutils/gcc/linux/g [...] discards 45834ea812f 190: onsuccess: #614: 6: Success after binutils/gcc/linux/g [...] discards 4654a9df688 189: onsuccess: #613: 6: Success after binutils/gcc/linux/g [...] discards 60771a4e1ea 188: onsuccess: #612: 6: Success after binutils/gcc/linux/g [...] discards f6085f0ae62 187: onsuccess: #611: 6: Success after binutils/gcc/linux/g [...] discards a92e0d8587e 186: onsuccess: #610: 6: Success after binutils/gcc/linux/g [...] discards 6a49432e61e 185: onsuccess: #609: 6: Success after binutils/gcc/linux/g [...] discards bc18c413556 184: onsuccess: #608: 6: Success after binutils/gcc/linux/g [...] discards 7c4a9df97d6 183: onsuccess: #607: 6: Success after binutils/gcc/linux/g [...] discards e6bcf64e148 182: onsuccess: #606: 6: Success after binutils/gcc/linux/g [...] discards 7c027c88f0e 181: onsuccess: #605: 6: Success after binutils/gcc/linux/g [...] discards 07ecea47230 180: onsuccess: #604: 6: Success after binutils/gcc/linux/g [...] discards c4713832611 179: onsuccess: #603: 6: Success after binutils/gcc/linux/g [...] discards fd60f6d07e6 178: onsuccess: #602: 6: Success after binutils/gcc/linux/g [...] discards 95070839d1e 177: onsuccess: #601: 6: Success after binutils/gcc/linux/g [...] discards 442dcd6520a 176: onsuccess: #600: 6: Success after binutils/gcc/linux/g [...] discards 0e49cd370f4 175: onsuccess: #599: 6: Success after binutils/gcc/linux/g [...] discards fe205d0d858 174: onsuccess: #598: 6: Success after binutils/gcc/linux/g [...] discards e71da943d5c 173: onsuccess: #597: 6: Success after binutils/gcc/linux/g [...] discards 7e8f7e4fd36 172: onsuccess: #596: 6: Success after binutils/gcc/linux/g [...] discards 31d5141d42d 171: onsuccess: #595: 6: Success after binutils/gcc/linux/g [...] discards 82744b8eecc 170: onsuccess: #594: 6: Success after binutils/gcc/linux/g [...] discards a73589fe273 169: onsuccess: #593: 6: Success after binutils/gcc/linux/g [...] discards 0f541f36808 168: onsuccess: #591: 6: Success after binutils/gcc/linux/g [...] discards 3e3e73a3a76 167: onsuccess: #590: 6: Success after binutils/gcc/linux/g [...] discards e4900fc5538 166: onsuccess: #589: 6: Success after binutils/gcc/linux/g [...] discards 8cf2036a824 165: onsuccess: #588: 6: Success after binutils/gcc/linux/g [...] discards 59dca5d5cb1 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/g [...] discards 8fd7d84356d 163: onsuccess: #586: 6: Success after binutils/gcc/linux/g [...] discards 84b05d1fceb 162: onsuccess: #579: 6: Success after gcc: 11 commits discards aad05c3fba6 161: onsuccess: #578: 6: Success after binutils: 15 commits discards 81f445b162b 160: onsuccess: #576: 6: Success after binutils/gcc/linux/g [...] discards 16362665f91 159: onsuccess: #575: 6: Success after binutils/gcc/linux/g [...] discards 3adbc63578c 158: onsuccess: #574: 6: Success after binutils/gcc/linux/g [...] discards fb83ac47f9d 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits discards 77781c19a0b 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 [...] discards 97db47c212b 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 [...] discards efc24bd30aa 154: onsuccess: #570: 6: Success after binutils/gcc/linux/g [...] discards a0ba86b5c39 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 [...] discards 1047d9cf84d 152: onsuccess: #568: 6: Success after binutils/gcc/linux/g [...] discards 7b754f4c464 151: onsuccess: #567: 6: Success after binutils/gcc/linux/g [...] discards 7ede5e517a7 150: onsuccess: #566: 6: Success after binutils/gcc/linux/g [...] discards f471deed065 149: onsuccess: #565: 6: Success after binutils/gcc/linux/g [...] discards 80688bd538b 148: onsuccess: #564: 6: Success after binutils/gcc/linux/g [...] discards 91eee000494 147: onsuccess: #563: 6: Success after binutils/gcc/linux/g [...] discards f5710f8be12 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 [...] discards e1b177da0f5 145: onsuccess: #561: 6: Success after binutils/gcc/linux/g [...] discards 27ae33b47bf 144: onsuccess: #560: 6: Success after binutils/gcc/linux/g [...] discards a07ff1d10b1 143: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] discards ab5ef0ef18c 142: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] discards 0375adba135 141: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] discards cacad66e2ce 140: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] discards 5e076206fd2 139: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] discards 56328c64bdf 138: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] discards 99910cdc4c7 137: onsuccess: #553: 6: Success after binutils/gcc/linux/g [...] discards 81e7c7f9fc7 136: onsuccess: #551: 6: Success after binutils/gcc/linux/g [...] discards 9c17243e40a 135: onsuccess: #550: 6: Success after binutils/gcc/linux/g [...] discards 16413b19059 134: onsuccess: #544: 6: Success after binutils: 18 commits discards dbe528c90fe 133: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] discards 6994ebe69d1 132: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] discards 3cb4447f06f 131: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] discards 6be54e4fc1e 130: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] discards 04ec834d4cc 129: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] discards 4e6e9ee55de 128: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] discards 32053d4bddb 127: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] discards 4302312f6f7 126: onsuccess: #535: 6: Success after binutils/gcc/linux/g [...] discards cd11a197ed1 125: onsuccess: #534: 6: Success after binutils/gcc/linux/g [...] discards cb5d88b9488 124: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] discards 4f9d0b3235a 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 [...] discards d0dee8a43d2 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 [...] discards 92226294a76 121: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] discards cf2d5f2ed5a 120: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] discards a7628503dec 119: onsuccess: #528: 6: Success after binutils/gcc/linux/g [...] discards 28e21b79b02 118: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] discards 3d6aeac973c 117: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] discards d308af366a4 116: onsuccess: #525: 6: Success after binutils/gcc/linux/g [...] discards 5ff0d356a2d 115: onsuccess: #524: 6: Success after binutils/gcc/linux/g [...] new 25671074cda 115: onsuccess: #524: 6: Success after binutils/gcc/linux/g [...] new f4dd02198d5 116: onsuccess: #525: 6: Success after binutils/gcc/linux/g [...] new 7c657d47f7b 117: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] new 75f599f37c5 118: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] new fa7e203e53d 119: onsuccess: #528: 6: Success after binutils/gcc/linux/g [...] new 8c4ebbcde0d 120: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] new 45ec5f3f804 121: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] new fafc7ba7403 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 [...] new 5610c0ce372 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 [...] new ed1cb748854 124: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] new 719f9853320 125: onsuccess: #534: 6: Success after binutils/gcc/linux/g [...] new 35b83c2530e 126: onsuccess: #535: 6: Success after binutils/gcc/linux/g [...] new 7251fd0da62 127: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] new 62d417f5de5 128: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new f767c888e33 129: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] new 6922a11f316 130: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] new e61fef6ea1b 131: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] new c1905f38192 132: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] new 5794e1d99ab 133: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] new 6d2cd812eb1 134: onsuccess: #544: 6: Success after binutils: 18 commits new c9b46018311 135: onsuccess: #550: 6: Success after binutils/gcc/linux/g [...] new c68dd82e2fa 136: onsuccess: #551: 6: Success after binutils/gcc/linux/g [...] new 9f0a8318877 137: onsuccess: #553: 6: Success after binutils/gcc/linux/g [...] new 3817a5d2de7 138: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] new 5668ee0ac88 139: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] new c0a11a6fd91 140: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] new 12662e4c613 141: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] new 425c53ccf07 142: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] new 89b464fe10f 143: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] new 4b12e8769f7 144: onsuccess: #560: 6: Success after binutils/gcc/linux/g [...] new dcd3e1e5cc6 145: onsuccess: #561: 6: Success after binutils/gcc/linux/g [...] new 0d8aed15e71 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 [...] new d9ddfab427f 147: onsuccess: #563: 6: Success after binutils/gcc/linux/g [...] new dcb6c9aa6ea 148: onsuccess: #564: 6: Success after binutils/gcc/linux/g [...] new 7bb4059feaf 149: onsuccess: #565: 6: Success after binutils/gcc/linux/g [...] new d0b0b42ad48 150: onsuccess: #566: 6: Success after binutils/gcc/linux/g [...] new 50d2dd7a398 151: onsuccess: #567: 6: Success after binutils/gcc/linux/g [...] new 3a299cd49fd 152: onsuccess: #568: 6: Success after binutils/gcc/linux/g [...] new d4f247a7277 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 [...] new 1fe8039573d 154: onsuccess: #570: 6: Success after binutils/gcc/linux/g [...] new ea37eed5c5e 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 [...] new e0ff2a58ba7 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 [...] new 5ef7ec86d0d 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits new a3a8c214130 158: onsuccess: #574: 6: Success after binutils/gcc/linux/g [...] new 9b94df41635 159: onsuccess: #575: 6: Success after binutils/gcc/linux/g [...] new 0bdaa8c294e 160: onsuccess: #576: 6: Success after binutils/gcc/linux/g [...] new 185121c88ee 161: onsuccess: #578: 6: Success after binutils: 15 commits new 3bdd098c9d5 162: onsuccess: #579: 6: Success after gcc: 11 commits new fc68f02be9f 163: onsuccess: #586: 6: Success after binutils/gcc/linux/g [...] new 430ba29ddb3 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/g [...] new 9a50224d1a3 165: onsuccess: #588: 6: Success after binutils/gcc/linux/g [...] new 92101c3a0b1 166: onsuccess: #589: 6: Success after binutils/gcc/linux/g [...] new caf60aebad7 167: onsuccess: #590: 6: Success after binutils/gcc/linux/g [...] new 4258555af3e 168: onsuccess: #591: 6: Success after binutils/gcc/linux/g [...] new 5b71fab686b 169: onsuccess: #593: 6: Success after binutils/gcc/linux/g [...] new 0260059bcb9 170: onsuccess: #594: 6: Success after binutils/gcc/linux/g [...] new 31a14aa004e 171: onsuccess: #595: 6: Success after binutils/gcc/linux/g [...] new 7fb4234cc60 172: onsuccess: #596: 6: Success after binutils/gcc/linux/g [...] new 470f7c79e2e 173: onsuccess: #597: 6: Success after binutils/gcc/linux/g [...] new f6f7ce8ed59 174: onsuccess: #598: 6: Success after binutils/gcc/linux/g [...] new 2e04d48a1cc 175: onsuccess: #599: 6: Success after binutils/gcc/linux/g [...] new 18fb7206528 176: onsuccess: #600: 6: Success after binutils/gcc/linux/g [...] new 557722fee76 177: onsuccess: #601: 6: Success after binutils/gcc/linux/g [...] new 8d3b0d48a28 178: onsuccess: #602: 6: Success after binutils/gcc/linux/g [...] new 964e782edf2 179: onsuccess: #603: 6: Success after binutils/gcc/linux/g [...] new 0e63288f7c8 180: onsuccess: #604: 6: Success after binutils/gcc/linux/g [...] new 73320fea10a 181: onsuccess: #605: 6: Success after binutils/gcc/linux/g [...] new cd23e597c4e 182: onsuccess: #606: 6: Success after binutils/gcc/linux/g [...] new 95a2e388f3d 183: onsuccess: #607: 6: Success after binutils/gcc/linux/g [...] new 4f4354e5ce2 184: onsuccess: #608: 6: Success after binutils/gcc/linux/g [...] new d5c6dcead64 185: onsuccess: #609: 6: Success after binutils/gcc/linux/g [...] new 16c18bc34a7 186: onsuccess: #610: 6: Success after binutils/gcc/linux/g [...] new 5a2b39bb67d 187: onsuccess: #611: 6: Success after binutils/gcc/linux/g [...] new 4f7079a9835 188: onsuccess: #612: 6: Success after binutils/gcc/linux/g [...] new 47b7bdb4598 189: onsuccess: #613: 6: Success after binutils/gcc/linux/g [...] new 8fba6b31261 190: onsuccess: #614: 6: Success after binutils/gcc/linux/g [...] new 35d6ac846ef 191: onsuccess: #615: 6: Success after binutils/gcc/linux/g [...] new c3b76a8cfbb 192: onsuccess: #617: 6: Success after binutils/gcc/linux/g [...] new c9dc0a68ac5 193: onsuccess: #618: 6: Success after binutils/gcc/linux/g [...] new 4443b2f3f4b 194: onsuccess: #619: 6: Success after binutils/gcc/linux/g [...] new 9a4f87a6383 195: onsuccess: #620: 6: Success after binutils/gcc/linux/g [...] new fe76af328e0 196: onsuccess: #621: 6: Success after binutils/gcc/linux/g [...] new 898e6e39a09 197: onsuccess: #628: 6: Success after binutils/gcc/linux/g [...] new 14c697a0230 198: onsuccess: #629: 6: Success after binutils/gcc/linux/g [...] new 7f802f483f6 199: onsuccess: #630: 6: Success after binutils/gcc/linux/g [...] new cbe844671a6 200: onsuccess: #1: 6: Success after binutils/gcc/linux/gli [...] new db8e548d9cd 201: onsuccess: #2: 6: Success after binutils/gcc/linux/gli [...] new 15d538b8155 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gdb [...] new d7a6ba5baa6 203: onsuccess: #4: 6: Success after binutils/gcc/linux/gli [...] new 8c7e4f16956 204: onsuccess: #5: 6: Success after binutils/gcc/linux/gli [...] new 375a557dff3 205: onsuccess: #6: 6: Success after binutils/gcc/linux/gli [...] new 8e9f73453c5 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gdb [...] new 4d8c7e97b0c 207: onsuccess: #8: 6: Success after binutils/gcc/linux/gli [...] new 70288cb1d80 208: onsuccess: #9: 6: Success after binutils/gcc/linux/gli [...] new 7e0b834b6f3 209: onsuccess: #10: 6: Success after binutils/gcc/linux/gd [...] new 9e3be332745 210: onsuccess: #11: 6: Success after binutils/gcc/linux/gd [...] new 51ba539d75b 211: onsuccess: #12: 6: Success after binutils/gcc/linux/gl [...] new 4ef344820b6 212: onsuccess: #17: 6: Success after binutils/gcc/linux/gl [...] new 1660f94fdcc 213: onsuccess: #18: 6: Success after binutils/gcc/linux/gl [...] new 1cb0fb29a98 214: onsuccess: #19: 6: Success after binutils/gcc/linux/gd [...] new bc31b8dc4e2 215: onsuccess: #20: 6: Success after binutils/gcc/linux/gl [...] new 4e53d6e4bff 216: onsuccess: #21: 6: 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 (494e997eea9) \ 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 1732 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2768 bytes 04-build_abe-binutils/console.log.xz | Bin 52560 -> 52748 bytes 05-build_abe-gcc/console.log.xz | Bin 238832 -> 239668 bytes 07-build_abe-linux/console.log.xz | Bin 9120 -> 8912 bytes 08-build_abe-glibc/console.log.xz | Bin 236304 -> 236064 bytes 09-build_abe-gdb/console.log.xz | Bin 51080 -> 50132 bytes 10-check_regression/console.log.xz | Bin 4280 -> 3924 bytes 11-update_baseline/console.log | 64 +++++++++++++++++------------------ 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 | 32 +++++++++--------- 18 files changed, 56 insertions(+), 56 deletions(-)