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_gcc/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 2b5c8e647c4 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards af7701cb79b 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 39aa92e7841 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 4e10de0f3e9 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards eebaf00fce5 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards b401fa6fd54 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards fd6255a3816 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards f0c5bd0cebc 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 8e285d2b40e 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards f3f00347288 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 7c4eef0de58 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 14c8b8c9157 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 57391874701 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 432889a3cb6 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 5ae9f07caff 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards db75282f4de 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 9ad0e0a391b 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 61525af08e4 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards d602a011441 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 1c37b78a235 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 10bcc264e09 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 4eedd886f5a 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards 2a6da2905aa 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 6dd2ba7521c 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 06ff36b79e5 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards 0f02e9dc524 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards 0b8898b31c7 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards a5917158442 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards 8a6b02b67e5 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards e0e7a8145db 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards 048d1220fd8 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 4ba045611ff 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards 1d700e3ff46 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 0cb3c2c9b54 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards a6cd6e7adea 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards d702b755882 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards e6683904ae4 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards f888f46497e 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards 590c2fb3a1c 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards 2a82010b10d 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards d5dbb7432e0 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards 62d45f5ff65 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards e3822d6ee61 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 9fa22068e6b 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards b090c004b41 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards a5ef0f57551 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards ee8db28cd9b 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards 5d3a4070c7a 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 8dca494790a 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 28fed67ed63 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 3441615eda1 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards a2fb86a7965 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 9547056e2aa 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards 0b78bef6fd7 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards 04f37392192 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards 2b273d28911 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards 6f27b100006 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards 4a93a4dd38f 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 95f971f86f1 152: onsuccess: #903: 1: Success after linux: 22 commits discards bef793a95b5 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 6d6ce7bd048 150: onsuccess: #900: 1: Success after gcc: 11 commits discards b18804750d7 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 93e5e4b82a0 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards d7853145cff 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards b52a3b5fb34 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards dd09e099ae2 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 94e51fb9321 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards 6d67bb214fb 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards 379d57dbfdd 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 34c5ca53878 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards 7f67d5f86a7 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 5133c9957ab 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards fbe46a2d3d5 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 155ce446137 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 8003caaafdd 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards c34f0459a54 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 89fab4dbae4 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards 04afdf4c4a2 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 52cab16e047 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 793c521d111 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards 3ddd8788d38 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards b2e42d5544e 129: onsuccess: #878: 1: Success after linux: 3008 commits discards df6f4c3f584 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 0f88d510af3 127: onsuccess: #874: 1: Success after linux: 219 commits discards b9aed14f295 126: onsuccess: #873: 1: Success after glibc: 2 commits discards d6359e15eed 125: onsuccess: #871: 1: Success after binutils: 26 commits discards a7eca1b2bc0 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 24914f1b733 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards fe517d49da2 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards a5fae5b2b20 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards 0dd2c60ed3b 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards f5895333be2 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards 1b7556f5050 118: onsuccess: #863: 1: Success after linux: 12 commits discards 22cf1a57fb5 117: onsuccess: #861: 1: Success after binutils: 18 commits discards ebc034d8ac1 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards ccae0987ee3 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards f762959ab02 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 0edfab3138b 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 61e47ba32e6 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards dbd56133254 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards b7572abbb8b 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 18ab1ba54a5 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new b3dc5356e01 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new a96210dba86 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new ed9de8ea2b9 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new bc8a738325f 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 6f8af3fc31d 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 082434b8b13 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 26624e79579 117: onsuccess: #861: 1: Success after binutils: 18 commits new ab61c166300 118: onsuccess: #863: 1: Success after linux: 12 commits new 6fbd94166a6 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new ba362d623ba 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new 2be9e0467a5 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new c767acea444 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new 1b0647c1fbf 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 9b2070e5003 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new fff188d8199 125: onsuccess: #871: 1: Success after binutils: 26 commits new 2ee541dde6f 126: onsuccess: #873: 1: Success after glibc: 2 commits new 96a47e08fe9 127: onsuccess: #874: 1: Success after linux: 219 commits new ea2224e2317 128: onsuccess: #876: 1: Success after binutils: 12 commits new 6fe6f6abd5b 129: onsuccess: #878: 1: Success after linux: 3008 commits new af750bef152 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new a6db1d2557a 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new 82086f0e056 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new f60f2e8e877 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new b4a9cba905d 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new 7bedd33cdfd 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new d3fbb1e7752 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 62896443ac8 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new f34b666c8f7 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new dfe70737b69 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 06c2d876925 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 115ae7de91c 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new ac4c5137de3 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new d6d907e6b0e 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new b90a54a2be8 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new de9762160b7 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 2b0b490fd07 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new 774c57e934c 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new 0c106e93e83 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new 6e1cda02b2a 149: onsuccess: #899: 1: Success after binutils: 15 commits new b2fe724c565 150: onsuccess: #900: 1: Success after gcc: 11 commits new 2d6e7ba84ff 151: onsuccess: #902: 1: Success after glibc: 8 commits new aea210ee4be 152: onsuccess: #903: 1: Success after linux: 22 commits new d41f9e3245a 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 904dd05a505 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new 873e5264fbd 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new 3051efdba17 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new b7f1c08d15d 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new 192b8110621 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new 7333907ec67 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new efe795e27a7 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 5586d27b9f2 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new d8fa184a6e1 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new bbb179797fc 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new ac1b597f03f 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new c2abb710ea2 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new e5efbd52a0a 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new aed90a14798 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 72efe2840d1 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 9fb4f434dc3 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 8798ca71792 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new 504c397e20f 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new ff1101394f3 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new 432174c5420 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new fea98006e6f 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new e5688755ecf 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new af1cf22ae0d 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 852898e8a4b 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 40b4a5bc9ec 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new f74405ee1db 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new 725f45305c5 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 794ff8e8ea7 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new 18629f1fe4b 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new 3746aaec019 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new a7d918ba1a9 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new b94274e18da 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new cb5b9341304 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new e83c39afcbc 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new e00618554f1 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 137cd9c6574 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new feaf3b3592e 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new fba215b02ef 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 49064ec2658 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 4138c7cfd80 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new b876cc63d76 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new fef1d2e0805 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 8fa81f68515 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new a918773e390 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 724b568fdf0 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 3967f3929e8 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new fa82429f01e 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new b5694d5dd76 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 07bee05813d 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 244c87ce973 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new d520b6da760 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new cd31f2b5b48 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new d9f8f91c7b8 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 30352878910 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new b4865b4b638 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 619d9d33f31 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new e73ccaefe3c 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 25a256bd4cb 211: onsuccess: #16: 1: 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 (2b5c8e647c4) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]
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 1772 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 39300 -> 38712 bytes 04-build_abe-gcc/console.log.xz | Bin 205408 -> 204068 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9728 -> 9148 bytes 07-build_abe-glibc/console.log.xz | Bin 246288 -> 247032 bytes 08-build_abe-gdb/console.log.xz | Bin 39072 -> 38368 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3760 -> 3820 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2828 -> 2964 bytes 11-check_regression/console.log.xz | Bin 7100 -> 7924 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 8 + 11-check_regression/mail-body.txt | 28 ++ 11-check_regression/results.compare | 27 +- 11-check_regression/results.compare2 | 360 ++++++++++++++++--------- 11-check_regression/results.regressions | 28 ++ 12-update_baseline/console.log | 42 +-- 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 | 30 ++- mail/mail-subject.txt | 2 +- manifest.sh | 36 +-- results | 28 ++ sumfiles/g++.log.xz | Bin 3709808 -> 3684076 bytes sumfiles/g++.sum | 197 +++++++++----- sumfiles/gcc.log.xz | Bin 3206204 -> 3228384 bytes sumfiles/gcc.sum | 461 ++++++++++++++++++++------------ sumfiles/gfortran.log.xz | Bin 1082984 -> 1077696 bytes sumfiles/gfortran.sum | 44 +-- sumfiles/libatomic.log.xz | Bin 2296 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 235672 -> 235272 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2684 -> 2684 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 447296 -> 446408 bytes sumfiles/libstdc++.sum | 14 +- 43 files changed, 897 insertions(+), 449 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions