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 17218a2547 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 5f29bed60f 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 702d00ada5 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 8c5f744d4d 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards e5c6783050 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards b58a98fe71 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards baae8f7796 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 1e7e6aadd4 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 51a6460513 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards ecf97162fb 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 4800a7a51c 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 0f32eabacb 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 200ce4967d 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards b244bce66b 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards fdf1701ba3 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 66e10da92d 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 0a5f81bb71 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 5512160d9d 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 74110b56e3 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards a9cec742a7 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards bae288b59c 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 3c9e69fac3 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards fe1c350fdf 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards ee536b4881 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards bf14c7dec4 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 76d2722e40 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 9ca162168b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 31919ce359 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 2f907ca3fc 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 7536b1a001 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 3604f444fc 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards a1eef42ebf 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards b433a80d76 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 68199eaaff 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 6d8b808e6e 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards ba7d110a54 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards d10c6180f2 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 5fafc2e891 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 6453ff180b 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 699351e97b 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards ef039a9724 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards ec60685ff7 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards ba3ac232b0 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 12e402e362 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards fa0f28a658 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 3add4cc5d0 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 30cb288828 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 052950b40f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards e9727e2345 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 0380ba805e 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 6559c8151c 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards ef8951b2bf 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 69c1db87e6 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards a7877d56a4 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 7d8800fa46 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 872d9c3328 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards bb543638f1 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 5ed96dfda4 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards ec5bac885d 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 0489aeafd9 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 16b0da4fa8 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards d43bd67e7a 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 07d7784c26 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 05c2e8edfe 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards e3f330478e 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards daa2c5d96f 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 6db030e5ae 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 037c8cb083 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards c9b11eb56d 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 7441ebef4f 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards f4aae1d48d 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards bcfa17dc4c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards beb534e163 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 3f32bf8eca 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards e1bda16b66 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards c3b60e8067 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 6b60c9c66f 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 84ba18c0f7 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards d7aca6ea3c 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards ee088b87c6 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 08a01c5e53 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 9898f5f1fb 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 9ea4d83aa5 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 9d92855324 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 0a2a2544ce 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards d42c502850 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 2b33044219 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 6aa3f0bc3e 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 0d0a8ae14b 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 51029b4b11 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards b91bc1f0ad 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards ac2320e2f3 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards d8884ee6e5 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 313e571864 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 35f0559d16 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 61f66db3bc 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 6c82e5eb8c 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 958f20b886 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards f5ed7cf000 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 401797e9b7 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards ced15b4786 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 4573c3c0ed 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new ebd53026c1 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 5f6ede2ff8 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 8c9f6baa43 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 0fbfa5a634 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new de38d86801 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 66c152703f 301: onsuccess: #2118: 1: Success after linux: 16 commits new b608db89fd 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 3485756c0d 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 18d92c923e 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new e800728c36 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new eea3093a23 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 55b165bb90 307: onsuccess: #2124: 1: Success after gcc: 2 commits new bbc71d1571 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new c4cf95d7d7 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new c8769e3b61 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 422375620e 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 94e9aef106 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 9ec3c2a2a7 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new f377976a29 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 902f69c40f 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 547341ec11 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 611f6d69bb 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 01dcdc4d2c 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new aab99f3084 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new f69834a310 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new b805ff64b5 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 2966cdfba9 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 7a33b26c63 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new cf32b3739a 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 541340611d 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new c4e4c534f5 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 8ab1059922 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 11629f7a12 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new da5855f53c 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 356f240792 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 853469ec78 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 0743dc022e 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new da40f8bf37 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new a7e773ebeb 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 39eb23c4fb 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 5260c4fa2a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new cca2670b69 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 1fa46a8323 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new ac43432cb2 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 026834b9b0 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 83dae4a708 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new b4fc00d608 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 61644a76a0 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 3b132be110 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new d4e1e9ea74 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new ebbcab6fb6 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 990f479d67 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 30c22fc2a6 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 968c6a6abc 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 7ba5b904bf 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 22e5b6d190 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new f76a860c35 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 30a59ccef0 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 0d85506880 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new cf3cc03dc2 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new dd9e8c4862 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 79bd89044e 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new c396244e10 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new ae458b159a 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 74af86ce04 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 9f7bd9ff57 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new ae0fba5b9b 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 191b5901d3 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 15e97fc96a 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 86fd3ccad3 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 6a4bba0402 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 2bdce65cf2 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new ed5e36fa57 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new aa95b2d17e 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 55f8f09597 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 1c0fb77a52 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 7c7102eda1 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 81c7a2203a 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new df354603ee 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 623153d069 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new ee8ee2251f 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new a489745c37 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 65e223b683 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 695a2bf3a5 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 75c3ad7c79 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 089b423d23 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new d80e1f05e5 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 1a8e5cf26a 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 562574e476 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 3ab854d060 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new f44d7d71b2 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 9d8f106de1 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 986555f5d9 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 52ea0cb736 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 1e663a9042 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new e3b9fdbaa4 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 5480015ec1 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 16af9fbb8c 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 0405b777eb 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 48db3fff04 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new d1da188a80 396: onsuccess: #2217: 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 (17218a2547) \ 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 1792 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31244 -> 31040 bytes 04-build_abe-stage1/console.log.xz | Bin 91500 -> 91984 bytes 06-build_abe-linux/console.log.xz | Bin 9336 -> 8612 bytes 07-build_abe-glibc/console.log.xz | Bin 235996 -> 236352 bytes 08-build_abe-stage2/console.log.xz | Bin 228236 -> 229732 bytes 09-build_abe-gdb/console.log.xz | Bin 38748 -> 38488 bytes 10-build_abe-qemu/console.log.xz | Bin 30800 -> 30832 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3916 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3268 -> 2984 bytes 13-check_regression/console.log.xz | Bin 9284 -> 7400 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 61 +- 13-check_regression/results.compare | 35 +- 13-check_regression/results.compare2 | 557 ++------ 13-check_regression/results.regressions | 35 +- 14-update_baseline/console.log | 64 +- 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 | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 35 +- sumfiles/g++.log.xz | Bin 2637436 -> 2650780 bytes sumfiles/g++.sum | 39 +- sumfiles/gcc.log.xz | Bin 2205296 -> 2186412 bytes sumfiles/gcc.sum | 2102 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 888848 -> 886596 bytes sumfiles/gfortran.sum | 10 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2252 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216860 -> 217064 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438968 -> 434616 bytes sumfiles/libstdc++.sum | 27 +- 43 files changed, 1457 insertions(+), 1639 deletions(-)