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 2f0bd18e1b 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 85b09476ae 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards bb0b67ae11 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 01c495d8d0 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards af5bed7004 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards ef31bb73d4 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 769a1b591a 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 2cebd6532c 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 04df5792c5 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 41ae789b0b 128: onsuccess: #2163: 1: Success after linux: 23 commits discards e7d4ada082 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 5182944ab0 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 7147463366 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 847b1b3b72 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 0a38f85998 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards aae75b6762 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 35752a1e98 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards ac77ae8536 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards eb74488074 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 23b1e57a5b 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards d3df47627d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 0c58ed3a7a 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 0e4bc6e2e5 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 4a3d1e73ed 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 8b04c2f958 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 552125c96e 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 315c867586 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 4227199e40 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 9f462eb928 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 8a2f71d470 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 1570cea9be 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 0b9accb707 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 1840d3046e 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 1c22c546ef 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 03ad8aa2a3 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards d104287f34 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 2c6dcea025 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 97c55c1d6e 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 9babc9f047 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 38309e3532 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards c2b14e1cd6 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 3fdd26d597 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards db94162dea 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards dc81c01cc7 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 0451cee8b6 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards bf3b12a629 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1586fb541e 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 76d89e2b35 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards aa20f029f9 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 6ec8c04193 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 93b0b44894 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 5f637c54ab 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards fd5e25d1ff 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards d77d3e5681 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 3b66b510d7 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 429daf61e4 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 741690bbbf 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards cfa89370c6 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e8f90de37f 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a74b2b5dd6 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards b77cfdf676 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 422d9d0c88 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2e60696a39 75: onsuccess: 1: Successful build after linux: 44 commits discards ebffd26bbc 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards edb37700aa 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ced95d6a6d 72: onsuccess: 1: Successful build after linux: 12 commits discards 92a8fc131d 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 66ba17fca3 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 58152d6f55 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 5437f60966 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2defc4f52b 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 0971c22445 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards fa3b9875a1 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 246f2271bb 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ee7212cc8b 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 8902d4b641 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards a83b909ea0 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 38773ab7f1 60: onsuccess: 1: Successful build after glibc: 2 commits discards 149a1bd6c2 59: onsuccess: 1: Successful build after binutils: 2 commits discards 3063411a8f 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 304e45e116 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7dcb990e0b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fb7c59c594 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 34e9c6334c 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 5c0e1b23a6 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 737cacc5db 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards c67538186c 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 00e115a90b 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 69f4c9fee6 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 355e80ddce 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b23d37cabc 47: onsuccess: 1: Successful build after linux: 10 commits discards db2045bab5 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards b1cedfa74f 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c0584a6d25 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 2b8a9824b5 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards e33353919f 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards 905dab919f 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dc1c5f71e8 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 2ebd895110 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards d1e5082f3e 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 3b5b1c694d 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4d0271161d 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d4b4d0ddcc 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new c8ce5d067b 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new c6ff00d333 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new bb6e66aa0e 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ef97cbcb4b 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 5936807550 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new c14b0c6d21 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 331900896d 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f5531edb78 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 222644aefa 47: onsuccess: 1: Successful build after linux: 10 commits new e62b591a0d 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 09a410eedb 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 190b074911 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 73939d6e18 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ec5e205ef8 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new be1702e4ea 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 535d9cece6 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new bc3c94fc43 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 5696d454e9 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fbc3e07eb5 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fc9b2a798c 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 2df995d8e8 59: onsuccess: 1: Successful build after binutils: 2 commits new 156471f55c 60: onsuccess: 1: Successful build after glibc: 2 commits new b11adf4110 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 70c87507be 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new f98ab25693 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 9b6e5f26aa 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1d450328d4 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new af30b24fa0 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 2d8126edeb 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 3ea4ec630e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ed631a6dfd 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new dcf84ff61e 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new e93546cfbf 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 1fb73b8171 72: onsuccess: 1: Successful build after linux: 12 commits new f0c0c5f252 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6dc21ef5c6 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 979fc2bb18 75: onsuccess: 1: Successful build after linux: 44 commits new 8015553d44 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 166547fd11 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 72901da79a 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new a67bdf7f68 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 51e5944289 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 654ff1aa99 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 614d48269c 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 317578ac75 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new fe912d8552 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 9509498344 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 5c90200fc8 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new f75ac94d9d 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new f75aa29a5f 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 6cb99e41d2 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 547e854faf 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 9e64e6bbe9 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new d05b6a5625 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new ce8a9ed96d 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 80cffa9b1a 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 90fab2d909 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 45f6b2ebd4 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 06330bafd2 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 7464a8d127 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 214c340cb6 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new d9612c6040 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 492c2204d7 101: onsuccess: #2130: 1: Success after binutils: 81 commits new e914f6d9b1 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 6e516c8bf2 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 1de8b7e46d 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new a670a3599d 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 0136ac0004 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 2270aab985 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 4c18f3de30 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 0ce0fb7f63 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 219b0d1a90 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 0901925fef 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 784c777fb9 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 4321fccf6f 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 1527e83bdf 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 2a51b2a11b 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 056225ee53 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new edb21833ab 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 9be5f7f119 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new f78f9050ed 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new a22d229aa5 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new ad309e45ce 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 62549b94b3 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new fc4ed9752d 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 51792b1e43 124: onsuccess: #2159: 1: Success after linux: 23 commits new 63fa2ce468 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 2db7f0ef81 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new bcf4041417 127: onsuccess: #2162: 1: Success after gcc: 9 commits new fd879da53c 128: onsuccess: #2163: 1: Success after linux: 23 commits new 884bf57602 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 445d9e6438 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new d2d7d94b98 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 70da955587 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 5f82c4e83f 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 3bae8ff2c9 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 164a44589e 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 82758d651c 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new bac1339088 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 0ebc2ed8c0 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 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 (2f0bd18e1b) \ 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 1748 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30520 -> 30652 bytes 04-build_abe-stage1/console.log.xz | Bin 72676 -> 72204 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 9268 -> 9280 bytes 07-build_abe-glibc/console.log.xz | Bin 240244 -> 240092 bytes 08-build_abe-stage2/console.log.xz | Bin 204836 -> 202724 bytes 09-build_abe-gdb/console.log.xz | Bin 37732 -> 37964 bytes 10-build_abe-qemu/console.log.xz | Bin 31532 -> 31408 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2620 -> 2544 bytes 13-check_regression/console.log.xz | Bin 12988 -> 11652 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 178 - 13-check_regression/mail-body.txt | 143 +- 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 773 ++-- 13-check_regression/results.regressions | 101 - 14-update_baseline/console.log | 70 +- 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 | 145 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 101 - sumfiles/g++.log.xz | Bin 3443752 -> 3412384 bytes sumfiles/g++.sum | 197 +- sumfiles/gcc.log.xz | Bin 3015508 -> 3007780 bytes sumfiles/gcc.sum | 6283 +++++++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 1034636 -> 1031712 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202032 -> 201884 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 414524 -> 421172 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 3948 insertions(+), 4199 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions