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 25a256bd4cb 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards e73ccaefe3c 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 619d9d33f31 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards b4865b4b638 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 30352878910 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards d9f8f91c7b8 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards cd31f2b5b48 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards d520b6da760 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 244c87ce973 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 07bee05813d 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards b5694d5dd76 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards fa82429f01e 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 3967f3929e8 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 724b568fdf0 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards a918773e390 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 8fa81f68515 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards fef1d2e0805 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards b876cc63d76 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 4138c7cfd80 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 49064ec2658 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards fba215b02ef 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards feaf3b3592e 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 137cd9c6574 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards e00618554f1 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards e83c39afcbc 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards cb5b9341304 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards b94274e18da 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards a7d918ba1a9 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards 3746aaec019 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards 18629f1fe4b 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards 794ff8e8ea7 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards 725f45305c5 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards f74405ee1db 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards 40b4a5bc9ec 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 852898e8a4b 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards af1cf22ae0d 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards e5688755ecf 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards fea98006e6f 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards 432174c5420 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards ff1101394f3 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards 504c397e20f 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 8798ca71792 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards 9fb4f434dc3 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 72efe2840d1 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards aed90a14798 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards e5efbd52a0a 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards c2abb710ea2 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards ac1b597f03f 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards bbb179797fc 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards d8fa184a6e1 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 5586d27b9f2 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards efe795e27a7 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 7333907ec67 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 192b8110621 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards b7f1c08d15d 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards 3051efdba17 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards 873e5264fbd 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards 904dd05a505 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards d41f9e3245a 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards aea210ee4be 152: onsuccess: #903: 1: Success after linux: 22 commits discards 2d6e7ba84ff 151: onsuccess: #902: 1: Success after glibc: 8 commits discards b2fe724c565 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 6e1cda02b2a 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 0c106e93e83 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards 774c57e934c 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards 2b0b490fd07 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards de9762160b7 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards b90a54a2be8 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards d6d907e6b0e 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards ac4c5137de3 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 115ae7de91c 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards 06c2d876925 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards dfe70737b69 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards f34b666c8f7 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 62896443ac8 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards d3fbb1e7752 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 7bedd33cdfd 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards b4a9cba905d 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards f60f2e8e877 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 82086f0e056 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards a6db1d2557a 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards af750bef152 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards 6fe6f6abd5b 129: onsuccess: #878: 1: Success after linux: 3008 commits discards ea2224e2317 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 96a47e08fe9 127: onsuccess: #874: 1: Success after linux: 219 commits discards 2ee541dde6f 126: onsuccess: #873: 1: Success after glibc: 2 commits discards fff188d8199 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 9b2070e5003 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 1b0647c1fbf 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards c767acea444 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards 2be9e0467a5 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards ba362d623ba 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 6fbd94166a6 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards ab61c166300 118: onsuccess: #863: 1: Success after linux: 12 commits discards 26624e79579 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 082434b8b13 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 6f8af3fc31d 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards bc8a738325f 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards ed9de8ea2b9 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards a96210dba86 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards b3dc5356e01 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 24a54ec1c45 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 43fd4b35c79 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new e08bf424b7b 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new b30f4c23dc6 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 91d44c322d6 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 67d5e4e6e4f 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 7cfb68534d1 117: onsuccess: #861: 1: Success after binutils: 18 commits new 8219f0e9a20 118: onsuccess: #863: 1: Success after linux: 12 commits new 34dfe7b7a29 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new dd2846991f9 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new ee35ae91239 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new 98fac037c8a 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new 861c7619eb7 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new c9931f064f2 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new f855cd73637 125: onsuccess: #871: 1: Success after binutils: 26 commits new f2f395739dd 126: onsuccess: #873: 1: Success after glibc: 2 commits new e63b134d8ac 127: onsuccess: #874: 1: Success after linux: 219 commits new d46eb83c2a8 128: onsuccess: #876: 1: Success after binutils: 12 commits new 9c0a06005d4 129: onsuccess: #878: 1: Success after linux: 3008 commits new 2d58ea26161 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new b6d9c36f2dc 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new db8f48c119c 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new f0b65f41c5f 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new ccc106a1ae0 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new 34dd294ee54 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new b8c46a25898 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 80d4031f6c4 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 44e85ab2a0e 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 97f234e28b2 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new a13b786943b 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 46ceed6840d 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new 5869ee0a94f 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new eb24dab7d92 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new 253f7818e3a 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new d05e1d6791c 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new f9f72368dc4 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new baa2f222437 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new 6fde411e269 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new 5e0d5708d48 149: onsuccess: #899: 1: Success after binutils: 15 commits new 2c965f3fa0c 150: onsuccess: #900: 1: Success after gcc: 11 commits new 70e3e1fe17b 151: onsuccess: #902: 1: Success after glibc: 8 commits new a436e1c0d34 152: onsuccess: #903: 1: Success after linux: 22 commits new e236959568a 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new f591eeadc2d 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new d9de1a2175e 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new f6032c4fce1 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new 466ca1a607d 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new 61be27bf4df 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new ce12168c973 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 2492d65f903 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 6382e382e62 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 25d196e86da 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new cae4b82cf3b 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 455b1238513 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new cea73aab284 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 2c1be87a4b3 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new b75979bbd5f 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 602c97a52aa 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 0452aeb30c1 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 03086cdb51d 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new c047f2657e9 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 37040ef1a31 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new 8a04402235c 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new 819834ddb55 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new 39addfe042e 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 2ebec8e9a2f 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new b1773e38da9 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 84dd9248b2d 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 342f26b0b67 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new 5e0fe197943 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new d53cb1a3317 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new dd7dbdad58c 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new 5087c1916c4 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new 24d31b283b8 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new b63d48bb8b6 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new 51df8e67135 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new cd1d5f11da9 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 9348714f234 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 35c1e96d66d 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new 640919a0bb7 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 597b1dc39f2 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 01b829f4daa 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new dda93e93976 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 043304aa4de 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new e357a156157 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 901d0045a2a 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 5a7326135dd 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new b5177a8b970 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new cea3b121a7e 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 720886a531d 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 22495f6fb60 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new ceaafad9f37 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 301217f3cd0 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 6f0622c570f 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new be0ce0bd339 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 86481dc99ba 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 9947fc91bf8 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 0d5d5b57b28 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 19317209603 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 48e7cd5d77a 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 1307f79a6a0 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new f16224650a6 212: onsuccess: #17: 1: 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 (25a256bd4cb) \ 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 1760 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 38712 -> 39092 bytes 04-build_abe-gcc/console.log.xz | Bin 204068 -> 204756 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9148 -> 8768 bytes 07-build_abe-glibc/console.log.xz | Bin 247032 -> 246824 bytes 08-build_abe-gdb/console.log.xz | Bin 38368 -> 38264 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3768 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2964 -> 2648 bytes 11-check_regression/console.log.xz | Bin 7924 -> 6240 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 8 - 11-check_regression/mail-body.txt | 34 ++-- 11-check_regression/results.compare | 27 +-- 11-check_regression/results.compare2 | 278 +++---------------------- 11-check_regression/results.regressions | 28 --- 12-update_baseline/console.log | 38 ++-- 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 | 36 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 +-- results | 28 --- sumfiles/g++.log.xz | Bin 3684076 -> 3676480 bytes sumfiles/g++.sum | 106 +++++----- sumfiles/gcc.log.xz | Bin 3228384 -> 3251420 bytes sumfiles/gcc.sum | 346 ++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1077696 -> 1078752 bytes sumfiles/gfortran.sum | 41 ++-- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 235272 -> 235164 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2684 -> 2684 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 446408 -> 444112 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 374 insertions(+), 677 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions