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 60d0ea4eb3 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 5e4136c6f8 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 01fb2b1d63 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 38f8e1bcf5 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 8838883943 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards b1d8afa74d 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 37862fc0be 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards cee5f9f500 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 608f1e86b8 128: onsuccess: #2163: 1: Success after linux: 23 commits discards d68a5e4ae7 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards b1a551287e 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards dd8ea9eaa5 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 8df7ee5828 124: onsuccess: #2159: 1: Success after linux: 23 commits discards d2c1352c17 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards e841245aa5 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards d6ddff5fd8 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 0188e2b155 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 8dd0b6f83d 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 1c7a14beaf 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 724b863077 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards d3ada16de5 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards e34343872a 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards b9fa0b5aa7 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards d5fa55596c 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards bf2f166684 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards df6ec97f7e 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 7c70835d1b 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 0ceb9392aa 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 17597255fa 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 48131d5b71 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards a8b5a096ce 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 4cd4574444 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards e574656042 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 5f2b8c6f4d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards c8dc08ffb2 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 62e166ec2f 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards be223602e1 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards fe0b812c6c 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 856f822255 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards c306e01759 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards a044f01739 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 811e731bed 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards d77cc9e653 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards b23728a5ec 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards a2b03adc22 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f04e9ad027 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 4f765e7320 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 7a50c29e17 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 89ba3bc252 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 861b1557f0 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards fe06b51432 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 095aaa3120 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 132fcaf7bf 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 8a5abc7bb2 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 6929afa859 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 14a4aea679 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 181bb00769 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 16b63c9612 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f7d5302c38 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards af6bc4187a 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 348cc62231 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7918aa952c 75: onsuccess: 1: Successful build after linux: 44 commits discards 1089286317 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 9a1fa3a474 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fac779b736 72: onsuccess: 1: Successful build after linux: 12 commits discards d7a0eef58a 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 544f2dd42b 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 7437d13e98 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards edf1568939 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5b3f891c66 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 2124b8a34c 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 72c434a7c7 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dc4a60c45a 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7ab5a32133 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 2323668a7a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 3b4e7cb816 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 6f9fdae999 60: onsuccess: 1: Successful build after glibc: 2 commits discards a08d5a3410 59: onsuccess: 1: Successful build after binutils: 2 commits discards a352478c19 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards af71982b06 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 1bad3543fe 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e4cce4407a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 1ba4bdb4de 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards ff88439f3d 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards c8ff032367 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 28917aefd5 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1698216bff 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 37dd956bcb 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards a1c54c3027 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c67a1505b4 47: onsuccess: 1: Successful build after linux: 10 commits discards 78505351b2 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 4ea96c58ea 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5d91dffb26 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards fd9487b6a5 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards e0ca7ea642 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards e1b8dafe35 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3efe71a581 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards e8d5e597e6 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 7eb3ed195f 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 61163f5fbc 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 360dc629de 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3e37a22980 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3b5b1c694d 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d1e5082f3e 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 2ebd895110 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new dc1c5f71e8 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 905dab919f 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e33353919f 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 2b8a9824b5 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new c0584a6d25 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new b1cedfa74f 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new db2045bab5 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new b23d37cabc 47: onsuccess: 1: Successful build after linux: 10 commits new 355e80ddce 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 69f4c9fee6 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 00e115a90b 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c67538186c 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 737cacc5db 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 5c0e1b23a6 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 34e9c6334c 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new fb7c59c594 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 7dcb990e0b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 304e45e116 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3063411a8f 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 149a1bd6c2 59: onsuccess: 1: Successful build after binutils: 2 commits new 38773ab7f1 60: onsuccess: 1: Successful build after glibc: 2 commits new a83b909ea0 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 8902d4b641 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new ee7212cc8b 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 246f2271bb 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fa3b9875a1 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0971c22445 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 2defc4f52b 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 5437f60966 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 58152d6f55 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 66ba17fca3 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 92a8fc131d 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new ced95d6a6d 72: onsuccess: 1: Successful build after linux: 12 commits new edb37700aa 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ebffd26bbc 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 2e60696a39 75: onsuccess: 1: Successful build after linux: 44 commits new 422d9d0c88 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b77cfdf676 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new a74b2b5dd6 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new e8f90de37f 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new cfa89370c6 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 741690bbbf 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 429daf61e4 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 3b66b510d7 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new d77d3e5681 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new fd5e25d1ff 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 5f637c54ab 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 93b0b44894 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 6ec8c04193 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new aa20f029f9 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 76d89e2b35 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 1586fb541e 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new bf3b12a629 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0451cee8b6 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new dc81c01cc7 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new db94162dea 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 3fdd26d597 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new c2b14e1cd6 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 38309e3532 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 9babc9f047 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 97c55c1d6e 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 2c6dcea025 101: onsuccess: #2130: 1: Success after binutils: 81 commits new d104287f34 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 03ad8aa2a3 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 1c22c546ef 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 1840d3046e 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 0b9accb707 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 1570cea9be 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 8a2f71d470 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 9f462eb928 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 4227199e40 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 315c867586 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 552125c96e 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 8b04c2f958 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 4a3d1e73ed 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 0e4bc6e2e5 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 0c58ed3a7a 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new d3df47627d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 23b1e57a5b 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new eb74488074 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new ac77ae8536 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 35752a1e98 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new aae75b6762 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 0a38f85998 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 847b1b3b72 124: onsuccess: #2159: 1: Success after linux: 23 commits new 7147463366 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 5182944ab0 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new e7d4ada082 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 41ae789b0b 128: onsuccess: #2163: 1: Success after linux: 23 commits new 04df5792c5 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 2cebd6532c 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 769a1b591a 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new ef31bb73d4 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new af5bed7004 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 01c495d8d0 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new bb0b67ae11 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 85b09476ae 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 2f0bd18e1b 137: onsuccess: #2172: 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 (60d0ea4eb3) \ 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 1720 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30472 -> 30520 bytes 04-build_abe-stage1/console.log.xz | Bin 72832 -> 72676 bytes 06-build_abe-linux/console.log.xz | Bin 8632 -> 9268 bytes 07-build_abe-glibc/console.log.xz | Bin 240280 -> 240244 bytes 08-build_abe-stage2/console.log.xz | Bin 203276 -> 204836 bytes 09-build_abe-gdb/console.log.xz | Bin 37800 -> 37732 bytes 10-build_abe-qemu/console.log.xz | Bin 31300 -> 31532 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2660 -> 2620 bytes 13-check_regression/console.log.xz | Bin 72748 -> 12988 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 176 +- 13-check_regression/mail-body.txt | 180 +- 13-check_regression/results.compare | 298 +- 13-check_regression/results.compare2 | 16321 +++--------------------------- 13-check_regression/results.regressions | 134 +- 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 182 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 134 +- sumfiles/g++.log.xz | Bin 3420960 -> 3443752 bytes sumfiles/g++.sum | 188 +- sumfiles/gcc.log.xz | Bin 3031424 -> 3015508 bytes sumfiles/gcc.sum | 5705 +++++------ sumfiles/gfortran.log.xz | Bin 1035640 -> 1034636 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202548 -> 202032 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 420032 -> 414524 bytes sumfiles/libstdc++.sum | 8 +- 44 files changed, 4775 insertions(+), 18681 deletions(-)