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 02242900b21 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards ba8b652fee6 118: onsuccess: #863: 1: Success after linux: 12 commits discards 918f85e2a69 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 9d2f4532b02 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards cf3920505e4 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards b60c74b7af5 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 0482a060710 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards da21edc01a0 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 38504873f98 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 6020e9134f2 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 461eb5fc5fb 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 6a8ae9da110 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 9778ad0a4bb 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 4ae737b71ec 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 089082c18c7 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 9199d1307a2 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 4e8bb120d18 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards 3400c94806c 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 856cfcd204b 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 2cee15b6296 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 7a10b0f2c73 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards 6e3d0120d41 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 89e99c15a7e 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 378b49a7017 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 167653fcaf2 95: onsuccess: #835: 1: Success after binutils: 3 commits discards d48cb20d829 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 571962a7515 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards d496184ab94 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 7a6337877ac 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards bcf50657a29 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 92285ee85d1 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards c9cbf6242a9 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 5b4893af8ea 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 6a2d47efe7f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 68993034a45 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 6f5fe57f3dd 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 2524e2d6904 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 202855a893b 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 16bf080dd17 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 98052c87702 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 766eea3c69c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 3df4adc6f57 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards 19fdd08a8bc 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards 0a58c04d374 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 7a9ccb581e9 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards ca5bf6bb0ee 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 02bee66e19b 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards d2d4ac33727 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards 741a5638b8f 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 8b9a9061098 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 8f71ecf8aa6 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards ad88ad10e50 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 2f9899382bf 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 91b2a06a7db 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards f8e2f369ad4 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards a027cf1c05a 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 8c4f4749fa8 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 98c54dfa3e1 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards 9a01ac7ffba 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 377b3b2ad01 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards 216853a2c6a 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards a3b9bee1bc4 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 3bbae48b8e1 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards 06ed784bf21 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards c4f714b4d96 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 7d47ede03f4 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 0721fdf2806 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 3c93246650b 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards 8cc2d21fb04 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 1180de743ef 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards a7a7bfcd3bd 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 5677b8ce820 48: onsuccess: #782: 1: Success after binutils: 8 commits discards d9c2a4b4cd4 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards cdca9bb9a4b 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 514278d8003 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards e864fddf3c3 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 2cee81ebfc0 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards 3f5880575a6 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards ce4b843b9cb 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 2ba57f88c48 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards b0b31ffe630 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards 2f5c082901f 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards 6c8b88cb630 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 3037ee1a1fd 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 31b1fe20af8 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 55191be855f 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards ec25f0a3873 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards d982b64a0bd 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards 1019783728c 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards 8603051a518 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards 16add68e636 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards c006d6f1b25 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards d2751d7d192 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards 8d51a056b4e 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 7e381ba923d 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards 8c1f1fb663e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards 7259133c5f5 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 446f13bf7f0 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 3ed461d62b6 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 4ef9ec60a4d 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards f6f8f305708 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new b32a1dadf9e 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new c32533c80b5 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 52eac4f18ff 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 46dde8ebe90 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 9de5833f9ed 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new e1bfb94a87c 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 0dada265ce2 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 5f570a5fdde 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 894695feb67 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new d1406ec4695 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new fe92e3b2747 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 7e232212853 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 5e00c5b611e 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 6fa24e3dfd6 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new ae38e8f1814 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 68dd2b335f8 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 121714b476c 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new a4e28e71c2b 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new b9eca511e02 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 17a196ded7f 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new aa925c6c795 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new d91f98d578a 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 9f30efddfa2 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new 03d43ce35cd 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 80e8cbf84d3 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new c4f8eee90f9 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 8f3168664ba 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new f333971e78f 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new cf8cf5c8166 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new b493f7dde94 48: onsuccess: #782: 1: Success after binutils: 8 commits new 4df711824a0 49: onsuccess: #785: 1: Success after binutils: 12 commits new ef9053f764e 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new a0e4cec84ee 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new e9b9cc520a4 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new b062579a9c2 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 618efc85143 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new 9521ca64ea6 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 4fb9c625830 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new af8481ad9dd 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 84b64b1df0d 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new 4a7df064418 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 06aac5daacb 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new c373f914153 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 0d4668028f2 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 6435228b6bd 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new e2c30ac73cd 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 869f9e72a1f 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 03ce2dc18b5 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new a682181f569 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new b43bcc36078 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new c45805643a2 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 58fd80e3607 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new adf534a1e49 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new d5fb5162d92 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 570a1e727a5 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new a5a476f9f5b 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 30afc751247 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new 6d9f89dda3a 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new f9c2f5599bc 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 294c6c26d5f 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new f7abd138dfb 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new de340c48516 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 085a0b46639 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 56460e77686 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new f6d65243974 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 0371d8c6651 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 8684de813b9 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 9a47f79d457 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 699fb7d2045 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 79a343a6d6c 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 7c0131405d5 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 59efb65f650 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 6fba8420a73 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new e8ead4039e9 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new b1d4bd1bf3f 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new b22f08b79f0 94: onsuccess: #832: 1: Success after binutils: 5 commits new 985ad4af17a 95: onsuccess: #835: 1: Success after binutils: 3 commits new c01db81b2d6 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 38074d9c0a4 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 1b885cab7b2 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new fab35a06a69 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 1ebe264f89d 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 1324b914218 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new ccf14b94e40 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 0fb01b784ec 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 89a0c228f2f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 2285d27f42a 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 2d37c00d8e2 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 1162873ea48 107: onsuccess: #849: 1: Success after binutils: 5 commits new 1b95615456f 108: onsuccess: #850: 1: Success after gcc: 2 commits new 07261adb25c 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 944ca9cd947 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 365be5a5132 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 23006f4737a 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 6ed424e493c 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new abe04a87932 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new e0908f6dffc 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 5e2ebb2956d 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 1ad647f1b30 117: onsuccess: #861: 1: Success after binutils: 18 commits new 79e88deac68 118: onsuccess: #863: 1: Success after linux: 12 commits new e8d686c50f9 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 1abaf1f4632 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...]

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 (02242900b21) \ 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 1732 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 39576 -> 39752 bytes 04-build_abe-gcc/console.log.xz | Bin 215288 -> 216032 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8728 -> 8584 bytes 07-build_abe-glibc/console.log.xz | Bin 243404 -> 244392 bytes 08-build_abe-gdb/console.log.xz | Bin 39148 -> 39232 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3840 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3576 -> 2516 bytes 11-check_regression/console.log.xz | Bin 7832 -> 7328 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 | 335 +-- 11-check_regression/results.regressions | 27 + 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 | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 27 + sumfiles/g++.log.xz | Bin 3747500 -> 3750376 bytes sumfiles/g++.sum | 145 +- sumfiles/gcc.log.xz | Bin 3330456 -> 3291704 bytes sumfiles/gcc.sum | 4933 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1081840 -> 1085088 bytes sumfiles/gfortran.sum | 54 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232148 -> 231448 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 456840 -> 453348 bytes sumfiles/libstdc++.sum | 13 +- 43 files changed, 2901 insertions(+), 2837 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