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-arm in repository toolchain/ci/base-artifacts.
discards 9a8a253688 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 72f61bbea5 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards e0e1884ba3 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 424a41df7a 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards e37f64eb93 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 3ad63f468b 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 26884825a6 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 1709f8017b 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards ab724c014c 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 4975e4a99f 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 4246fe1298 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 808b3e24fc 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 108a4054e5 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 039a109ed2 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 42c96188a1 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 5659f629f8 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 1eab947d55 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 86a2de79fb 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards fe41eb86f1 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards c2d5cb4080 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards d3bce738c7 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 7889f66df9 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 3c1ed8dad6 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards c4c80097ac 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards c0705cc099 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards db7db3b9af 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 4d2d85dd14 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards a954a2608f 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards f43ce1fc35 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards ffd48ad854 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 3886f87f4e 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 336b81233b 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 646665077f 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards a3e15565d4 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 33a30a39c1 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards bbdff834fd 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards b8e64cb519 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 7179e17471 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 2ad74fbbb3 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 984fca8764 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 293de8915a 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 9a8ec8deaa 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 0f1f312096 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 9863289f9e 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards ab56acdc33 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards fdea0a5a91 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 6a49411235 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards f709b106df 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 8dd2a9fd4b 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards c62db366c5 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards de7aaed172 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 1f2188f72a 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 4013ffebe1 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 31d5adc4cf 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards a80c05ebb9 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 231c4397b1 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 4a67408d10 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards aac7e63107 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 0913dce4a0 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards ae59d47614 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards ad62226f28 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 5fbd865211 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards a9ce4bcd5c 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 3b5cf0544d 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 4ec782d1ab 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards c1158ec89d 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 7594e3df83 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards b0a0c5c804 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards a7a3c5394f 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 0213cfef93 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 955349a27d 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards b39b7f4e13 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards f7af4af87a 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards d945b97b73 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards d8afb06048 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 3478106284 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 76d0d3300a 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 38077fdf0f 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards f5b213410b 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 3ba67b6746 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 8949d9045a 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 29326b1c3c 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards d1f61b40b7 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 5b2d808253 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 27a37b9f30 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 99acb4c67b 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards b693c815e4 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 49daf14222 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 18c31d515f 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 65308fcbb0 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards ef4bc2c24b 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards e30485262c 301: onsuccess: #2118: 1: Success after linux: 16 commits discards d7ffe04d4f 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards f24f5fe5d3 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 99eda83bc9 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards fca52b4edf 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 53b7cc5f7d 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 7f5f8eedbe 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 53ef863315 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards a6462aa061 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards a314577259 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 63470ba3dc 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new dd31928532 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 0e326fd202 294: onsuccess: #2110: 1: Success after gcc: 17 commits new ff35778232 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 5ab3662dca 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 29e2f8e42e 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 3675a08e9c 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 8b244a70b6 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 3c783a617f 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 138697b5a0 301: onsuccess: #2118: 1: Success after linux: 16 commits new ff79e792d3 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 92fdb0f864 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new e99714551e 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new c34111983b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 1d5894bfdf 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 063990721b 307: onsuccess: #2124: 1: Success after gcc: 2 commits new b2b4a0392d 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 17155778ad 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 180f110d5a 310: onsuccess: #2129: 1: Success after binutils: 4 commits new d0a588f4bf 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 4d00ba9c5d 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 5df196101a 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 271a295f9a 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 95056b306b 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new dc11d9b663 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new fb96f39018 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 6b51c3ca7c 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 220e062f96 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new b9d2482f1a 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new f3970c34e9 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 54d583c7a2 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 52330ac1c6 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 90308832c0 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 8326e4bb32 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 4d781dbb9f 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 5159810fcb 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 8202546d9d 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new e8a5c75c2b 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 99317c0efd 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 08decbcddb 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new c315c2686c 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 6373477317 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 9c7eeba343 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 8251d91cdb 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 51aa600c10 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new f758829337 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 921beb0fca 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 9434ad0b1d 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 6a03e55117 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 004495709e 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 4013e272c6 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 815c5370da 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 580732a0d2 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 1f018e0676 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 0583c446c0 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 07d476bdb6 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new f9a15b1b3d 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 67c3ec68c8 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 7f5d929f8c 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new a87f8dfcd0 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 6574bc8021 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 34247f2bd1 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 495e5a364a 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new c406c07da2 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 5f59b7bb0e 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 7b9b90892a 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 41d04e9321 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 64680ab714 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new dcbd8d6270 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new dd75af96b3 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new a4fc1a9355 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 3063618a16 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 838e70d97f 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 30115e9bf8 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new f0ca65eba5 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 87b4abcaa5 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new a948050243 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 73269c1968 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 081cad49a8 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 9ac044f7d6 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 91792ee226 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 6bcbcb1a91 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new e49cacafb0 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new ed273a15ee 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 13724b65b3 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 5668d6f405 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new f9593092ab 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new d145ecfa4e 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 06a59a2025 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 10143ac2fa 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 6f89910d40 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 1491d8f7db 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new e942c5c91b 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 1bbed4add0 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 1adfc065e4 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new caf484a6a0 387: onsuccess: #2208: 1: Success after gcc: 2 commits new e2b6728ea1 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 855cf26439 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 11819f3295 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 7bf5da7c0d 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new dc78b06b15 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 413d592062 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...]
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 (9a8a253688) \ 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 1760 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 33984 -> 30884 bytes 04-build_abe-stage1/console.log.xz | Bin 92096 -> 91724 bytes 06-build_abe-linux/console.log.xz | Bin 8696 -> 8676 bytes 07-build_abe-glibc/console.log.xz | Bin 236632 -> 237048 bytes 08-build_abe-stage2/console.log.xz | Bin 228344 -> 228604 bytes 09-build_abe-gdb/console.log.xz | Bin 41192 -> 38104 bytes 10-build_abe-qemu/console.log.xz | Bin 32240 -> 32244 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3920 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2748 -> 2648 bytes 13-check_regression/console.log.xz | Bin 6560 -> 5984 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 7 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 9 +- 13-check_regression/results.compare2 | 62 +- 13-check_regression/results.regressions | 27 - 14-update_baseline/console.log | 36 +- 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 27 - sumfiles/g++.log.xz | Bin 2654048 -> 2642732 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 2206064 -> 2194796 bytes sumfiles/gcc.sum | 2134 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 892108 -> 894156 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214552 -> 214480 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438312 -> 438088 bytes sumfiles/libstdc++.sum | 28 +- 42 files changed, 1217 insertions(+), 1280 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