This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 0ebc2ed8c0 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards bac1339088 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 82758d651c 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 164a44589e 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 3bae8ff2c9 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 5f82c4e83f 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 70da955587 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards d2d7d94b98 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 445d9e6438 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 884bf57602 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards fd879da53c 128: onsuccess: #2163: 1: Success after linux: 23 commits discards bcf4041417 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 2db7f0ef81 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 63fa2ce468 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 51792b1e43 124: onsuccess: #2159: 1: Success after linux: 23 commits discards fc4ed9752d 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 62549b94b3 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards ad309e45ce 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards a22d229aa5 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards f78f9050ed 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 9be5f7f119 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards edb21833ab 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 056225ee53 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 2a51b2a11b 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 1527e83bdf 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 4321fccf6f 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 784c777fb9 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 0901925fef 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 219b0d1a90 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 0ce0fb7f63 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 4c18f3de30 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 2270aab985 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 0136ac0004 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards a670a3599d 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 1de8b7e46d 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 6e516c8bf2 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards e914f6d9b1 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 492c2204d7 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards d9612c6040 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 214c340cb6 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 7464a8d127 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 06330bafd2 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 45f6b2ebd4 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 90fab2d909 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 80cffa9b1a 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards ce8a9ed96d 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards d05b6a5625 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 9e64e6bbe9 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 547e854faf 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 6cb99e41d2 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards f75aa29a5f 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards f75ac94d9d 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 5c90200fc8 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 9509498344 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards fe912d8552 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 317578ac75 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 614d48269c 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 654ff1aa99 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 51e5944289 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a67bdf7f68 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 72901da79a 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 166547fd11 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 8015553d44 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 979fc2bb18 75: onsuccess: 1: Successful build after linux: 44 commits discards 6dc21ef5c6 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards f0c0c5f252 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1fb73b8171 72: onsuccess: 1: Successful build after linux: 12 commits discards e93546cfbf 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards dcf84ff61e 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards ed631a6dfd 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 3ea4ec630e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2d8126edeb 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards af30b24fa0 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 1d450328d4 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9b6e5f26aa 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f98ab25693 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 70c87507be 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards b11adf4110 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 156471f55c 60: onsuccess: 1: Successful build after glibc: 2 commits discards 2df995d8e8 59: onsuccess: 1: Successful build after binutils: 2 commits discards fc9b2a798c 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards fbc3e07eb5 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5696d454e9 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bc3c94fc43 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 535d9cece6 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards be1702e4ea 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards ec5e205ef8 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 73939d6e18 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 190b074911 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 09a410eedb 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards e62b591a0d 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 222644aefa 47: onsuccess: 1: Successful build after linux: 10 commits discards f5531edb78 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 331900896d 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c14b0c6d21 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 5936807550 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards ef97cbcb4b 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards bb6e66aa0e 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c6ff00d333 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards c8ce5d067b 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards d4b4d0ddcc 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 775c34b36d 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 6d03ed6947 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new a099bf322c 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new f466793e27 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5233713bef 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 5ad567a827 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 81c81ed735 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 6378b5d6e9 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4ef3768ed7 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new ae2d36e74f 47: onsuccess: 1: Successful build after linux: 10 commits new 51491ea66a 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cf64b59d2d 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 3f08932939 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a4679f20c4 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4936c6c92e 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 7df69e7e90 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c0f923c01e 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 5b20e84bf1 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new ed116af7a9 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ad610c3cb4 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 628714356d 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 428724546e 59: onsuccess: 1: Successful build after binutils: 2 commits new 95ca43bcb3 60: onsuccess: 1: Successful build after glibc: 2 commits new 449b40237c 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e9ea2f1058 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new ec01ff9095 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new a822de45c2 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d4f36a8b78 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 46245355c1 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 6a482db7a4 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new fc5850dc70 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5eb66a528b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new b8e3936508 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 651411b5d9 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 568a1e85a0 72: onsuccess: 1: Successful build after linux: 12 commits new 0bf8aa8e96 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7232817438 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 20b357faf7 75: onsuccess: 1: Successful build after linux: 44 commits new 9124173bcb 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bb29ee7a29 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 6e045b8196 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 2aef72dd85 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9ce820e7cf 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 599f4fe34d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new ae14dac0ab 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 446192d391 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 25861d686e 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 315a5e0c1e 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 39cb4c1361 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 639f70679a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 0591079fbf 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 1c950584c9 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 258a3687a1 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 06c732fd8e 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 17b505317d 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 68945a0e3e 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new ae774e7fc3 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 52b97f2c8e 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 158668c3d0 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new a248bf38ce 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 5051b57d87 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new f73a462df2 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 94d83e6c06 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new d85792145a 101: onsuccess: #2130: 1: Success after binutils: 81 commits new c0a845b919 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 7169b786ba 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 23b866e7ed 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 66283ecc7d 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 919be69eee 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 572ee4e788 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 9b632f6114 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new f760b09089 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 64f38f8608 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 10ef29a7ca 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 96d1c54057 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new b469269ff9 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 28fcf058f9 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new e559a385a1 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new be6fb482ab 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 72fc453c62 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new d171b633aa 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 10637df200 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 3fdc9e3d32 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 81db3484bc 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new f819b7313b 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new f0889d9fca 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 7e31e44fc5 124: onsuccess: #2159: 1: Success after linux: 23 commits new b46c2dab2e 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 8c5ddc89c2 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new d28b0dbfa3 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 92a15c9c49 128: onsuccess: #2163: 1: Success after linux: 23 commits new 797b5a3450 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new faf237ad82 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 7c10f5281e 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 8aba7c088f 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 7e07b06b77 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new a84ad074fd 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 60b9037c42 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 4e6b207a21 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 7cd2e15403 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 06cd6faa85 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 69f73d9795 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...]
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 (0ebc2ed8c0) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
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 1704 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30652 -> 30228 bytes 04-build_abe-stage1/console.log.xz | Bin 72204 -> 72456 bytes 06-build_abe-linux/console.log.xz | Bin 9280 -> 9260 bytes 07-build_abe-glibc/console.log.xz | Bin 240092 -> 239744 bytes 08-build_abe-stage2/console.log.xz | Bin 202724 -> 202620 bytes 09-build_abe-gdb/console.log.xz | Bin 37964 -> 37500 bytes 10-build_abe-qemu/console.log.xz | Bin 31408 -> 31168 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2544 -> 2748 bytes 13-check_regression/console.log.xz | Bin 11652 -> 6000 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 127 +- 13-check_regression/results.compare | 203 +- 13-check_regression/results.compare2 | 1336 +-------- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 129 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 26 + sumfiles/g++.log.xz | Bin 3412384 -> 3443048 bytes sumfiles/g++.sum | 77 +- sumfiles/gcc.log.xz | Bin 3007780 -> 3000652 bytes sumfiles/gcc.sum | 4490 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1031712 -> 1032052 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201884 -> 202160 bytes sumfiles/libgomp.sum | 9 +- sumfiles/libitm.log.xz | Bin 2656 -> 2652 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 421172 -> 427612 bytes sumfiles/libstdc++.sum | 12 +- 42 files changed, 2509 insertions(+), 4055 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions