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 22218a2e5a 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 450f30d492 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 0d7e2f6455 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 6aba51a1fc 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 74f6a0bd04 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 9c342d0c84 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 62a1a770e5 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards bb9a26491f 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 0f8bd032cb 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 69666dc9a9 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 015a5b072f 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 1f492c06a1 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 2a26378aa2 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 6e43586169 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 78831c1cfd 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 16cd349383 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 37d6dcb946 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards ce98df23a9 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 0d7c785a71 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 04af39b9f0 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards bd1270d101 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 1725cac99d 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 4dd9aa1f6a 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 3256fe5eee 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards c42f0a1812 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 0f4df8aec8 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards feb058d58f 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 7a22e65646 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 80ad6e13b9 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 04b72780af 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 21264f1b13 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 3f2c606640 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 45719a330a 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 2a9a71a420 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards c073f9d3db 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 726025ac66 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards fe22393d59 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 39f4a1b798 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 9ded356e65 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 23f8204fbd 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards cfd06e24b0 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards ff02477f4e 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 7bca415181 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 68847552db 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards f43cb6ff69 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 824de7865d 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards afbcd49a44 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 0d7af62a22 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 1851c30f60 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards bc81afb17c 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 3e277b0413 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 000c1e7f8c 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 52de90d588 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards f49095129b 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 5b74fa32ea 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards d207680feb 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 581a6cf96c 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 30f363efef 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards f88a00b2c4 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 5f95ec78fb 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 9061ae6acc 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 3464ddb026 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards f58f2c75e6 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 711ab3d832 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards cda2787f74 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 2874a33cec 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 09780ccfd5 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards bf48ee3235 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards bb0000e4cf 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 5e83c280e8 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 5b6809d7cf 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 88d4a4d1f8 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards d4fbaa667a 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 1c1f8cbf86 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 1459ea44d1 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 18e303f8b1 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 23c9d28d48 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 80de97cf78 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 132a0d11db 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 4ae18547a3 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards c40cc1850d 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards d21c55d731 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 4bb9c47cd0 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 35ccf06fbe 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 5c9f3b5221 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards f597b15025 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards de8c566ac0 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 83dc123e07 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards ad58a42a48 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards e3e3cabf96 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 274de1f6cb 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards acf3bf9e23 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2cf4006b6f 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 2782b74b74 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 00bff74630 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5ad4e371c7 75: onsuccess: 1: Successful build after linux: 44 commits discards 4c8dae6a62 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 596dc1e4c5 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 516a96a491 72: onsuccess: 1: Successful build after linux: 12 commits discards 9911c3be18 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards b1b0957b27 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 3aaad0eb3b 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 38c6028b1d 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new a03c098fec 72: onsuccess: 1: Successful build after linux: 12 commits new ad1cde4aaf 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fc768470cc 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 51ae1faee6 75: onsuccess: 1: Successful build after linux: 44 commits new 13c26c26cf 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new feccadf3ef 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new c2a5319622 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 8ce6b3a502 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4da74eda18 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a1fe1256ad 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new bc67c34f64 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 764cd2bf89 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 1661cc2150 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 10b7e42fa3 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new ee6c374e81 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 95e31baa5a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new a6cb5bbca9 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 1269991640 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new d1960f87b2 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 67c2f21834 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 32dc207869 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new a004202215 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 3553982143 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 3bdefa4dd9 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 4f64ebebbe 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 1b259620b5 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new f690b5452a 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 5492f156ae 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 1c3762e792 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new d62d670f98 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 99015e63fd 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new b0b63fbb0b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new d0a0b92bad 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 0e5997b3cf 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new c014068a1e 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 507f7b9151 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new cc4d5a1838 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new e9a164f6ba 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new fe41397130 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new dffecb1d22 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new e332748def 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 74b1301e96 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 8fef47ca9f 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 7b82ab00c1 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 42aab777de 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 683dc598d0 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 315e673f0f 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new da0e62e672 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 956b7cd1e0 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 7d399113f0 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 5842eebac2 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 3ac48cf542 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 1d00f27910 124: onsuccess: #2159: 1: Success after linux: 23 commits new 4feba58d50 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 4ab13254c5 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 0e15d94ca6 127: onsuccess: #2162: 1: Success after gcc: 9 commits new a12b970c40 128: onsuccess: #2163: 1: Success after linux: 23 commits new a576061e22 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 1049d360ea 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new ff3bb5ba7d 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 96427b939a 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 4e1d510c9b 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 827a8e9af9 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new e56d500351 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new ca2f8474e9 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 4008dc44c9 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 46b713fbe0 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 4c341c1b28 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 75517dbb15 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 3d92732235 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 5b83db90d7 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 4f29b97e69 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 669a411ae7 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 2af70daf59 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 43f0b9b576 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new b62853d59c 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 079eeaa5ce 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 0e5495707b 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 36d0a79838 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 550918f1cd 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 0344969ff5 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new b966d8d40c 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new dc02457201 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 46864dbd32 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 12dd0c383f 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 5b55a6ed7d 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new dc45ac7bfa 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 3cdff9ecd4 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 84b5ea73c9 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 12f6f57c1b 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new b92616319b 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 2a2c291883 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 0aedc64490 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new ef1b6c4a09 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new a144d890b1 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 3e12cc140d 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new da43183c45 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 0b2f795704 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new bc660d614f 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 9cc049ddc2 171: onsuccess: #2206: 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 (22218a2e5a) \ 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 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30872 -> 30508 bytes 04-build_abe-stage1/console.log.xz | Bin 73836 -> 72864 bytes 06-build_abe-linux/console.log.xz | Bin 9484 -> 9024 bytes 07-build_abe-glibc/console.log.xz | Bin 239708 -> 239540 bytes 08-build_abe-stage2/console.log.xz | Bin 204500 -> 203100 bytes 09-build_abe-gdb/console.log.xz | Bin 38052 -> 37352 bytes 10-build_abe-qemu/console.log.xz | Bin 31656 -> 31716 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 4144 -> 2900 bytes 13-check_regression/console.log.xz | Bin 26556 -> 26296 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 346 +- 13-check_regression/mail-body.txt | 224 +- 13-check_regression/results.compare | 465 +- 13-check_regression/results.compare2 | 7353 +++++++++++++++++-------------- 13-check_regression/results.regressions | 154 +- 14-update_baseline/console.log | 68 +- 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 | 226 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 154 +- sumfiles/g++.log.xz | Bin 3400624 -> 3405488 bytes sumfiles/g++.sum | 5874 ++++++++++++++---------- sumfiles/gcc.log.xz | Bin 3007952 -> 3041640 bytes sumfiles/gcc.sum | 4842 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 1035680 -> 1032700 bytes sumfiles/gfortran.sum | 22 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202704 -> 202256 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423672 -> 422684 bytes sumfiles/libstdc++.sum | 6 +- 44 files changed, 10597 insertions(+), 9208 deletions(-)