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 542c825371 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 74686a94ec 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards ea7f611b6a 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 9105e4f5fd 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards b548daea55 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards c5094bf867 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 9815fda0de 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 230b98331d 95: onsuccess: #835: 1: Success after binutils: 3 commits discards a9b58fd3db 94: onsuccess: #832: 1: Success after binutils: 5 commits discards dee562e0c6 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 6c789d69c1 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 44f85b7699 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards d0a8515d76 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards de0e7ed6ac 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 4650b30521 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 69606f4f32 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 6de8910eee 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 25350d600f 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 9a7d791fac 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards e851d7c1e5 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards fd9c7dd67a 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards b4293befd4 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 0d1856385d 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards d126e6cf38 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 9ba0507ce8 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 275b43698c 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards ad7003ee2b 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 90f2e14a37 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 3fa2c5f65c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 4f4fda49fc 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 070248922f 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 1ecd899883 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 9db7857684 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards c9c37b1d5e 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 1ab05e8b87 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 673e669279 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 4e1688d34e 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 5483197a74 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards ec602f5fa0 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards e88bba9b91 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 2cd79b8ebf 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards c3841c6ed8 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards a3df40993d 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards e3e67e0081 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 46bf1fa0e4 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 609f27ca18 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards bb6733085f 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards a97a0b91cf 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 40a578b0cb 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 6c13dbdfa0 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 294ace5026 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards e536c9ea30 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards f4b78269a9 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards fb8f25be9f 49: onsuccess: #785: 1: Success after binutils: 12 commits discards f75d570d23 48: onsuccess: #782: 1: Success after binutils: 8 commits discards d81b3e6078 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 74ff3c86c1 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards d38dd8e5e9 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards f90ddf8895 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 2d1203d8a3 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards cc21f650f3 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 1afc206d9a 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards 1e6ef5be2a 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards 878d84e35a 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards 8a0af56acb 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards d6c360b462 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 618dfb578c 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 511a098942 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards 159b7206e1 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards acd93bffe5 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards b75ab67353 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards 77c54cb69b 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards 50470632ec 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards 5339d37c1d 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards 690ad4d291 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards d76d65c3f6 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards e522ab0136 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards 006fefc06b 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards 662a6734f5 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 443b438182 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards d21f16d48c 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 64ad0320f1 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 03c39c6fd0 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 081994ca2d 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1c3d4a2b86 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5bcdc44fa0 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 92104184f5 16: onsuccess: 1: Successful build after binutils: 4 commits discards 08acfdaff3 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5fedfddc0e 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f036af0085 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e3b48ef670 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 091568d807 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f463378b18 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1987156052 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a42de4047f 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 9dd60d73b4 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards cf3ed3347f 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 7984c39d25 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 1cad7a3833 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 30aa0973cd 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 143cceedd9 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new f348979073 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 4e305383e9 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new a744e2945b 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 820c096d57 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 360f240957 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new d055da0d61 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new bb7c2a77f8 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new f9ac8a25b5 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c52e383ff7 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new babdc3e24f 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fc64b540b4 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b961cf32d3 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4008500922 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new eb3733acc5 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 46e770d61e 16: onsuccess: 1: Successful build after binutils: 4 commits new dd0e9e8694 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9b6801d502 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 23e7013aa6 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f9a9a7e1fa 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bd377d7977 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 278aa2e01c 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 58e6585ba8 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 4a41bff458 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 6f6f49cb08 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new e15491788f 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new 1e55c22a2f 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new dbac8a3727 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new 8c90c4f542 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new e9c11279fd 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new 6cb1da5a7e 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new 2d8b8de2dd 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new 97beab0550 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new 02ad3523f0 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new 5f7ca5fbe6 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new 151aa0675c 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new b444605a3d 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new 5120ef8a5c 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new 508fdd906e 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new 984bf64465 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 414ee26008 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 0742c1eabe 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 6769485d2c 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new 04f5ed61b5 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 2ff4ece4ce 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new b49e1442d6 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new a0b219770b 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 94b1480a6d 48: onsuccess: #782: 1: Success after binutils: 8 commits new 192ca53f30 49: onsuccess: #785: 1: Success after binutils: 12 commits new 66eaec6df4 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 074a9a56f7 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 5f5b1c57b8 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new c909221efa 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 4ac8cbc969 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 6eb190649d 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 254bb676f5 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new e37a93db85 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 76230ebac7 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new a5bd5e330a 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 58e0cd5555 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new c312cdd3bb 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new d9330ad12d 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 8a4123f6da 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 5ad3a8e543 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 6ad83501f0 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new e21fdaacd6 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 451e23a9da 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 00f64bbc77 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new a1a9b991f7 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 7d687bb15e 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new f88324098e 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 7ebb5d6e0c 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 09b821d6b8 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new c9f49e297e 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 807d7eee5c 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 394c4ef349 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 56a0131452 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 82ca3839d1 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 6e877311c3 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 55976fa96f 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 34481c3b05 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 37cb8ca0dc 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new c0cf4d4bfd 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new f58ac3ef1c 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 5ab54f4819 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 5ddc199adc 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 4eaf51b755 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new c02e8263bb 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 19eca28185 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 7aafccf583 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new be84b88f36 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 32568b3ce4 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 081fa0f078 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new a1efc2d8c7 94: onsuccess: #832: 1: Success after binutils: 5 commits new c5b3d84293 95: onsuccess: #835: 1: Success after binutils: 3 commits new 89390fc79e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 8dcaeebb6d 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 09d3ad869b 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 48dedfb3b2 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 5bd70d0f45 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new ae322eefb1 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new f3b86bba50 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 1aa97e7877 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits

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 (542c825371) \ 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 1696 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2716 bytes 03-build_abe-binutils/console.log.xz | Bin 39796 -> 39184 bytes 04-build_abe-gcc/console.log.xz | Bin 214372 -> 214444 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8288 -> 8296 bytes 07-build_abe-glibc/console.log.xz | Bin 244648 -> 244028 bytes 08-build_abe-gdb/console.log.xz | Bin 39888 -> 39000 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2836 -> 2684 bytes 11-check_regression/console.log.xz | Bin 8152 -> 6680 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 6 + 11-check_regression/mail-body.txt | 26 + 11-check_regression/results.compare | 25 +- 11-check_regression/results.compare2 | 492 +-- 11-check_regression/results.regressions | 26 + 12-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 26 + sumfiles/g++.log.xz | Bin 3778280 -> 3768964 bytes sumfiles/g++.sum | 167 +- sumfiles/gcc.log.xz | Bin 3304204 -> 3295056 bytes sumfiles/gcc.sum | 4936 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1081064 -> 1080092 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231396 -> 230512 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 455508 -> 446520 bytes sumfiles/libstdc++.sum | 13 +- 41 files changed, 2885 insertions(+), 3005 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