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 44de160fb7 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3a6b07073e 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 6968f2b058 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3f6c547ad8 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards a3d98556af 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 05d4d88ce9 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 108f803c79 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards cd2ebc5b0e 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards d7e5796aab 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards ffd4873673 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards f345abcb48 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 2b316df495 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards f1f26b5de3 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 5d6eba6cb2 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 474881098f 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards b84ff57ebe 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 2648694dca 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 097be2801e 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 3484a295a7 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 404f6ac81d 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 5351a51cd1 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 38482a840c 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 5700543973 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards c8296e8c9b 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 50e412041a 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 0b7246ae88 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 08eec65b4e 215: onsuccess: #26: 1: Success after binutils: 10 commits discards f62cdaf4b6 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards a00dcc56ab 213: force: #24: 1: Success after binutils: 2 commits discards 918ec07d7d 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards b2e55c361d 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards c2ab2af6f8 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 64e10a8f70 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 1cbcb237e5 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 3fc874ef75 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 9eaa02c29e 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 30ef3c8bcc 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards fcbccd2a43 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 36ffa6656d 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards f277c961e5 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 748acc67ee 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards fdc18df394 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 9b6e7ddff9 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 2260188c7b 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 8179713ff7 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards d0e68bd1ed 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 15f60b470b 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 2233497969 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 8c45c2504d 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 1ef2e85c7f 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 7058b43675 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards bbe8f64847 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards f5e88cbb0c 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards c048939dbf 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards e755b64e79 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards 52e19376fb 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 5c2014185a 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards d7187a3009 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards 0b123df3ad 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards c2f5107138 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards e3f58872bd 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards acebc9d23a 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 73a29547e4 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 0eea2e7e74 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards 12654d9130 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 73591b7a99 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards cad449ac9b 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards de7c1d6868 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 868efc6cf5 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 3827c50ad4 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 7d2f7ed53c 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 969c685859 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 4604ab6283 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards 00cad6760f 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 10f038d373 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards b9dcbd6757 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 0df37d1a48 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 6eea178e5f 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 2d2ab7c133 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards c1df2d488b 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 78956fb1d9 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards dae0649b73 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards 753b7df644 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 0b76a41507 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards 8819d65d22 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards db70b4cd57 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 6ee9d3c2b2 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 91a5cd02fb 154: onsuccess: #583: 1: Success after linux: 10 commits discards 4852711acc 153: onsuccess: #582: 1: Success after glibc: 9 commits discards e0e992cd6b 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 093b3e289f 151: onsuccess: #579: 1: Success after binutils: 21 commits discards f162aa8884 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards bbb074f078 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 2d93df57ed 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards d8309a1066 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards fa2188abdb 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards 2c516a0623 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards 91240193b5 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards b30d9c7880 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards f2f5fec18b 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits discards e94601dd22 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] new a71d9bad90 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] new 0bd71d8e02 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new 6209fcea41 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 6c5649d968 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new f615575c8c 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new 8258f95e21 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new 3a54fa9101 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 82052eda9e 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new f2c84d1acd 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 112a3d6e1b 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new ad31f1c21c 151: onsuccess: #579: 1: Success after binutils: 21 commits new 3a8fa5cc0e 152: onsuccess: #580: 1: Success after gcc: 6 commits new d882a95dc0 153: onsuccess: #582: 1: Success after glibc: 9 commits new f92055351b 154: onsuccess: #583: 1: Success after linux: 10 commits new aaa89e0e5d 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 0e117178b2 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new f08395013a 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new 05baf78a52 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new c36f598207 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 1b20468d6a 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new da76bd7471 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new a85473f3f4 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 9a6ca6d7a6 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new 5c91b4ca0e 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new bf33778cc6 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 6f2b9bba32 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 3d56772cc8 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 5e0e06c109 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new ea234cee94 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new ddd2f3a476 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 3f48d95980 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 2660f88273 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 3755ef42de 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 7838c8ce2f 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new c39f8f60d0 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new a07bd7b283 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new f1de6dad0e 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 1dde72d429 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 6d29e56d19 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 9019102154 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 4848676c32 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new d1b05ee795 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 133299e0ef 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new a87bf5a265 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new 419c853bba 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new ead1f49f5c 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 9a9dbe6876 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new ec4a564f73 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 2f8e288843 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new a5cde1c66d 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 45100fd6cb 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new 9e7aab4fdc 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 6b9ee10037 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 7e5eaef61b 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 7315dc35a7 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new b33f8f7120 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 4fdfadcade 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 5c198c0a4f 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 3c976c10c7 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 9cc6dabed1 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new b40b6da6e2 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new d03eebdd27 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new d29d3a2a86 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 70fda19c98 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 76c124c68f 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new ed355216e3 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 995bffea3b 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 6bcae5b003 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new ccdefef1c0 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 4400a7b83b 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new fcad16e66e 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 7fc2c5be82 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 9620dee8d6 213: force: #24: 1: Success after binutils: 2 commits new 8037c2ac61 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 432eab3365 215: onsuccess: #26: 1: Success after binutils: 10 commits new 7ccba97783 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new de9c43b032 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new da00606b6f 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 5d2462b66e 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new c880d034da 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new b85b4fc8a5 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 991fcf2892 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new d7e643f6c5 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 7d78ddeafc 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new f619c230c8 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 4dfd057fc9 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 2dd7948ec0 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 5296bc0fcd 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 3e8fe27916 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 36ce985dfe 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new f96e9411ed 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 037b5457b2 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 61d7cfc36b 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new ae87be290f 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new b24772c6af 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 048d97ac52 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new c667cacab8 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new bf28126c14 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 6bcd1b35ef 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 16f0412a06 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 066eab3d33 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 5b91434f7b 242: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...]
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 (44de160fb7) \ 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 2060 -> 2224 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 48772 -> 48656 bytes 04-build_abe-gcc/console.log.xz | Bin 236072 -> 235724 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8800 -> 8972 bytes 07-build_abe-glibc/console.log.xz | Bin 232096 -> 233072 bytes 08-build_abe-gdb/console.log.xz | Bin 47384 -> 46476 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3808 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2172 -> 2300 bytes 11-check_regression/console.log.xz | Bin 1320 -> 1628 bytes 11-check_regression/results.compare | 15 +++------- 11-check_regression/results.compare2 | 45 +---------------------------- 11-check_regression/results.regressions | 4 +++ 11-check_regression/trigger-bisect | 2 ++ 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 41 +++++++++++++------------- git/binutils_rev | 2 +- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- mail/results.compare | 15 +++------- mail/results.regressions | 4 +++ manifest.sh | 26 +++++++---------- results | 4 +++ sumfiles/binutils.log.xz | Bin 62180 -> 62188 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100628 -> 100644 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132300 -> 132284 bytes sumfiles/ld.sum | 2 +- 30 files changed, 62 insertions(+), 108 deletions(-) create mode 100644 11-check_regression/results.regressions create mode 100644 11-check_regression/trigger-bisect create mode 100644 11-check_regression/trigger-notify create mode 100644 mail/results.regressions