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 3de12d5bbe 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 95dd549be3 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards d7ea4fe558 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 2b264694bd 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 78ccd8ce15 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 12ab650e4e 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 1779b44c86 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 70ff20be62 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 3af5a56825 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 5b139598db 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 94db267807 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 8bbe5d4453 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 2195142926 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards e30a34ea00 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards d2b1ada7ec 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards a70250b523 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards bc82a4af18 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 70f822d000 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 302efe03ba 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards f8fb3e5a13 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 520f626004 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 3fb18f4cdf 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards d162682d1a 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards f406929eaa 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 9967dc2e72 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 3f55498d3c 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 9d220de1c0 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 95f897f385 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards c3955ab95c 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 0caf937690 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 5bcaaf497d 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 37f4770b12 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 1b36c876e4 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 19440b1314 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards fd890e289a 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards d26490aafa 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 2c8460314f 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 17548ef44a 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards ce9422661f 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards b6adea1a40 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 644898eac5 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 558ba61e7a 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards d56a4c349c 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 15a21bb874 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 68163fe3e3 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 94c50038cc 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 3777669df2 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3b55e073bf 75: onsuccess: 1: Successful build after linux: 44 commits discards 3231d7a1b5 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 04cc44caa7 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f57b1a9352 72: onsuccess: 1: Successful build after linux: 12 commits discards 62609a844e 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards f6b06504fb 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 2b474f4f68 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards e8bc9503ce 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f8b1f73863 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 7dff385b77 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 2ba3d54ed4 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 70ef48e125 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eb07ae788f 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards fdb6c1e72e 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 44723d2c6e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 9685c4969b 60: onsuccess: 1: Successful build after glibc: 2 commits discards 2d690d2120 59: onsuccess: 1: Successful build after binutils: 2 commits discards 3da89673b1 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards f2e35fb29e 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 982668f64e 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1886864481 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards a52710b82c 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 8ee8b0549f 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 9e049155ab 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 000272c4d6 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 16c4a7ec78 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b232c9ba4d 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 2b073d33b9 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fb7706f369 47: onsuccess: 1: Successful build after linux: 10 commits discards 9d382cdb97 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 5aeaf681ec 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 515351a855 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 0676b0a647 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 2fa8eacf02 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards 6df17c9ef5 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 18860ec347 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 7642d25146 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 88df5a7d63 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 457a5e0a10 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 80bc170814 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0e1cd5f40e 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d6c8f371e5 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 1cc99d6de1 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 185a42876e 32: onsuccess: 1: Successful build after gcc: 7 commits discards 9b078be1e4 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 8c590af119 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 55ed90a622 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ed46be486f 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 832372cf79 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 2bd7f48c90 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 90b86f510d 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e9469cdcfd 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f870cbe6c5 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e531414c60 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 148afd3dbc 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new afc41b6e5f 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new eb4fc5c98c 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 40265fa132 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 266752ea7d 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 862b75195a 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 32f4413646 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d2c6392f85 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 68dc98ccfe 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 7bbdbb284c 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 5e7ddca46d 32: onsuccess: 1: Successful build after gcc: 7 commits new 3cdfe394ba 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e06b8ac5a6 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 95854e83f5 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 970bb6a7bd 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5bc08ae354 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c96982e7d1 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 2182a0bbba 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 9e4e6b7a23 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 3abf44cb46 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 45cb39253c 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new e03897d800 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 8a4dd860b6 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 3405b5c265 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new baf213d5e6 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 00937d8e4c 47: onsuccess: 1: Successful build after linux: 10 commits new 4b3e29079e 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4fe6c1889b 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 04e32ec2d0 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c135f8b8c3 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ea5c5ff133 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new e78e6bd67c 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 27ea671e50 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 1e49b74b3a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 0a0193edda 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a3ab8f43c2 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a384f25ac8 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 812bbb4b87 59: onsuccess: 1: Successful build after binutils: 2 commits new e8bd447513 60: onsuccess: 1: Successful build after glibc: 2 commits new 8f84ea0f86 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 9184b8a72e 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 26792a4096 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new d2746340a5 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8ce0322337 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1cbed6bb0e 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new c0d9726581 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 9d44f3f2ca 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ff6ff97358 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 2cfc0a7708 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new c5ffa03a1a 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 0f650ce7ed 72: onsuccess: 1: Successful build after linux: 12 commits new 403a4dfb36 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fbdbe1428b 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new d0c3ae1295 75: onsuccess: 1: Successful build after linux: 44 commits new 49a93ce09f 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 376fc601a9 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new d2d1090a45 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new d97df4f283 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 21f6f70fe5 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 00dde5ca8c 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 8700d2d611 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new c3d1817a87 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new c48b80e3c7 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 3a12a223ee 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 2a7fdfaa38 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 75b7ab91d6 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 309715824a 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new bb717a39bd 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 7e2ea3695b 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 0d9dfedce1 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 39e9d37304 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 125606fcc0 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 7cd198d27d 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 69a53a2a0d 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 697817bd0d 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new d861b54c9e 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 2e086208e2 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 433dcc1f2a 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new ffc0f9594a 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new cb643825a8 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 72f2c48b6e 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 789cacd147 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new d712d249cc 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 28026ccecc 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 84a7759d5e 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new e16cbdc64c 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new e15704d0ed 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 17abc20efc 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 97da0e7c53 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new b11bb7c187 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 77cf7c1d76 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 7717f3a495 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 9f3cbeb147 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 1660cf75bc 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new bc6b10f175 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 425c875e3d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new d9f18e8ea9 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new b4af7c55c7 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 260e728ac1 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new ad2dab249b 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 8df5dad405 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new d1e6239476 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...]
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 (3de12d5bbe) \ 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 1696 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30624 -> 30588 bytes 04-build_abe-stage1/console.log.xz | Bin 72936 -> 72648 bytes 06-build_abe-linux/console.log.xz | Bin 8832 -> 8832 bytes 07-build_abe-glibc/console.log.xz | Bin 239812 -> 240028 bytes 08-build_abe-stage2/console.log.xz | Bin 203132 -> 203412 bytes 09-build_abe-gdb/console.log.xz | Bin 37768 -> 37704 bytes 10-build_abe-qemu/console.log.xz | Bin 31372 -> 31504 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3136 -> 2944 bytes 13-check_regression/console.log.xz | Bin 6308 -> 5648 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 19 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 76 +- 13-check_regression/results.regressions | 39 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- results | 39 - sumfiles/g++.log.xz | Bin 3445444 -> 3413268 bytes sumfiles/g++.sum | 178 +- sumfiles/gcc.log.xz | Bin 3005912 -> 3030060 bytes sumfiles/gcc.sum | 3661 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1028604 -> 1026892 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202020 -> 202228 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2660 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 428724 -> 423132 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 2012 insertions(+), 2228 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