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 ab3a1a083c9 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards 44a12eb49b2 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards df2a105daed 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards 9732ae991ce 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 72107ed7e91 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards 9517f36bcd9 118: onsuccess: #863: 1: Success after linux: 12 commits discards 7e5285c5a0c 117: onsuccess: #861: 1: Success after binutils: 18 commits discards dc150b63e53 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 63b6118131a 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 1f68281be45 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards d359075888a 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 8ed5b4aad74 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 84e22835941 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 55de3c32fcc 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards a1bace73a0e 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards d9d0e128416 108: onsuccess: #850: 1: Success after gcc: 2 commits discards a9896b54606 107: onsuccess: #849: 1: Success after binutils: 5 commits discards b98586d07fc 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 88692dd9af0 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards f442979a116 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards bbc1f3b0e82 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards 272374766f5 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards c5c64363150 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 233b971d221 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards e3f7b6fe8ee 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards fa08fe43712 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 35741088f3e 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 43bf52d2df1 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 9cedaf07b84 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 175e971e1fa 94: onsuccess: #832: 1: Success after binutils: 5 commits discards ad94dd08559 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 9db5d71fdeb 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 9530e295a7c 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 28661c6f2ec 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 0c56b52c463 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 1c074dd7873 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 6dcf0fd6f9d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards dea4ebc72c8 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards d3095f7faa2 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 2d65dab67bd 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards ed0bfaebdae 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards bad95a8ff1a 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards d4cff3d7ce4 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 6552f26c582 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 84d0c747935 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards f1a21856f55 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards b534ce783e1 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards ba6ff964bf2 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 8ce2aef2ff5 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards 23aa4a90e51 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 28dc1a6c60d 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards a6f071dd773 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards a5e629ec68f 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 2a739d4289b 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 0593d0b9818 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards ee1e5725c1e 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards c58f2e77347 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 062899f6706 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards f59c195227a 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 41b1704513e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 1179e8defef 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 3d66f9b4517 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards 6f4fc559576 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 32218a20000 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards ebaabae2ae0 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 82d9fca4652 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 998a1cdfafb 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards 749a03992fa 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards e098201f4f6 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards fa72cc6ec65 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards cddb027a6c8 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 8c93c3fe343 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards a6c51a43560 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 3daa8721be9 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards be4ff11c5f2 49: onsuccess: #785: 1: Success after binutils: 12 commits discards aac840c5c3d 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 72f4b4cef61 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards 300b53841b6 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards ac8b68c6ce7 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards 2c359fdb6cc 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 2a29fe50bb6 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards a3f5baf2a78 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 45a8e815368 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 4d7dd4ce2eb 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards 1bd2edd4eea 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards 6f698f40101 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards 2995d0b121f 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 65e4aac64c2 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 7d4fe4da526 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 9ffc0159b6b 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards bf71170c46a 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards fc01f82c50b 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards 7d71c7d84d7 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards 0d0633aed66 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards c900bbd4aaa 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards 55b89fbcae3 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards bbc968b4898 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards 81b23c4926c 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 3b179209147 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards 1cc54c70492 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards 9bba33ec773 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 2256e45dbfb 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 43f8b49e701 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 9da6ce213a6 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 625deb0b995 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 19f756f55c6 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new 1990cf1dda1 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new dba2c009ca2 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new ced712ad465 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 0b2e615da22 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new a03fbae1c98 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new 312a9aeae0e 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new b04abee7888 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new f679be996dd 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 493d82a3ebf 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 0cd9f3abf1c 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new b02b14fed6e 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new 35ca6eb00b8 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 0ea89b2d20f 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new e8dd4b8c477 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new 01a9feb2ad5 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new c9663a302af 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new fd5f5a82565 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 4fdf42e6926 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new a56f3ae0426 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new db6dd868562 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new c10c66aadbb 48: onsuccess: #782: 1: Success after binutils: 8 commits new 678af8acbbd 49: onsuccess: #785: 1: Success after binutils: 12 commits new 0939e71583a 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new a83de673e57 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 8426be54da5 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 6a65a7921fd 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 2977aa5dc2e 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new a4ade735f3b 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new decf7953860 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new e902a49b42e 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 18b6e505b7c 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new 7cf41d7f833 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 303089687ad 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new a3685f0a56b 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 0173aee81f9 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 38a4f7e9c51 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 875edf783f7 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new f978f7412db 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 1476c57689d 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new d22cadfcc6e 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 952d92d07dd 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new 99862e9b51d 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 7990df4c0cb 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 0d19e70d6c5 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new f9882b14d04 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 226bb53c5cc 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new eac8eabf9e2 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new e01f7a6e5ba 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new 78fa218f3b0 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new f374dfe171c 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 6dafa09174d 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 125093ac8b7 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 847d38d1af4 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new efb0d9b32a7 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new c79a32c9e88 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 162cb65f090 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new c049761930a 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 3748e692210 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 66bcce70455 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 4381553d94d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 38d7132799b 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 77bdab4351e 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 70e44b63b1b 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 856aa737e08 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 6bc57bf1199 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 17aef3d756e 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 6855798af83 94: onsuccess: #832: 1: Success after binutils: 5 commits new 7104ef88470 95: onsuccess: #835: 1: Success after binutils: 3 commits new ab4b56ae5eb 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 4677aa5bc46 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new eb4109ad615 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new bf17e3ddd47 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new b2210c401c7 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new ab11f232bc8 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new cb211320a60 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 745c50c5f0c 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 32a17c9d05f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new f770b18ae36 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new abfe64ecacb 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new aea6580a9f1 107: onsuccess: #849: 1: Success after binutils: 5 commits new bfabcb49132 108: onsuccess: #850: 1: Success after gcc: 2 commits new 946a26b1052 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 2cfaf2312ee 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 6c7a97b3b12 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 659cb837376 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new f20cfaca5bd 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new fb53133d9a4 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new c5569a93524 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 12eae6e69ce 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 841fc5c7246 117: onsuccess: #861: 1: Success after binutils: 18 commits new 7dd42c26314 118: onsuccess: #863: 1: Success after linux: 12 commits new f41fb9d5aa0 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new c6edf3e6497 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new e4c4554f594 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new 174cf10e11d 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new e763aa905f3 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 32b4b7af398 124: onsuccess: #869: 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 (ab3a1a083c9) \ 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 1760 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 41168 -> 39684 bytes 04-build_abe-gcc/console.log.xz | Bin 216220 -> 214340 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8764 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 246468 -> 243588 bytes 08-build_abe-gdb/console.log.xz | Bin 40500 -> 39268 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3884 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3024 -> 2680 bytes 11-check_regression/console.log.xz | Bin 7520 -> 6428 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 11 - 11-check_regression/mail-body.txt | 61 +- 11-check_regression/results.compare | 38 +- 11-check_regression/results.compare2 | 132 +- 11-check_regression/results.regressions | 46 - 12-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 46 - sumfiles/g++.log.xz | Bin 3781660 -> 3762216 bytes sumfiles/g++.sum | 138 +- sumfiles/gcc.log.xz | Bin 3307336 -> 3307240 bytes sumfiles/gcc.sum | 4792 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1079296 -> 1087176 bytes sumfiles/gfortran.sum | 69 +- sumfiles/libatomic.log.xz | Bin 2280 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233012 -> 231992 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 457880 -> 447864 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 2667 insertions(+), 2858 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions