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 403bad84d08 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 2205aa1fd7e 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards a05d577c099 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards 492ad94ede9 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards cf1f50b09ed 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards dcf104390c8 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 2f79576d764 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards 7f714b22491 118: onsuccess: #863: 1: Success after linux: 12 commits discards 9d395a19a55 117: onsuccess: #861: 1: Success after binutils: 18 commits discards c3eba9414be 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards ccb258c256e 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 89aef48e330 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 24828cce108 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards eb90575d5a1 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 512aa1ffdaa 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards d4d7b02600c 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 6998ad62ba8 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards c878055b1be 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 6cf155880b2 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 467adf4549d 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards b13664c021b 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 150df82f8c5 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 0c887230f31 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards 418c60a0bb9 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 09f53ae7070 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 6fa2c86f496 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards e49938fa827 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards 49f693c8eb2 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 177f93bacfd 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 9e447e1620b 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards e6165376e3a 95: onsuccess: #835: 1: Success after binutils: 3 commits discards de0b6bd6f75 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 0209bbc4f07 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards ddeb05f18e1 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 44a576b920e 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards fb79ef905ed 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 32343b06fe9 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 42a525e6eca 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 0a06be8ac08 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 65aca2e66f2 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 59a780f9154 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards fb3d55ec7e3 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 08168498604 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 906d2284a3f 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 2fa94851dab 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards c74e169f4cf 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 887127f4237 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 9bea57acc70 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards 13d285898c7 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards fe4c994e072 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards be12acbc720 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards 364990f8f46 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 63c1114690d 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards 97784a00fc8 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards fb18cbdc80b 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards a986d25d50b 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 93d34983c0a 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards 91915943010 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 96e87f584e9 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 3c954f0ad26 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards cf8a572d6f2 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards ec802a00835 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards c3581717ede 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 0b7bc06a01f 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards 1bb652624b6 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 8447f16377f 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards 27c960a9e51 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards dd67158a84d 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards a139aaf387d 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards 15e7ec69786 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 8e6121f4286 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards f0b94ddb790 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 179ced9db34 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards e2ed93c6366 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards deb08fc6d05 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 5536550696f 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards cdeed7ea40c 49: onsuccess: #785: 1: Success after binutils: 12 commits discards c1f71857cfc 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 943c83835c6 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards 9f191bf23f6 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards c4bdbb6fb27 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards b2b5b9305b9 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 6311e3b9e79 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards 843c82b098a 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards c39617128bd 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 273c0282410 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards ae66fb75ef3 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards d95d374a5af 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards d59b9ee0bc0 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards a053dbc7325 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 1c78b90200f 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 404312c6e45 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards 2288ca6109b 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 167e93bd331 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards 545e9702e77 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards 14430edfc3e 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards 1f5ddfa2989 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards 0c031ea5632 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 43bc0abb1d5 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards a95f294f7a5 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 90aaf430a46 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 853b7c3f241 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 37fc2f8c114 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new a52c5f6f511 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new e1d0303f6a6 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new f1bcf0f2077 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 0a2b474e3a9 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new de8cd4517d6 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 6d23ac6bfdf 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new bcbb0305aa8 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 1c2bf9098a2 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new f5e5e116e70 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 85ca7b4710a 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 936a17f01b9 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new d20bb2f3706 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new 35b0d057fc3 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 6c5fa26d2f4 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 765b47c591a 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new 1ec990d0845 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new ea86f2ebc35 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new a23b7087aec 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new e0b8f497d05 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new 71a16499d9f 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new 7c79d7400fc 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 3efd68200eb 48: onsuccess: #782: 1: Success after binutils: 8 commits new 634c2d9b95d 49: onsuccess: #785: 1: Success after binutils: 12 commits new b9d9946af5c 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new 44c381592cd 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new c80df5222f2 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new cac39176f11 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new e909bd25943 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new d7eab650ba3 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new a3084d4fee0 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new a3d9d1b4b0f 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 74d0d5f7573 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new 6040d526d06 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new f49bd65ae6a 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new 0bc17309257 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 0550464486e 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 8ef5f6cba39 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 4881947f9fa 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new fa7004690ba 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 946fbe5aabb 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new b2296fdef10 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 7ccf8cc46d0 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new d30af7aed73 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new d3cfa337df9 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 2012689e515 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new 88feb218869 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 6f6cdad7569 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new 5f43bd78d81 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 0de8c805dcf 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new dfd2ceb40c9 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new fcbb79769fe 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 5d3e98bc2ee 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new d84cbcb4b06 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 0c02d1ed2ee 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 536d9e406cb 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new af63c6a1ea7 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new c08f5fa222e 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 86facfabb21 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new b85a2293935 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new b91c943f38e 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 470a52d55e1 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new d3c344bb1ea 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 99c13d66d92 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 2e94d067ac4 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 4db90aecaad 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new e93d92dea15 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 9fa06547220 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 9215b66d08a 94: onsuccess: #832: 1: Success after binutils: 5 commits new 1892aa053cf 95: onsuccess: #835: 1: Success after binutils: 3 commits new 04eff527652 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new aee332345f3 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new dac443bb21b 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 808cdfe26e2 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 9a0a0572201 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new bae0ca9a380 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 65e27f03c04 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 79ff81d57c2 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 50bb3b353b8 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new b4db12a0e42 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new feb647ef96f 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 57a7208cfbc 107: onsuccess: #849: 1: Success after binutils: 5 commits new c932bea0022 108: onsuccess: #850: 1: Success after gcc: 2 commits new 0b7f625bd54 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 240b2756c64 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 22f629c991e 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 9b2b8cb3416 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 2bb57884697 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 044ff0f3194 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 3d421bd2deb 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 573759605ef 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 98505b3bdfa 117: onsuccess: #861: 1: Success after binutils: 18 commits new 709669aeb16 118: onsuccess: #863: 1: Success after linux: 12 commits new ee255d5c9bb 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new a13aa8828e5 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new 22ddbecda30 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new eca6e580fe2 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new 08f0604d2e0 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 549b5c0442a 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 4b64be3b71c 125: onsuccess: #871: 1: Success after binutils: 26 commits new 7b50105aa6f 126: onsuccess: #873: 1: Success after glibc: 2 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 (403bad84d08) \ 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 1748 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 39416 -> 39564 bytes 04-build_abe-gcc/console.log.xz | Bin 214116 -> 213256 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8888 -> 8856 bytes 07-build_abe-glibc/console.log.xz | Bin 244092 -> 243240 bytes 08-build_abe-gdb/console.log.xz | Bin 39376 -> 39372 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3956 -> 3844 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2756 -> 2684 bytes 11-check_regression/console.log.xz | Bin 4764 -> 4608 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- sumfiles/g++.log.xz | Bin 3758284 -> 3770740 bytes sumfiles/g++.sum | 116 +- sumfiles/gcc.log.xz | Bin 3306336 -> 3303912 bytes sumfiles/gcc.sum | 5110 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1086424 -> 1079188 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233052 -> 233064 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 450752 -> 455572 bytes sumfiles/libstdc++.sum | 12 +- 34 files changed, 2698 insertions(+), 2700 deletions(-)