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 ca20ffa86c 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] discards 34bf0f6c1c 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] discards 12d1dd5abf 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] discards dc8b096d68 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] discards 1e97c74d0e 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] discards ea081b9422 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] discards 8451edf039 152: onsuccess: #903: 1: Success after linux: 22 commits discards a7b7991f47 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 828bd8108f 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 79c97a1148 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 5ce1bf8f1c 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards 58df207f66 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards b28441fd92 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards a46fcc696b 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards fc9fe679e2 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards 6c041b78c3 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards 1e22e7139c 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 9254847ddb 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 50837cc2a2 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 97d1ad7375 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 67dbee9faf 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 571267052a 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards a56fdee8f6 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 12f71f01d3 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 1326050cd7 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards f0f78a1482 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards f7922e2e84 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards d86fe65ca5 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 7bdd977de0 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 5e14b080d0 129: onsuccess: #878: 1: Success after linux: 3008 commits discards b4b14752b1 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 58f7c746d2 127: onsuccess: #874: 1: Success after linux: 219 commits discards 2153d1d816 126: onsuccess: #873: 1: Success after glibc: 2 commits discards b921d73f89 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 6f37cb8f05 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards e6a71289e5 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards e3ef35171a 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards a183d4a239 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards ccb2702a22 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 41c02868c4 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 2f62cf6626 118: onsuccess: #863: 1: Success after linux: 12 commits discards 5728fc2690 117: onsuccess: #861: 1: Success after binutils: 18 commits discards cb52e787fc 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 32ab78759c 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 1d1a0dcae6 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 32930f9379 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 445622230c 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards c530f97249 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards d3c0255e9e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards b1439aebc3 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 7af7543a81 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 4a98992bce 107: onsuccess: #849: 1: Success after binutils: 5 commits discards fdb3aca946 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards f05af8315a 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards f726184637 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 62cc949475 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 74ebcc5a24 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards fd7655521e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 1e512224a9 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 6af3f4f8e6 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards d58ab3bd53 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards ae46d63fef 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards d5626a95fd 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 031244154d 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 54e7f8fca5 94: onsuccess: #832: 1: Success after binutils: 5 commits discards bb799c4cd2 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 1546b5b34f 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 5085772ef3 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 09b085bc31 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 656f95d6cd 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 74d74d4ab3 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 5cd22ff804 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards db391896f0 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards a3ec215a5b 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 8390d85428 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 60bc26c86e 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards e85d037aa2 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards a823617fc7 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 84d9da20a9 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 6c0aae16bb 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 1e39524560 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 3ba0919ac2 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 7477af49c7 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards c30931edb0 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 98e6345cee 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 59ec1026eb 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards a83f5a4557 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 7af19e07e1 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards e5d36ae38e 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 2558995dd0 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 24314a4669 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards ed92eab36c 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards ae99759983 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards edf38fdd06 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 6e751ea6aa 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 3a14805787 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 95e87f1546 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 54a4fff6c4 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards c5f0d3ccf2 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 98bd9109d3 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 1ffe945b11 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 1def3eecc8 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 8f18d7c614 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new a91755f3e7 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new db5de082c9 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new ad3badd2bd 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 7ff5e75f02 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new e604eacdfa 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new b3ff14c86b 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new bfefec0bc4 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 35cbb78f4b 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 8696d78bb9 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new d2faaafe14 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new cdb8b1f9ad 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 9a0ec6fb15 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 9cf60b5977 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 51bf789a7c 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 777ccf0643 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new cac51be6f5 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 59c0ba3d7c 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new d515dd22f9 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new c429fec0f4 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 1ad1f4c4d4 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 5563a490ba 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new c456b4d156 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new f8c3c58ecf 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 25db7464e4 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new b69f91d1bb 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new becfbefe38 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 8eb84e6e07 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 75746c50d0 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new df4014ff81 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 42f65e9a1c 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new f6d79076c4 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new ac40dd2265 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 54f2a4d962 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new b132823d65 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new ecb3e354e2 94: onsuccess: #832: 1: Success after binutils: 5 commits new 7d4e39cf3b 95: onsuccess: #835: 1: Success after binutils: 3 commits new 313392930f 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new d3ae7b0c81 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new c864654c56 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 6f3a16284b 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new d58a3f40c3 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 75c1d6dffa 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 763d434d53 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 4da95252d0 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new a0f446f882 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 91ecb6e6ba 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 5410ecf872 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 6ebcb19510 107: onsuccess: #849: 1: Success after binutils: 5 commits new f722e65c3e 108: onsuccess: #850: 1: Success after gcc: 2 commits new b9ea68f20c 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 81ed3ee7dc 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new be0bcdbba1 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 152704c68c 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 9298cce3e3 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new d582b0c1ae 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 4257cd0bb7 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 1eee3d9594 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 1c4285fc5e 117: onsuccess: #861: 1: Success after binutils: 18 commits new e35617401e 118: onsuccess: #863: 1: Success after linux: 12 commits new 78fbb3abaa 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 0d9f951afc 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 9c0d6fded7 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new ce9b1198ed 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 26693c5adf 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 8d81e4858c 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 298a627a1c 125: onsuccess: #871: 1: Success after binutils: 26 commits new b11c8e9ba9 126: onsuccess: #873: 1: Success after glibc: 2 commits new 5f9f50a511 127: onsuccess: #874: 1: Success after linux: 219 commits new 6074e27835 128: onsuccess: #876: 1: Success after binutils: 12 commits new 123f757f5a 129: onsuccess: #878: 1: Success after linux: 3008 commits new 02e583f706 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new 9a7748b807 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 10d6d9d721 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new d48044bb21 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 79ce8e89a7 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 92e8bc0f88 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 6794148d18 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 84cee64215 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new e49236e1c4 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 53bb9422da 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new f11fa16b73 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new d1e4481346 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 6014b5448f 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new cf891b3091 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 3807ba9a7c 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new ca225e278d 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 2147b5ab66 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new 86d3ffbd04 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new aa315cc9ab 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new 64109a7982 149: onsuccess: #899: 1: Success after binutils: 15 commits new bd83a1583c 150: onsuccess: #900: 1: Success after gcc: 11 commits new 7664bbb29e 151: onsuccess: #902: 1: Success after glibc: 8 commits new f7bc9abe07 152: onsuccess: #903: 1: Success after linux: 22 commits new 949a2b1a04 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] new 167d45328d 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] new 1c0d7fc575 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] new 899928e76a 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] new e654f72e02 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] new c8cb3cb3d3 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] new 3a7f213dad 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...]
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 (ca20ffa86c) \ 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 1752 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39756 -> 40016 bytes 04-build_abe-gcc/console.log.xz | Bin 215296 -> 215032 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8548 -> 8796 bytes 07-build_abe-glibc/console.log.xz | Bin 244148 -> 244320 bytes 08-build_abe-gdb/console.log.xz | Bin 39564 -> 39336 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3876 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2364 -> 2628 bytes 11-check_regression/console.log.xz | Bin 6396 -> 6496 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/mail-body.txt | 57 +- 11-check_regression/results.compare | 32 +- 11-check_regression/results.compare2 | 56 +- 11-check_regression/results.regressions | 42 - 12-update_baseline/console.log | 34 +- 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 | 59 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 42 - sumfiles/g++.log.xz | Bin 3728756 -> 3754968 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 3297940 -> 3297304 bytes sumfiles/gcc.sum | 5182 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1078372 -> 1084076 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232200 -> 232364 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 455484 -> 458104 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 2800 insertions(+), 2962 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