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 3822c46070 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 0a542f16c8 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 627e4e8e97 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards cbaa0df499 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards b18f13b6ee 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 2bcab5b6ba 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 8da56d63ff 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 034ed959d7 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 9185b8fd5d 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 71ba76e4a0 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards fbc21fed1c 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 58846d51db 95: onsuccess: #835: 1: Success after binutils: 3 commits discards eb7f3e3017 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 985c54272f 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 1665534e10 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 4bfd152dd0 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 1191885369 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 02b87eb8cd 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 956fa97044 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 250b5b5a50 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 2fd0640ec0 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 02e17fed94 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 3dee8464b3 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 5e1032d748 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards f197ebb1ac 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 063dc393f7 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 59a99321ba 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 62ff6520e5 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 1fcf7aaf4b 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 2874ea1d28 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 91359aaabf 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 2bb2b8e446 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 96e6d1059f 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 8eb4ceec8e 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 7252f0fda2 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 62c58fb369 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 030ef561a0 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 6d0a0f8c89 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards a6fa0e0169 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 2067b6b1bb 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards d942a3b516 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 5692507d1b 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards ffa60f0c1e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards e58019d609 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 7fb87c3933 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards eedda08df3 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards b689522dd4 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 08cc175a27 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards a9e9a25829 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 4462cd6acd 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 00b546c8ee 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 10e6f9e25f 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 0636f85f34 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 6c53f499e5 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards d625be300b 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards b1f649cdfd 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards a178a380ba 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 597054fb9c 49: onsuccess: #785: 1: Success after binutils: 12 commits discards f73b6b005c 48: onsuccess: #782: 1: Success after binutils: 8 commits discards ac80051f72 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 1b4494350e 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 0f7383c022 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards c95a710796 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 5965b5ef36 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards 1f81b725b0 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards a90fe51e6d 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards 0e5dc1850d 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards d1eddcbe29 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards 2942703694 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards 24566a6fbb 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 3b68ee7c32 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards a1ae4a91c2 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards 4cf6df99f9 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards 0a17ac557a 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards 619a1952ac 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards 07788853b2 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards 9f5a508e68 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards da4fc7ec50 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards 34570243a8 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards c0e00cb5b1 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards ea44ae79cb 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards 1593976da6 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards 818dbbe132 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 5318691b6a 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards a19142a764 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 1b1f467c75 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ab1b1169d7 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c24332671a 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 57e89c12c7 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c02f0af1ed 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3f9dd591e9 16: onsuccess: 1: Successful build after binutils: 4 commits discards 7bd325ffb3 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b7e6b102e4 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b5f10c808b 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cbead31d5c 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 787b401272 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 80b837fe20 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 88373bc4e0 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 997b1769f3 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards bcefa11c9a 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 426f284298 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 56d05682ac 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new a53b3ce05d 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 15df8ec5f2 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 54b5960a58 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f9d65887bc 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0a798b78e7 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d945cdf276 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d32b181058 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d65f8d2686 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 48bc4b5fc8 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 10483fe461 16: onsuccess: 1: Successful build after binutils: 4 commits new 8dd67756c6 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ce30367b6b 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4520c8ccf5 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6799c9510f 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 43b356f605 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1441263ef8 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new e9dcb45b3a 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new fdcff7226c 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 2e7ee697e3 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new d8bff7915e 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new aa81be09a2 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new edc293cb96 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new b327bd8499 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new c3f9cd2aa5 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new ea85315b27 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new 9dfd1e551c 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new c19c5ee173 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new 788f04e0c0 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new 0749c3c2f2 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new 4c354174a4 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 744f50b020 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new 3b8cfbd729 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new a6f4007594 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new 6a25cd8b8b 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new de63bef12b 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 9b5ad0a79c 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new d26bd41df8 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new c9a84e47f9 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 745fee97c0 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 0f59091717 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 46a7e32e95 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 058246c192 48: onsuccess: #782: 1: Success after binutils: 8 commits new 0c2460f6f9 49: onsuccess: #785: 1: Success after binutils: 12 commits new 8738324826 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new cde7f379c7 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new ad1f615109 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 369a6310da 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new bdb3eb5939 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 7da6ba605f 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 98f4354cdb 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 6068980344 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 1d4bf8fa02 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new bca262068b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 39a8840b96 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 84eab28200 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new f57561d16e 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 113d2d66ca 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new dfb0af22ce 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 75be994ae4 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 72c532a80e 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 4d31e12b54 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 6b025ec522 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new cd173f7a9d 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new d05f7a37e7 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new aba336dfd8 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 50063c5081 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 33fa8a23ef 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new b636855c66 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 60e0a58231 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new b20641bdbf 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new b16a50a556 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 24b02b1d18 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 7e46b71ad5 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new fbb57ddd25 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new a95ab73a86 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 70b4545888 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new bd7a097765 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 6bfcc9ab57 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 10e7743e25 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new e8aaf63b2f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 6ad5cb7d2e 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 9baa1e013b 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 0225e51745 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 4cb53c4914 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 14cdbbfe91 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 201905811e 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 16d7b6e367 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 2b3fc0f58b 94: onsuccess: #832: 1: Success after binutils: 5 commits new d07a5ada51 95: onsuccess: #835: 1: Success after binutils: 3 commits new 85f57b2eae 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new b2836fcbf5 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new f16d49972f 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 86d874ef43 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 4d4bc71c8c 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 90af853f70 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 3abc68e12d 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 35e2da66ea 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 531db87fcd 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new e73da6a995 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 8021513e4e 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 17ecd1e0f9 107: onsuccess: #849: 1: Success after binutils: 5 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 (3822c46070) \ 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 1692 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 39272 -> 40072 bytes 04-build_abe-gcc/console.log.xz | Bin 213312 -> 216264 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9548 -> 9632 bytes 07-build_abe-glibc/console.log.xz | Bin 243792 -> 246396 bytes 08-build_abe-gdb/console.log.xz | Bin 38800 -> 40492 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3980 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2572 -> 2656 bytes 11-check_regression/console.log.xz | Bin 6456 -> 5524 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 27 + 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 63 +- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 56 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 27 + sumfiles/g++.log.xz | Bin 3724504 -> 3774500 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 3310512 -> 3303828 bytes sumfiles/gcc.sum | 4920 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1078664 -> 1070508 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230840 -> 231824 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 450496 -> 451768 bytes sumfiles/libstdc++.sum | 12 +- 39 files changed, 2766 insertions(+), 2651 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