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 d1e6239476 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 8df5dad405 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards ad2dab249b 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 260e728ac1 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards b4af7c55c7 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards d9f18e8ea9 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 425c875e3d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards bc6b10f175 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 1660cf75bc 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 9f3cbeb147 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 7717f3a495 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 77cf7c1d76 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards b11bb7c187 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 97da0e7c53 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 17abc20efc 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards e15704d0ed 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards e16cbdc64c 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 84a7759d5e 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 28026ccecc 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards d712d249cc 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 789cacd147 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 72f2c48b6e 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards cb643825a8 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards ffc0f9594a 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 433dcc1f2a 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 2e086208e2 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards d861b54c9e 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 697817bd0d 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 69a53a2a0d 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 7cd198d27d 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 125606fcc0 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 39e9d37304 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 0d9dfedce1 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 7e2ea3695b 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards bb717a39bd 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 309715824a 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 75b7ab91d6 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 2a7fdfaa38 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 3a12a223ee 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards c48b80e3c7 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards c3d1817a87 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 8700d2d611 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 00dde5ca8c 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 21f6f70fe5 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d97df4f283 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d2d1090a45 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 376fc601a9 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 49a93ce09f 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d0c3ae1295 75: onsuccess: 1: Successful build after linux: 44 commits discards fbdbe1428b 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 403a4dfb36 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0f650ce7ed 72: onsuccess: 1: Successful build after linux: 12 commits discards c5ffa03a1a 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 2cfc0a7708 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards ff6ff97358 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 9d44f3f2ca 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c0d9726581 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 1cbed6bb0e 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 8ce0322337 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d2746340a5 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 26792a4096 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 9184b8a72e 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 8f84ea0f86 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards e8bd447513 60: onsuccess: 1: Successful build after glibc: 2 commits discards 812bbb4b87 59: onsuccess: 1: Successful build after binutils: 2 commits discards a384f25ac8 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards a3ab8f43c2 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0a0193edda 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1e49b74b3a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 27ea671e50 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards e78e6bd67c 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards ea5c5ff133 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards c135f8b8c3 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 04e32ec2d0 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4fe6c1889b 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 4b3e29079e 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 00937d8e4c 47: onsuccess: 1: Successful build after linux: 10 commits discards baf213d5e6 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 3405b5c265 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8a4dd860b6 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards e03897d800 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 45cb39253c 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards 3abf44cb46 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9e4e6b7a23 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 2182a0bbba 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards c96982e7d1 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 5bc08ae354 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 970bb6a7bd 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 95854e83f5 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e06b8ac5a6 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3cdfe394ba 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5e7ddca46d 32: onsuccess: 1: Successful build after gcc: 7 commits discards 7bbdbb284c 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 68dc98ccfe 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards d2c6392f85 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 32f4413646 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 862b75195a 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 266752ea7d 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 40265fa132 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards eb4fc5c98c 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards afc41b6e5f 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8c9a8570e1 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 83a0202800 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 09317bb49f 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3ea8cbbbd6 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6ed11cbefc 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new f49a14f25b 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b86f564f57 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3cdc9af63c 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new b83149e801 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 30d9fac59b 32: onsuccess: 1: Successful build after gcc: 7 commits new 93d0fa331d 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 97cfbb65c9 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 69da4d3ff7 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 33cb99a8ab 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d0ae9cf602 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4d7b024a5e 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 287e5748e7 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 7dd8589257 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 4c72d83118 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c1c3c4abd4 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new f3c679d332 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 9dd2ec038c 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 211541b3e6 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ac7e6dea05 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new d0581367b6 47: onsuccess: 1: Successful build after linux: 10 commits new a4e97b03ee 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8199cd5567 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new ca46418213 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 21509d3092 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2eabc7b6a7 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 34c677ad49 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 8912f30156 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2bffd99cd7 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 4b8359d462 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 07ff7f1372 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8f7f705671 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 4d2cec1b9f 59: onsuccess: 1: Successful build after binutils: 2 commits new 0212b8b2f1 60: onsuccess: 1: Successful build after glibc: 2 commits new 8ac1e22697 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 7e5ba51abe 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new e72dd2e6a8 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new da44e1b5f0 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9bdea36937 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ad11fc55c6 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 1d9f68206e 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 844e00506a 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c8a06c1f0b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new eebd049f60 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 442c4905c3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new ec19161b1a 72: onsuccess: 1: Successful build after linux: 12 commits new ed484e7242 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8adfe20fcc 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 5d6494328e 75: onsuccess: 1: Successful build after linux: 44 commits new b8604be9dd 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dcefbbee4c 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 16eb850ffa 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 6f84471467 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 29c8c9c494 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 24cc46038f 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 5674c1e550 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 76702d26d1 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new ae8d1bf782 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new c67cf23b08 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new dc79cf066e 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 20e0f4cc4a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new ed5faae3a1 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 21c36ae947 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new aec36b9432 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 645a84d9e5 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 80bae3d089 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 9d60f41ce9 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new ebb0993452 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 79e165bdc9 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new afbc3c61d7 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 0612b6d22e 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 75f8bae4d1 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 1d9598773c 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 4b14774ded 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 07f64af26c 101: onsuccess: #2130: 1: Success after binutils: 81 commits new d51a1351c0 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 3d2c714f22 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 634cc047e5 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 67209d9c96 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 0fa75ee2af 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 3aba82c268 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 3838aa8cbc 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new bb058e26c6 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 96166ce217 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new cf13b9283b 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new ba903996b3 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new b928d77d38 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 77b5261ce2 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 89d08d985d 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new f1ff3038e9 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 87bb79695f 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 8ae910c264 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 5cf1cfe971 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 177ad65a9d 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 72757b2d9a 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new da677ec666 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new d8f254ac92 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 0c1215e0ff 124: onsuccess: #2159: 1: Success after linux: 23 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 (d1e6239476) \ 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 1692 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30588 -> 30548 bytes 04-build_abe-stage1/console.log.xz | Bin 72648 -> 72764 bytes 06-build_abe-linux/console.log.xz | Bin 8832 -> 8728 bytes 07-build_abe-glibc/console.log.xz | Bin 240028 -> 240044 bytes 08-build_abe-stage2/console.log.xz | Bin 203412 -> 203300 bytes 09-build_abe-gdb/console.log.xz | Bin 37704 -> 37920 bytes 10-build_abe-qemu/console.log.xz | Bin 31504 -> 31612 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3932 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2944 -> 2916 bytes 13-check_regression/console.log.xz | Bin 5648 -> 5508 bytes 13-check_regression/mail-body.txt | 39 - 13-check_regression/results.compare | 43 +- 13-check_regression/results.compare2 | 35 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 41 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +- sumfiles/g++.log.xz | Bin 3413268 -> 3405196 bytes sumfiles/g++.sum | 55 +- sumfiles/gcc.log.xz | Bin 3030060 -> 3032656 bytes sumfiles/gcc.sum | 4517 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1026892 -> 1034192 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202228 -> 202076 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423132 -> 420428 bytes sumfiles/libstdc++.sum | 8 +- 36 files changed, 2347 insertions(+), 2497 deletions(-)