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 cdb45e1f23 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards af768508cf 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 8062a8095b 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 6e0ddca995 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 0c2f7c4dc1 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards f7f9a24f56 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards d5f4bbca36 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 12a28bbea5 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards a4bbbdccc3 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards e5e7de6500 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 38ad6eb7be 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards bde7fb1ffe 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards e2d2ffd2c5 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 240b7bc6a8 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards eb2d99cfcf 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards ca14f79858 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards b030f23afb 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 6337f47844 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards fe8c8b13ac 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 87e8273c9e 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards b0f587b61a 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 248b2a0c19 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 129b5a8b1c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 004af1ebbb 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 44f0e08e96 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 5bbf98aae8 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 9b4f52cea7 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 55327714b7 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards df5cd1e91d 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 5289f7dd42 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards c887e52834 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 0ce39ba5b6 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards f1ea7314a3 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 1e7c802c84 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards aa0e5d4d56 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards f5b7b1df14 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards fa273820b4 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards fd1b03d57a 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 1167ad895d 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards ea5f563cb6 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 369e42ccec 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 291f8bbe40 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards a82bfec1d1 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards b4537da7f4 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 5f0e5fd2ad 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards bb79069d0b 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 2f417a39f5 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 1d930b5a5d 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 937ef2d9e8 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 8bb3f20680 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 7b96933d63 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 8b2b14eab8 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards c5def12f7e 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 33f70281d4 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards c2e5ade83d 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards b037deb5c5 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards eedfefb0b8 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards a26782c022 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 771fc3d7d4 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 1588e22d75 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 813f64184b 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 124a25e7ac 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards bba97b521c 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards c4456fc6b9 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards b39ff44eec 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 5af0f77026 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards e98eede53b 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 9375cee6f6 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 734d9b48d6 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 275870e58b 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 55aa4ba33a 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 8582db2722 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 09a5465ef8 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards b0741a61c1 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards a5f129140b 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 7f34d695b7 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards fdd556501c 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 2624e0bba3 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 7ece853457 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 29cd1d40f4 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards de8e713499 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards c5eb67ae41 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 564bcca12b 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 13b28028be 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 6ffaadf6ba 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards dee711f99c 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 4da5e12cce 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards fafd5e5d2b 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 047e2a5688 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 0580834284 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards ee6d6b5631 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards ea3e4e2b74 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 8e8a34e892 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards f1eb5228bc 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards f9de18ef49 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 4830deb053 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 4290834da2 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 5f91ecb485 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 488a687f3d 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 1492e7d152 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 98b39166e4 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new bd25b05064 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new a3962e2316 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 548c70a50d 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 8fc9814d89 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new b6fc51da5f 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 171d22db4f 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 0a91f3303f 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 971095ec5a 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 7740009629 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new deec42cecb 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 211c3142e7 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new aa1210dbc1 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new c52ebb793b 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 0f82c7a82f 259: onsuccess: #2075: 1: Success after glibc: 2 commits new d3ae270705 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 24db890b80 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 542d72e536 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 4292540224 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 85820443f2 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new e4fe04c99b 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new a0a23e0438 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 7e201ff13e 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 41ef52353b 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 6f1c182a1b 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 9210ee6215 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new b30b62f42b 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new e27ab4918f 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 45ed2030fe 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 1b363b020d 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new a51a561269 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 370688a24c 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new ed9cc9b379 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new f00c129283 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new e9e884ea86 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new f011bd5650 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 069688c068 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new fc0aabcf36 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new b2be42565e 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 382f534915 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new a04c393ce0 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 0e9af6bd1c 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 8f7a927670 287: onsuccess: #2103: 1: Success after gcc: 9 commits new f0412bf560 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new e63c889494 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 6e1382658a 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 9412e5853c 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 5a76bcc828 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new f91e629a13 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 30e1edc724 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 10531e9927 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new ec42cf2229 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 56864feda3 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new f99fe88ee9 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 752e5f6506 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new fe6d654bcb 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 3f443c669f 301: onsuccess: #2118: 1: Success after linux: 16 commits new 03842ffc31 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 236a498df6 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 532798623a 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new f1e12a0fce 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 26d244a081 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 753ba30aa1 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 658dbe2f2a 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 0700766aba 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 6dbcda94b3 310: onsuccess: #2129: 1: Success after binutils: 4 commits new d856f67222 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 5d0f0b113b 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 53d27141be 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 35bc0431fc 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 0e1a4d6252 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 002309c543 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 805d94f3a9 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 9d21ecb627 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new ae607ec4ce 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new b93941337c 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 8181817a88 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new d2c69c1f84 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 4db8175ea3 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new cd39c2db33 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 65b4fa5a9e 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 9d84a24b39 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new f76e79dd1a 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new dbc8a3cb91 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 3175843a4b 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new b59e74c0a5 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new d7307ae123 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 7d9c91cc9c 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new bd13890aa8 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new efa6db08e9 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new cf1fac97c3 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new b835586250 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new d5c8b94b61 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 29e557e25d 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 9c041cf139 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 7f7c41363e 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 0bb9bb4bbb 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new af556f5b04 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 261659033e 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 62afcac574 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new b3ed92b681 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 265d970880 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new f2d9fc75e4 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...]

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 (cdb45e1f23) \ 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 1780 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 32288 -> 31632 bytes 04-build_abe-stage1/console.log.xz | Bin 92688 -> 91888 bytes 06-build_abe-linux/console.log.xz | Bin 9508 -> 9436 bytes 07-build_abe-glibc/console.log.xz | Bin 238552 -> 236660 bytes 08-build_abe-stage2/console.log.xz | Bin 229728 -> 229280 bytes 09-build_abe-gdb/console.log.xz | Bin 39376 -> 39020 bytes 10-build_abe-qemu/console.log.xz | Bin 32340 -> 31960 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2540 -> 2868 bytes 13-check_regression/console.log.xz | Bin 6384 -> 5144 bytes 13-check_regression/results.compare | 12 +- 13-check_regression/results.compare2 | 42 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- sumfiles/g++.log.xz | Bin 2686892 -> 2689544 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 2239296 -> 2254864 bytes sumfiles/gcc.sum | 2418 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 897004 -> 896256 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214136 -> 213996 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 442204 -> 444492 bytes sumfiles/libstdc++.sum | 8 +- 35 files changed, 1299 insertions(+), 1313 deletions(-)