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 9cc049ddc2 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards bc660d614f 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 0b2f795704 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards da43183c45 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 3e12cc140d 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards a144d890b1 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards ef1b6c4a09 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 0aedc64490 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 2a2c291883 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards b92616319b 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 12f6f57c1b 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 84b5ea73c9 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 3cdff9ecd4 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards dc45ac7bfa 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 5b55a6ed7d 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 12dd0c383f 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 46864dbd32 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards dc02457201 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards b966d8d40c 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 0344969ff5 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 550918f1cd 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 36d0a79838 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 0e5495707b 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 079eeaa5ce 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards b62853d59c 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 43f0b9b576 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 2af70daf59 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 669a411ae7 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 4f29b97e69 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 5b83db90d7 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 3d92732235 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 75517dbb15 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 4c341c1b28 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 46b713fbe0 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 4008dc44c9 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards ca2f8474e9 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards e56d500351 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 827a8e9af9 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 4e1d510c9b 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 96427b939a 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards ff3bb5ba7d 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 1049d360ea 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards a576061e22 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards a12b970c40 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 0e15d94ca6 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 4ab13254c5 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 4feba58d50 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 1d00f27910 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 3ac48cf542 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 5842eebac2 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 7d399113f0 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 956b7cd1e0 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards da0e62e672 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 315e673f0f 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 683dc598d0 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 42aab777de 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 7b82ab00c1 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 8fef47ca9f 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 74b1301e96 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards e332748def 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards dffecb1d22 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards fe41397130 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards e9a164f6ba 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards cc4d5a1838 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 507f7b9151 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards c014068a1e 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 0e5997b3cf 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards d0a0b92bad 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards b0b63fbb0b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 99015e63fd 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards d62d670f98 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 1c3762e792 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 5492f156ae 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards f690b5452a 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 1b259620b5 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 4f64ebebbe 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 3bdefa4dd9 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 3553982143 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards a004202215 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 32dc207869 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 67c2f21834 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards d1960f87b2 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 1269991640 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards a6cb5bbca9 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 95e31baa5a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards ee6c374e81 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 10b7e42fa3 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 1661cc2150 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 764cd2bf89 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards bc67c34f64 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards a1fe1256ad 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 4da74eda18 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 8ce6b3a502 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c2a5319622 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards feccadf3ef 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 13c26c26cf 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 51ae1faee6 75: onsuccess: 1: Successful build after linux: 44 commits discards fc768470cc 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards ad1cde4aaf 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a03c098fec 72: onsuccess: 1: Successful build after linux: 12 commits discards 38c6028b1d 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 2fadb9bee7 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new c335784d66 72: onsuccess: 1: Successful build after linux: 12 commits new 2fbd69b2a6 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3f3f728471 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 825a053775 75: onsuccess: 1: Successful build after linux: 44 commits new d6006ad73f 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9e036e2089 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 0101894773 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 59c423e429 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 10750cc932 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 525adb350f 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 272a8f3207 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 28243755f9 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 98801c9dff 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 5ef426bbdb 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new f41a959a0d 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 8ef6ed65e5 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new c650e47634 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new f01f9df4a9 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 60196e991a 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new c589f779fc 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 103f6f737c 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new a9227657d0 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new f81726939b 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new b9e2e7bef9 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 35387944bf 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new cfa17dbe98 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new ac25e9d8fd 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 7d99696c4b 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 65d809ef33 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new ec312fdcf2 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 17a593a1fd 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new c65dc656f9 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 69bafb7891 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 59f7b4bd79 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 0aa25e9127 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new d499270000 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 9ae80015ed 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 5fcda510bb 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new a15e81b6e4 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 5a0bd61c84 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 73fe7ab3fa 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 1c7291f439 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 9cb434d79e 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new c77c641641 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 38e8f46fc6 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new aa81e4dad1 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 820a3d9e08 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new d7ca793d10 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 2d3e0c97fc 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new d43919a076 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new e69a2e0da4 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 82c45aa40f 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 5103a3e987 124: onsuccess: #2159: 1: Success after linux: 23 commits new eb357676a9 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 1df0b2fb6f 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new d11f48cede 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 9f436cfd20 128: onsuccess: #2163: 1: Success after linux: 23 commits new 19c99490ea 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 91860e4c31 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 4b65b9c787 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 73eef4066a 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 34bed7f669 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new bb33f82c94 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 71782058c0 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 0900dfd3fb 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 7461a8884b 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new d41f45ef03 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 653e4aa71b 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new fe95e9fd29 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 99a3ffe21e 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new b01a867064 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 2d4705111c 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 96df226891 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new aac8cd95c4 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 0c43773f53 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 68771b79b2 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new adfc360083 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new e87f0c31ed 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new ba73217d1f 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 1b0cfa2e10 151: onsuccess: #2186: 1: Success after gcc: 2 commits new c402964017 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 0ce799a743 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 7e21a0f4d6 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 4ea84b2061 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new a3459fb57c 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 8f4e4eb41b 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 09c43b0bd2 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 276e0420f9 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 58d8db1c39 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 983ca60edf 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 44d50f2139 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new c1f20cc8eb 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new ab430c1f9f 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new ad93c4ad88 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 5803a1f853 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 882bc23060 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 606c83301c 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 5d9ea963aa 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 2caaab12a5 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 2078a43226 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 90ff28182c 172: onsuccess: #2207: 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 (9cc049ddc2) \ 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 1744 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30508 -> 30740 bytes 04-build_abe-stage1/console.log.xz | Bin 72864 -> 72672 bytes 06-build_abe-linux/console.log.xz | Bin 9024 -> 8544 bytes 07-build_abe-glibc/console.log.xz | Bin 239540 -> 238996 bytes 08-build_abe-stage2/console.log.xz | Bin 203100 -> 202920 bytes 09-build_abe-gdb/console.log.xz | Bin 37352 -> 37920 bytes 10-build_abe-qemu/console.log.xz | Bin 31716 -> 31968 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2900 -> 2808 bytes 13-check_regression/console.log.xz | Bin 26296 -> 16704 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 45 +- 13-check_regression/mail-body.txt | 215 +- 13-check_regression/results.compare | 93 +- 13-check_regression/results.compare2 | 5608 +++++++++---------------------- 13-check_regression/results.regressions | 93 +- 14-update_baseline/console.log | 78 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 217 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 93 +- sumfiles/g++.log.xz | Bin 3405488 -> 3411232 bytes sumfiles/g++.sum | 2996 ++++++++--------- sumfiles/gcc.log.xz | Bin 3041640 -> 3037936 bytes sumfiles/gcc.sum | 4465 ++++++++++++------------ sumfiles/gfortran.log.xz | Bin 1032700 -> 1029596 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202256 -> 202428 bytes sumfiles/libgomp.sum | 8 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 422684 -> 428700 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 5555 insertions(+), 8426 deletions(-)