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 624918485e 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards addbbae548 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 571a9c1fc8 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards f9daa953b7 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 90d30c51f9 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards bd16b7bf18 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 4c00e545a0 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 9a438412cf 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards ba96d5dc79 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 13c9a28d4b 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards c0f941f2f4 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 0715ba9be7 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 91870fdeb8 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 2eb2bb8dca 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 0ace79c243 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 7af676061a 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 825fae43ca 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 3545ecfc9c 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 16a950171f 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards b82e61f222 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 02b58b3f7c 215: onsuccess: #26: 1: Success after binutils: 10 commits discards bd1d084b3f 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 2cf7498bc3 213: force: #24: 1: Success after binutils: 2 commits discards 8725cae74b 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 6d19adb277 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards d83a09d921 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 8cd0ec044d 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards a053eced19 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards d2061dcae3 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 0c341c829c 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 44de991171 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 48d3ff8668 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 1f4490316f 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 6035e0fe5e 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 4de317bb1e 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 360f486755 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 5ecb679028 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards fafbc4eed3 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards c04e571d7e 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards ee19303c5f 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 206b4e174d 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 6e228bf3bd 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards da9874d86c 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards f0a7f17ef9 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards a9d8528a58 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards 29399dfc39 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards a76e999b32 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards e4351eeafc 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 622f90295a 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards a03eca5a71 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards b3d894409f 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards b9cce2011a 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards f0989b546f 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards 216c5e6ec5 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 5e2c43a7ae 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 1bce800ceb 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 85493627b7 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 5442e55948 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards 5038eac8fe 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 22d44e58eb 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 0138d3ded8 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards 5e36ed7f37 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 062eddda1d 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 08759ccf5b 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards a798b4cc24 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 2562f19450 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards cd0e21ad77 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards 84366cc001 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards a136dc8fe7 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 36e3f79dbe 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 980e45a7bb 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards cd7d5be4c7 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 1bdc0d85b6 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards 83df1f3637 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards ef4459c6ae 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards 53f59ae163 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards 0664999c40 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 2cbbfd10f7 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards f37e5f9770 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards c83ca69e0a 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 6d99f1bb6b 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 5fe81a03bc 154: onsuccess: #583: 1: Success after linux: 10 commits discards 173edfc70c 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 5b945c4f04 152: onsuccess: #580: 1: Success after gcc: 6 commits discards b75e45a809 151: onsuccess: #579: 1: Success after binutils: 21 commits discards dfbedbc6c8 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 72e3b82f15 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 65855c0a4b 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards 62b5cd5346 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 7421ae6ef2 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards 374c1e686d 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards b730776f8a 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards 5b7a915ba8 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 2e842aa764 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits discards 2d1c6132ed 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] discards 86ac65c2d1 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards ca30fa46d2 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 823f7c2491 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 037013b1a1 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards f12a2c409c 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] discards 4e245fd4c5 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new ce07d57d1c 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 189386dd50 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] new aba9325482 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 6cb6257065 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 919285fd13 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new f96d222dbe 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 9f0f8a7fe4 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] new 25d82b7336 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new 5be897601b 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 5d2f8e594f 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new c4380028fe 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new 02107941e1 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new 81160301ec 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new a41985621f 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new 3e8b82c57d 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 9b38dab53e 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 36b57443c8 151: onsuccess: #579: 1: Success after binutils: 21 commits new fdebddde0a 152: onsuccess: #580: 1: Success after gcc: 6 commits new 7719f3e8ae 153: onsuccess: #582: 1: Success after glibc: 9 commits new 79425c1328 154: onsuccess: #583: 1: Success after linux: 10 commits new eb383c9ce3 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 84e24a6dd0 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 834a30f7c5 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new 8c2466322d 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new 61a0932cfb 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 29dd948ca4 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new 8919cd6808 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new a3a675ab5a 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 68ff9bccee 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new 2fcd745b9a 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 59f2a2a954 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new c71ba2f0be 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 2f277edcf4 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 17b18a8f3a 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 8ce3539900 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new 643bd89323 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new afc66c42b8 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 6268222a01 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new e3dc9578c4 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 4066c2e242 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 1a484e3690 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new c73d8335f4 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 45407460a5 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 7affba5982 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 71c4b0b62b 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 918274dff3 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new de28b273d9 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 7e0a184a8e 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 4db1bee013 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new d21f8f1e44 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new 0a9fc90078 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new cb8e930ad1 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 91f58f9fed 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new f24b3f0e75 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new e967fd6612 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new 7f4989fa8a 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 013d65e773 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new cf1b11f5b7 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new d70a5b8d37 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 00e888cdbd 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new eef5077994 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 7fecda589b 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 6d9b497376 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new ba2e3b9964 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new b6932e79e9 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new dae7a1ecc9 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 0468ef2100 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 0c230f0c47 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 01131fd584 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 850c94b83f 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new c3bb00e049 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 8359343e46 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 696f853bc5 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 04147220b1 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new a4f345a305 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 0228b10f79 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 4f6afb4c5f 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new e6348b63ba 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new c6ad5829b6 213: force: #24: 1: Success after binutils: 2 commits new bd1b377d36 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 0dc81df90b 215: onsuccess: #26: 1: Success after binutils: 10 commits new b9aa09c998 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new e617598dab 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new d5e90a78cf 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 986f379096 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new c5d0144c87 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 0562c149db 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 41dd761de8 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new fbfa5fe787 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 029968810d 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 23833dce0c 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new f37d2e661e 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 54f4c64683 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 0222ae3840 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 27b2b5abd0 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 608e0a1a60 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 3d4f08871e 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new e62a9fa803 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 097b4a8735 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new fce33d35cf 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 60d123b520 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 855b3dd410 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...]
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 (624918485e) \ 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 2036 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 48776 -> 48956 bytes 04-build_abe-gcc/console.log.xz | Bin 236528 -> 236776 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8500 -> 8492 bytes 07-build_abe-glibc/console.log.xz | Bin 232360 -> 232268 bytes 08-build_abe-gdb/console.log.xz | Bin 46900 -> 46788 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3800 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2164 -> 2164 bytes 11-check_regression/console.log.xz | Bin 4840 -> 4928 bytes 11-check_regression/results.compare | 8 ++--- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 38 ++++++++++----------- 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/changes-list-long.txt | 52 ++++++++++++++--------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++++++++----------- manifest.sh | 36 ++++++++++---------- sumfiles/binutils.log.xz | Bin 62744 -> 62732 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100960 -> 100584 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132360 -> 132320 bytes sumfiles/ld.sum | 4 +-- 30 files changed, 101 insertions(+), 101 deletions(-)