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 d2e4b0b410d 223: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 441bf372a75 222: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards f388f5b9aea 221: onsuccess: #27: 1: Success after binutils/gcc/linux/gl [...] discards c8a0ec27f20 220: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards d41ac80ecb9 219: onsuccess: #24: 1: Success after binutils/gcc/linux/gd [...] discards c75b73dd4d0 218: onsuccess: #23: 1: Success after binutils/gcc/linux/gd [...] discards 8ed54f4b6c3 217: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] discards b0ae333d7ad 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] discards 5d16290cff3 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 5ccff2b38e4 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards f95d3013c96 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 7f5fb54f59e 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards d29259f4edc 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards fc388ac6685 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 1939b3f050f 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards f594b1dee93 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 2337823fce3 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 2ca30455a32 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 3a4325bde88 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 111d98b02b9 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards a8f7ba540b2 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 0ee4da442a2 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards faaccf555a7 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 7ced618af1f 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 92783db3869 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 0d9afc7ab83 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards da25aa609a7 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards c55f28ef6f5 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 553f0e111c4 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards a36f142d5d1 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards a1ac618a53e 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 1f308232458 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 584ce986496 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards f6d78c02377 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 11d58e7e21a 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards 151c924d208 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards fe8f6ba1b65 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards c4b3e0edefa 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards de43f546559 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards 698f9bc7106 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards e34cd11810a 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards 8aa03d67601 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards 356d9dc70fb 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards 992ec2ed1ba 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 5fef94ad2cf 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards 5ed5bb60825 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 0c184e11458 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 1c4cdfa58c1 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards cf76e861a1d 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 3de9e49faf3 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards c3dde12a55c 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards 58eeb21332b 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards 0d77b3b8406 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 8d28a6a88ec 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards 1369c4bcdb5 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards ae073edfc38 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 47721cbc1b0 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards ebce4b5b4c9 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards f0a9e0504d2 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 26b0f662ed4 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards 94e699d48ae 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards a6202c03682 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards a7139fc26b9 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 0884f61d49c 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 62916e98783 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 3d944c79d8a 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards cde8d237416 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards a90f8a95058 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards 3c5798f4c5a 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards 96e5dfb293f 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards 6398a01d140 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards c95265ec7f3 152: onsuccess: #903: 1: Success after linux: 22 commits discards f347dca3d37 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 24462e59bae 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 3d8df75177c 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 1ec37a078fd 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards da65aae5bae 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards f50be1b6ef8 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards 9c745a463c7 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards cc9d9a0f7eb 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards c6c08579a70 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards adb97dac0dd 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 9532ae9f776 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards 0ff34c7c2b2 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 61b4dccd369 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 8495b37b9a8 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards e93a3de87bc 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 3b52f40e6d4 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards abcf2814f23 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards f4f75aa07d7 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards 21b93c36ee3 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 467ee4225bc 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 25ce3949173 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards d12d1e90d69 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards f7a5f652397 129: onsuccess: #878: 1: Success after linux: 3008 commits discards e8e952c6ab2 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 9afc5bb187d 127: onsuccess: #874: 1: Success after linux: 219 commits discards 7ae7b4452bc 126: onsuccess: #873: 1: Success after glibc: 2 commits discards c955a8d9a93 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 4d551cd3f86 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards e64b494251c 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 6f8f4a4cb91 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 75e81e0d46d 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 681ca85b192 125: onsuccess: #871: 1: Success after binutils: 26 commits new 0cb9bbf259b 126: onsuccess: #873: 1: Success after glibc: 2 commits new a0a7688fcbd 127: onsuccess: #874: 1: Success after linux: 219 commits new 2ac8defa574 128: onsuccess: #876: 1: Success after binutils: 12 commits new b432c9452a8 129: onsuccess: #878: 1: Success after linux: 3008 commits new 3a49b7c8560 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new bb28af186e5 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new aa8c2dfba7a 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 0ccc5449967 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new d3fdcb2c78e 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new a56746404ab 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 99854268f50 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 936699abd4c 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 450457acee0 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 315d847cc6b 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new aad57280df0 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 4c1d0029726 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new 2001dca86d1 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 6473a3b56ca 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new df2f8301e79 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new b206f76a0a7 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new acae41bb12c 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new ebe85eedcf3 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new bf9b50af429 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new 544626a6d3a 149: onsuccess: #899: 1: Success after binutils: 15 commits new 60939f0eeb4 150: onsuccess: #900: 1: Success after gcc: 11 commits new ceb605be57b 151: onsuccess: #902: 1: Success after glibc: 8 commits new 6727389ac81 152: onsuccess: #903: 1: Success after linux: 22 commits new 4c3142e0cd4 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 514d9b2bca6 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new a8d36a02ec8 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new b69877d4f18 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new 9ec12e884a4 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new 88470bdc1d0 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new 9c825c1d104 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 24ed9979cbb 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new f2abd032c87 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new ffff27db90d 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 60f81216be5 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new b10c29e90ed 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new 14490aa442b 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 5e99cad46c2 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 588b04dc074 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new b1d4be8acbf 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new f5f7fcf0f30 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new a1852bf843e 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new 15a8bc2414b 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new dad69aa26ca 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new 8f8372addd3 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new ab80e475530 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new 0fd6a0e2eda 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new d3df604f602 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 1eb03330c14 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 72362e93844 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new e14e8153be2 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new 412de42412d 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new e4d81570d7d 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new 79ff15ca3cc 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new d2482a09422 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new 36e5988ca43 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new d6bd15c53a6 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new af65481e075 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new 52e147c357c 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 095447ee56d 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new af58649d488 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new 63084179246 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 6ef68b75cc6 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 7559ee9edbd 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 7ba79c309e9 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new b0b970c006d 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new c734a2dddb4 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new eb379a316f1 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 79fdfa509c0 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new ce58cd274e9 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 954547a6301 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new bf6f039bb3a 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 0fa077c8c25 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 49f76e41e0a 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 59bf472f713 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 5809fc382a8 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 4f53b981226 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new bb1823f2f66 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new f5394ced0fd 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 40d6167bc54 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 7755595b3e6 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 26ff1758f0d 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new df5a72f2479 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new d6b9f33e492 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new cf0df260b72 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new f05b0584bde 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 84acb76c803 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 01745c8aa11 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] new d33626ca193 217: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] new 3ea95c61108 218: onsuccess: #23: 1: Success after binutils/gcc/linux/gd [...] new 0c5a327ba81 219: onsuccess: #24: 1: Success after binutils/gcc/linux/gd [...] new 335c19b1af3 220: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new 58b5918a42c 221: onsuccess: #27: 1: Success after binutils/gcc/linux/gl [...] new 49cdf36c652 222: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 928f45aee25 223: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new e286a3779ab 224: onsuccess: #30: 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 (d2e4b0b410d) \ 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 2120 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 35104 -> 35548 bytes 04-build_abe-gcc/console.log.xz | Bin 205456 -> 204448 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8952 -> 8416 bytes 07-build_abe-glibc/console.log.xz | Bin 242832 -> 243360 bytes 08-build_abe-gdb/console.log.xz | Bin 35116 -> 34988 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3808 bytes 10-build_abe-check_gcc/console.log.xz | Bin 10548 -> 10072 bytes 11-check_regression/console.log.xz | Bin 10756 -> 4352 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 1868 +----- 12-update_baseline/console.log | 50 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.sep.xz | Bin 66112 -> 73840 bytes sumfiles/g++.log.xz | Bin 3693960 -> 3722688 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 11039 +++++++++++++++++--------------- sumfiles/gcc.log.sep.xz | Bin 63060 -> 78484 bytes sumfiles/gcc.log.xz | Bin 3214604 -> 3216132 bytes sumfiles/gcc.sum | 2 +- sumfiles/gcc.sum.sep | 6145 +++++++++--------- sumfiles/gfortran.log.sep.xz | Bin 24744 -> 21076 bytes sumfiles/gfortran.log.xz | Bin 1083172 -> 1086852 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 2596 ++++---- sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 235668 -> 235488 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2684 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 19232 -> 23516 bytes sumfiles/libstdc++.log.xz | Bin 450948 -> 448264 bytes sumfiles/libstdc++.sum.sep | 20 +- 43 files changed, 10257 insertions(+), 11537 deletions(-)