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 8ce28f0640 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards c85ec761f8 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards b049814b7a 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 60d67f0988 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 35a8804204 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards f1015bce93 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 8d3bb6db37 95: onsuccess: #835: 1: Success after binutils: 3 commits discards b1e832e416 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 27b00e5c23 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 187330af3d 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 8bb2901e7f 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 45947a5bad 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards d91c57d56d 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 395c3478ce 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 336d500e24 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 1f251cebe4 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards e1e36ffb36 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 309609b386 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 1ec495e146 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards a3c4fec973 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 50ce8fbb9c 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards b84f861185 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards c02990348d 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 5652f33e98 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards b3e7f332f5 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 15c2e27d28 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards cf737224e3 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 0830c401be 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards aeda5a64c2 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards cdc3c1e946 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 55f2360d8b 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 6ecf6c5d0a 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 581f2b1679 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards b7b2fc5a78 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards a0cdb59ad9 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards bd84a31d87 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 549034b7ab 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 8bd0e87274 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 3930699636 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 3f060fe55f 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards ac5509df10 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards a1f8fc278a 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 6cf55ad934 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 58eab802f1 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 084ad84c4c 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 5490575364 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards d37c2b87f1 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 4ce73ffded 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards b1cd6181fc 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards bf673f6e84 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards ea9da694e6 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 8625fcb3fd 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 2caf435516 49: onsuccess: #785: 1: Success after binutils: 12 commits discards f31c58352c 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 7fb46e3415 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards a785bec747 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards cca428cab2 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards a4996dd12c 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 905dd095eb 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards 5068cc7b22 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 7c8c35de0f 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards ce033bd7d7 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards 6bc132e805 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards 969f846586 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards 5ac0d45e02 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards f599bef16c 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 0eff7c3a05 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards 8425f3a8c6 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards 867f25ec40 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards 95a25307de 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards 53fe58bd18 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards 044fa59317 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards 8b77bc3524 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards e3d730b8d0 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards d39a2d6ef1 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards 0a125ef551 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards 8cadc7f1e3 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards d49b8510f8 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 9483851f4c 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 7dc514a786 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 14bfa859c0 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a5ea9e210d 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c3060f859c 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7b0b3acbc9 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e0be1feea6 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2359d070ba 16: onsuccess: 1: Successful build after binutils: 4 commits discards eee3fea60f 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 878ce17d6f 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 030a16dbb1 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4127a192a9 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9cb67b0d95 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4fc0a63e0a 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6d84fb49c7 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 673b2faef3 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 3ccb600a39 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards d85836ab26 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 6d672e94dc 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 889f18e9db 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 3142422efd 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 608c7e847c 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards d78e1bed9d 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new e3adfc0d6b 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 143cceedd9 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 30aa0973cd 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 1cad7a3833 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 7984c39d25 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new cf3ed3347f 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 9dd60d73b4 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new a42de4047f 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 1987156052 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f463378b18 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 091568d807 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e3b48ef670 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f036af0085 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5fedfddc0e 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 08acfdaff3 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 92104184f5 16: onsuccess: 1: Successful build after binutils: 4 commits new 5bcdc44fa0 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1c3d4a2b86 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 081994ca2d 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 03c39c6fd0 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 64ad0320f1 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d21f16d48c 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 443b438182 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 662a6734f5 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 006fefc06b 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new e522ab0136 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new d76d65c3f6 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new 690ad4d291 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new 5339d37c1d 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new 50470632ec 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new 77c54cb69b 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new b75ab67353 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new acd93bffe5 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new 159b7206e1 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new 511a098942 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new 618dfb578c 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new d6c360b462 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new 8a0af56acb 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new 878d84e35a 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new 1e6ef5be2a 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 1afc206d9a 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new cc21f650f3 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 2d1203d8a3 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new f90ddf8895 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new d38dd8e5e9 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 74ff3c86c1 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new d81b3e6078 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new f75d570d23 48: onsuccess: #782: 1: Success after binutils: 8 commits new fb8f25be9f 49: onsuccess: #785: 1: Success after binutils: 12 commits new f4b78269a9 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new e536c9ea30 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 294ace5026 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 6c13dbdfa0 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 40a578b0cb 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new a97a0b91cf 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new bb6733085f 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 609f27ca18 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 46bf1fa0e4 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new e3e67e0081 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new a3df40993d 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new c3841c6ed8 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 2cd79b8ebf 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new e88bba9b91 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new ec602f5fa0 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 5483197a74 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 4e1688d34e 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 673e669279 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 1ab05e8b87 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new c9c37b1d5e 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 9db7857684 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 1ecd899883 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 070248922f 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 4f4fda49fc 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 3fa2c5f65c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 90f2e14a37 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new ad7003ee2b 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 275b43698c 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 9ba0507ce8 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new d126e6cf38 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 0d1856385d 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new b4293befd4 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new fd9c7dd67a 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new e851d7c1e5 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 9a7d791fac 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 25350d600f 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 6de8910eee 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 69606f4f32 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 4650b30521 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new de0e7ed6ac 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new d0a8515d76 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 44f85b7699 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 6c789d69c1 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new dee562e0c6 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new a9b58fd3db 94: onsuccess: #832: 1: Success after binutils: 5 commits new 230b98331d 95: onsuccess: #835: 1: Success after binutils: 3 commits new 9815fda0de 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new c5094bf867 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new b548daea55 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 9105e4f5fd 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new ea7f611b6a 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 74686a94ec 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 542c825371 102: onsuccess: #843: 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 (8ce28f0640) \ 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 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 39764 -> 39796 bytes 04-build_abe-gcc/console.log.xz | Bin 215748 -> 214372 bytes 06-build_abe-linux/console.log.xz | Bin 8752 -> 8288 bytes 07-build_abe-glibc/console.log.xz | Bin 244432 -> 244648 bytes 08-build_abe-gdb/console.log.xz | Bin 39128 -> 39888 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3844 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3744 -> 2836 bytes 11-check_regression/console.log.xz | Bin 5980 -> 8152 bytes 11-check_regression/mail-body.txt | 30 - 11-check_regression/results.compare2 | 405 ++- 12-update_baseline/console.log | 34 +- 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 | 32 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 3749764 -> 3778280 bytes sumfiles/g++.sum | 30 +- sumfiles/gcc.log.xz | Bin 3299144 -> 3304204 bytes sumfiles/gcc.sum | 5151 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1077360 -> 1081064 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2272 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 231784 -> 231396 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 453816 -> 455508 bytes sumfiles/libstdc++.sum | 4 +- 37 files changed, 3036 insertions(+), 2716 deletions(-)