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 32b4b7af398 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards e763aa905f3 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards 174cf10e11d 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards e4c4554f594 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards c6edf3e6497 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards f41fb9d5aa0 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards 7dd42c26314 118: onsuccess: #863: 1: Success after linux: 12 commits discards 841fc5c7246 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 12eae6e69ce 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards c5569a93524 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards fb53133d9a4 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards f20cfaca5bd 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 659cb837376 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 6c7a97b3b12 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 2cfaf2312ee 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 946a26b1052 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards bfabcb49132 108: onsuccess: #850: 1: Success after gcc: 2 commits discards aea6580a9f1 107: onsuccess: #849: 1: Success after binutils: 5 commits discards abfe64ecacb 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards f770b18ae36 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 32a17c9d05f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 745c50c5f0c 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards cb211320a60 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards ab11f232bc8 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards b2210c401c7 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards bf17e3ddd47 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards eb4109ad615 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 4677aa5bc46 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards ab4b56ae5eb 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 7104ef88470 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 6855798af83 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 17aef3d756e 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 6bc57bf1199 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 856aa737e08 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 70e44b63b1b 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 77bdab4351e 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 38d7132799b 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 4381553d94d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 66bcce70455 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 3748e692210 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards c049761930a 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 162cb65f090 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards c79a32c9e88 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards efb0d9b32a7 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 847d38d1af4 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 125093ac8b7 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 6dafa09174d 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards f374dfe171c 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards 78fa218f3b0 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards e01f7a6e5ba 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards eac8eabf9e2 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 226bb53c5cc 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards f9882b14d04 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards 0d19e70d6c5 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 7990df4c0cb 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 99862e9b51d 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards 952d92d07dd 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards d22cadfcc6e 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 1476c57689d 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards f978f7412db 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 875edf783f7 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 38a4f7e9c51 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 0173aee81f9 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards a3685f0a56b 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 303089687ad 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards 7cf41d7f833 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 18b6e505b7c 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards e902a49b42e 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards decf7953860 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards a4ade735f3b 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 2977aa5dc2e 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 6a65a7921fd 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 8426be54da5 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards a83de673e57 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 0939e71583a 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards 678af8acbbd 49: onsuccess: #785: 1: Success after binutils: 12 commits discards c10c66aadbb 48: onsuccess: #782: 1: Success after binutils: 8 commits discards db6dd868562 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards a56f3ae0426 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 4fdf42e6926 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards fd5f5a82565 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards c9663a302af 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards 01a9feb2ad5 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards e8dd4b8c477 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 0ea89b2d20f 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards 35ca6eb00b8 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards b02b14fed6e 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards 0cd9f3abf1c 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 493d82a3ebf 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards f679be996dd 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards b04abee7888 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards 312a9aeae0e 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards a03fbae1c98 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards 0b2e615da22 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards ced712ad465 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards dba2c009ca2 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards 1990cf1dda1 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 19f756f55c6 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards 625deb0b995 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 9da6ce213a6 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards 43f8b49e701 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 28c289ae33b 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 90aaf430a46 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new a95f294f7a5 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 43bc0abb1d5 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new 0c031ea5632 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new 1f5ddfa2989 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 14430edfc3e 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 545e9702e77 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 167e93bd331 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new 2288ca6109b 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 404312c6e45 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 1c78b90200f 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new a053dbc7325 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new d59b9ee0bc0 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new d95d374a5af 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new ae66fb75ef3 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 273c0282410 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new c39617128bd 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new 843c82b098a 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 6311e3b9e79 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new b2b5b9305b9 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new c4bdbb6fb27 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new 9f191bf23f6 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new 943c83835c6 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new c1f71857cfc 48: onsuccess: #782: 1: Success after binutils: 8 commits new cdeed7ea40c 49: onsuccess: #785: 1: Success after binutils: 12 commits new 5536550696f 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new deb08fc6d05 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new e2ed93c6366 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 179ced9db34 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new f0b94ddb790 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new 8e6121f4286 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 15e7ec69786 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new a139aaf387d 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new dd67158a84d 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new 27c960a9e51 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 8447f16377f 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new 1bb652624b6 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 0b7bc06a01f 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new c3581717ede 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new ec802a00835 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new cf8a572d6f2 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 3c954f0ad26 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 96e87f584e9 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 91915943010 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new 93d34983c0a 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new a986d25d50b 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new fb18cbdc80b 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new 97784a00fc8 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 63c1114690d 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new 364990f8f46 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new be12acbc720 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new fe4c994e072 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 13d285898c7 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 9bea57acc70 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 887127f4237 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new c74e169f4cf 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 2fa94851dab 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 906d2284a3f 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 08168498604 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new fb3d55ec7e3 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 59a780f9154 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 65aca2e66f2 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 0a06be8ac08 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 42a525e6eca 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 32343b06fe9 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new fb79ef905ed 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 44a576b920e 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new ddeb05f18e1 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 0209bbc4f07 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new de0b6bd6f75 94: onsuccess: #832: 1: Success after binutils: 5 commits new e6165376e3a 95: onsuccess: #835: 1: Success after binutils: 3 commits new 9e447e1620b 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 177f93bacfd 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 49f693c8eb2 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new e49938fa827 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 6fa2c86f496 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 09f53ae7070 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 418c60a0bb9 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 0c887230f31 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 150df82f8c5 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new b13664c021b 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 467adf4549d 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 6cf155880b2 107: onsuccess: #849: 1: Success after binutils: 5 commits new c878055b1be 108: onsuccess: #850: 1: Success after gcc: 2 commits new 6998ad62ba8 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new d4d7b02600c 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 512aa1ffdaa 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new eb90575d5a1 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 24828cce108 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 89aef48e330 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new ccb258c256e 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new c3eba9414be 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 9d395a19a55 117: onsuccess: #861: 1: Success after binutils: 18 commits new 7f714b22491 118: onsuccess: #863: 1: Success after linux: 12 commits new 2f79576d764 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new dcf104390c8 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new cf1f50b09ed 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new 492ad94ede9 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new a05d577c099 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 2205aa1fd7e 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 403bad84d08 125: onsuccess: #871: 1: Success after binutils: 26 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 (32b4b7af398) \ 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 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39684 -> 39416 bytes 04-build_abe-gcc/console.log.xz | Bin 214340 -> 214116 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8740 -> 8888 bytes 07-build_abe-glibc/console.log.xz | Bin 243588 -> 244092 bytes 08-build_abe-gdb/console.log.xz | Bin 39268 -> 39376 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3956 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2680 -> 2756 bytes 11-check_regression/console.log.xz | Bin 6428 -> 4764 bytes 11-check_regression/mail-body.txt | 46 - 11-check_regression/results.compare | 35 +- 11-check_regression/results.compare2 | 62 +- 12-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 48 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- sumfiles/g++.log.xz | Bin 3762216 -> 3758284 bytes sumfiles/g++.sum | 106 +- sumfiles/gcc.log.xz | Bin 3307240 -> 3306336 bytes sumfiles/gcc.sum | 5676 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1087176 -> 1086424 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231992 -> 233052 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 447864 -> 450752 bytes sumfiles/libstdc++.sum | 12 +- 35 files changed, 2985 insertions(+), 3146 deletions(-)