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 bf9b9fa0ed 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ddb599ed6c 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards b6cd543e7a 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 116c09eda2 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 52ea12b0f6 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 0adf260977 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 67939c8edf 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 66bd22b4b2 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards d615450588 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 3868c44d57 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards a0895c34e9 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 83f1bd33bc 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 932ac7c82d 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 8a2f328e2b 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 0e5e06fec3 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards ae97731e37 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 84c8c16fbd 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 6e13d78574 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards e7b789339c 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 9a98673f70 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 25e0a369f0 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards d2457701c5 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 220fa364af 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 20c03e74a0 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards aef896e716 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 680e1057b9 215: onsuccess: #26: 1: Success after binutils: 10 commits discards fa64094eeb 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 0e8d7bc4d3 213: force: #24: 1: Success after binutils: 2 commits discards 049a81286c 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 61c74c675e 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 88fe4a673d 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards a294e1b659 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards ed5179337f 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 5d87045586 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 23db40b4ea 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards ed0e39ec61 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 5bd35ce42b 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 9de25bfde2 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards f86f9f30df 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 97968509b2 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 7135768a9b 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 48d583cfa3 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards f9f1447d2b 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards e7e4c107a2 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards a976331a9d 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 78f7a6f34e 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards b752d7a19a 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 9db2d1e504 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 74a21b9ef0 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards b5bcd97720 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards 9cb12d6527 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 501c9ccb06 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards 27b03afd6b 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 72c7c78b44 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards a4340cf67c 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 9960552ec0 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards c96489bff2 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards c14b5e55cc 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards 1205ddc8cc 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 0a0da23a3b 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 5c69074d3e 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 6798ebd950 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 10caa398c3 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards bd29cc8a58 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards ced52c59b5 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 511d687694 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards f8ce44b3c0 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards f9b1d1ed4b 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 61550da27e 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 2de10cdac2 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards e9393eb991 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 6fc3cf0bf6 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards 707eb64f85 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards d5b6a4a503 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 9d19df52fd 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 015a843794 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards e4f3e4b045 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 4dd09eff08 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards 134b2b8444 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 7422c53162 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards f26d48c6b9 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards a758d65e0f 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 56a60a2f85 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards 7cf5dcffa7 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards dae564e509 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 55d37f5700 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards 9c959f4f63 154: onsuccess: #583: 1: Success after linux: 10 commits discards 9e79515355 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 0e15d1b210 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 10912f3f2f 151: onsuccess: #579: 1: Success after binutils: 21 commits discards bc09e9b646 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 507d808f82 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 5cd296cbef 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards cd8109c734 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 0a795ccae9 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards 25e16346e9 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards 4500a46371 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards 8d5cfb94fe 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 8ebf7a0849 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits discards 2a5825d7cd 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] discards 65ea3b6a57 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 37cda1f4e6 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new e94601dd22 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] new f2f5fec18b 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new b30d9c7880 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 91240193b5 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new 2c516a0623 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new fa2188abdb 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new d8309a1066 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 2d93df57ed 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new bbb074f078 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new f162aa8884 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 093b3e289f 151: onsuccess: #579: 1: Success after binutils: 21 commits new e0e992cd6b 152: onsuccess: #580: 1: Success after gcc: 6 commits new 4852711acc 153: onsuccess: #582: 1: Success after glibc: 9 commits new 91a5cd02fb 154: onsuccess: #583: 1: Success after linux: 10 commits new 6ee9d3c2b2 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new db70b4cd57 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 8819d65d22 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new 0b76a41507 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new 753b7df644 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new dae0649b73 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new 78956fb1d9 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new c1df2d488b 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 2d2ab7c133 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new 6eea178e5f 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 0df37d1a48 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new b9dcbd6757 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 10f038d373 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 00cad6760f 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 4604ab6283 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new 969c685859 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 7d2f7ed53c 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 3827c50ad4 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 868efc6cf5 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new de7c1d6868 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new cad449ac9b 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new 73591b7a99 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 12654d9130 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 0eea2e7e74 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 73a29547e4 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new acebc9d23a 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new e3f58872bd 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new c2f5107138 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 0b123df3ad 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new d7187a3009 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new 5c2014185a 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new 52e19376fb 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new e755b64e79 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new c048939dbf 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new f5e88cbb0c 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new bbe8f64847 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 7058b43675 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new 1ef2e85c7f 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 8c45c2504d 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 2233497969 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 15f60b470b 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new d0e68bd1ed 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 8179713ff7 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 2260188c7b 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 9b6e7ddff9 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new fdc18df394 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 748acc67ee 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new f277c961e5 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 36ffa6656d 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new fcbccd2a43 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 30ef3c8bcc 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 9eaa02c29e 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 3fc874ef75 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 1cbcb237e5 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 64e10a8f70 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new c2ab2af6f8 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new b2e55c361d 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 918ec07d7d 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new a00dcc56ab 213: force: #24: 1: Success after binutils: 2 commits new f62cdaf4b6 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 08eec65b4e 215: onsuccess: #26: 1: Success after binutils: 10 commits new 0b7246ae88 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 50e412041a 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new c8296e8c9b 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 5700543973 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 38482a840c 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 5351a51cd1 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 404f6ac81d 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 3484a295a7 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 097be2801e 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 2648694dca 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new b84ff57ebe 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 474881098f 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 5d6eba6cb2 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new f1f26b5de3 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 2b316df495 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new f345abcb48 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new ffd4873673 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new d7e5796aab 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new cd2ebc5b0e 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 108f803c79 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 05d4d88ce9 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new a3d98556af 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 3f6c547ad8 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 6968f2b058 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 3a6b07073e 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 44de160fb7 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...]
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 (bf9b9fa0ed) \ 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 2052 -> 2060 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 49328 -> 48772 bytes 04-build_abe-gcc/console.log.xz | Bin 235328 -> 236072 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8616 -> 8800 bytes 07-build_abe-glibc/console.log.xz | Bin 232940 -> 232096 bytes 08-build_abe-gdb/console.log.xz | Bin 47748 -> 47384 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3804 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2592 -> 2172 bytes 11-check_regression/console.log.xz | Bin 2000 -> 1320 bytes 11-check_regression/results.compare | 10 +++--- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 38 ++++++++++----------- dashboard/dashboard-generate.sh | 17 --------- dashboard/dashboard-push.sh | 7 ---- .../squad-vs-first/score/results-functional.json | 1 - git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/dashboard-push.sh | 7 ---- jenkins/notify.sh | 2 +- {11-check_regression => mail}/results.compare | 10 +++--- manifest.sh | 36 +++++++++---------- sumfiles/binutils.log.xz | Bin 62196 -> 62180 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100580 -> 100628 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132284 -> 132300 bytes sumfiles/ld.sum | 4 +-- 32 files changed, 60 insertions(+), 94 deletions(-) delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh delete mode 100644 dashboard/squad-vs-first/score/results-functional.json delete mode 100755 jenkins/dashboard-push.sh copy {11-check_regression => mail}/results.compare (63%)