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 531983cc33 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 8de1a61ad6 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 12e93408b4 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 1871e8d733 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards e9e8375fcd 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards b90bc11e67 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 89ebe5671a 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards e6c7e32e7f 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 1c9a8e3951 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards dbf9890d02 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards cffc987933 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards e83307dd57 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 5eae999a38 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards bd2ca0b42c 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 53e7ab9670 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 1b6b5f4c31 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 4b43491f64 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 76cca0f78d 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards f5d48a5fba 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards de4608cf8b 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 16ee579285 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 6b9cd94a62 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 333a53d8d3 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards c7e7a36caa 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards a2413d4fdd 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 2bab471ea6 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 11027f54c6 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 21c09e845a 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 557c6c5edc 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 0fc9bee10d 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 4fca1d7451 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 48f4aa2f05 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 75f9f44148 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards d67c9d0e5d 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 671a9096b6 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 9052c946ef 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards a277856390 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards de8d965520 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 2c6899fa6b 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards c42a45810a 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 9b37a77e72 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards ab97d6a9dc 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 193d696582 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards d1f3785cf1 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 9f8c71a9b8 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 84a472cbf1 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 40599d572b 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 5d35f03211 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 303f5a4126 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards fc3d0697f5 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 3e615efb37 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 3a949d918f 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 621d2b3f61 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 5f47bccbc7 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards eacd0c7e69 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 781abce72f 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 1324ba9283 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 76a77c2be1 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards d51f9a1964 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 0a84d89044 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 23a7f59a7c 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 7d68ed7ea4 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 1c50c57cde 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards dbc8526681 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards c045bd4062 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 3051148946 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards ace3d26754 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 92824673af 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards cd9c63c78b 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 8d7c21f6a1 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 3acfafdfc4 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards e0216145e2 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 917ba96cb4 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 78973d0811 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards dd28aad890 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards a1ac9c7493 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 40fdd39ee1 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards c99123ef96 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards ca1790a4e4 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards ab4cedb9bd 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 6b39a72224 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 149108daf0 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 4df974a83f 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 33f514a94e 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards e2a26665dd 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 06c7892017 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards fbc51565bd 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 51c6f84e14 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 2e969e5676 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 30ec737c10 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 099d9f19fa 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 019d130f81 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 10c11bebcc 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 276df279d9 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards ff8567fdc8 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 6bd6859e0b 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 0fdd16c443 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 9920a37271 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 3e6309063a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 7a2eb97e5b 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards f7815925b6 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 2e14ba10ef 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new d3ba6a3cc2 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 8052cece19 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 5b420d668a 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 0b18b93a98 301: onsuccess: #2118: 1: Success after linux: 16 commits new 0dfbc8fdfd 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 6642aa1eed 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 6467b880a4 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new a4e3dce242 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new b1a78ce0ac 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 5123171c40 307: onsuccess: #2124: 1: Success after gcc: 2 commits new bab72d104c 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 8e9e801229 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 1f6665a073 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 2204c8e2b2 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 31f26ac5d6 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 7d755e5416 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 9c3882334b 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 5cf26b4633 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new eebc0b217e 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 45c70be91f 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new e8f28b1ad8 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new f67238a3f3 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new e9027e2b49 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 81f79419ac 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new c290c114b2 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 90b96ea145 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new a427e145e2 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new c3a50bc0fb 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 24c4e205b8 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 4960cddc0e 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 3b28df09b9 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 195ccdd0ea 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new b02cb68e31 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 98723018bc 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new ea0f5c1ab3 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new b7b383a730 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 566a0f33dc 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new b4f421b97c 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new e07f932de6 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 2e0fea03a3 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 0bdb233794 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new e0e8710857 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 857a27bba8 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 4b2edbd718 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new cb0724bdcc 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 5d34816400 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new d9461a2976 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 69516c06f9 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 12804c0c77 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new b3b9517118 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new c516a906cc 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 646f5c81d2 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new def66db8cc 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new ca302121e9 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 724b19e353 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new d2145649c5 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 2fe98342eb 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new d06c2fa18b 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 8d86d79563 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 05a1926501 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 43f4383d9e 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 838ffacb50 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 85e6f0cbca 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 2143ee9c42 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new db0b499264 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 48ef642f6d 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 05e20aadb7 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new f56f2a6b15 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new bc37d0aa93 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 239cd8791b 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 147e21802b 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 124f741862 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 10b301c4b3 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 0a98fc5b5d 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new fc4415956e 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new c26218715d 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 536022d699 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 67e50d3151 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new f01f687c37 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 33137acc62 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 43eae9c7d6 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new abd7beedfe 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 80391536fb 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 407438eb2e 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new bb3686f21c 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 618a5610fe 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 237a02a44d 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 443b4d544f 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 180d9311a9 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new a7a13d8fc2 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 0b7cd3550c 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 529ed69d61 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new a703553571 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 9d1475df0c 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 068ab9312d 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 460b62a8d5 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new dbca80fb74 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 406b6e645f 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new fc349e943c 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 24b225adda 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new bc610a8971 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...]
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 (531983cc33) \ 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 -> 1820 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 30868 -> 31620 bytes 04-build_abe-stage1/console.log.xz | Bin 91792 -> 92208 bytes 06-build_abe-linux/console.log.xz | Bin 9376 -> 9416 bytes 07-build_abe-glibc/console.log.xz | Bin 235792 -> 236904 bytes 08-build_abe-stage2/console.log.xz | Bin 228136 -> 228564 bytes 09-build_abe-gdb/console.log.xz | Bin 38460 -> 38612 bytes 10-build_abe-qemu/console.log.xz | Bin 30636 -> 31404 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3104 -> 2832 bytes 13-check_regression/console.log.xz | Bin 6780 -> 6536 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 45 +- 13-check_regression/results.compare | 20 +- 13-check_regression/results.compare2 | 51 +- 13-check_regression/results.regressions | 20 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 47 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 20 +- sumfiles/g++.log.xz | Bin 2651172 -> 2640088 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2205476 -> 2195232 bytes sumfiles/gcc.sum | 2020 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 893624 -> 891064 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216992 -> 216844 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434720 -> 437620 bytes sumfiles/libstdc++.sum | 33 +- 42 files changed, 1182 insertions(+), 1210 deletions(-)