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 f2d9fc75e4 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 265d970880 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards b3ed92b681 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 62afcac574 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 261659033e 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards af556f5b04 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 0bb9bb4bbb 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 7f7c41363e 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 9c041cf139 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 29e557e25d 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards d5c8b94b61 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards b835586250 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards cf1fac97c3 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards efa6db08e9 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards bd13890aa8 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 7d9c91cc9c 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards d7307ae123 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards b59e74c0a5 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 3175843a4b 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards dbc8a3cb91 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards f76e79dd1a 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 9d84a24b39 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 65b4fa5a9e 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards cd39c2db33 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 4db8175ea3 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards d2c69c1f84 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 8181817a88 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards b93941337c 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards ae607ec4ce 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 9d21ecb627 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 805d94f3a9 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 002309c543 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 0e1a4d6252 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 35bc0431fc 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 53d27141be 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 5d0f0b113b 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards d856f67222 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 6dbcda94b3 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 0700766aba 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 658dbe2f2a 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 753ba30aa1 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 26d244a081 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards f1e12a0fce 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 532798623a 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 236a498df6 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 03842ffc31 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 3f443c669f 301: onsuccess: #2118: 1: Success after linux: 16 commits discards fe6d654bcb 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 752e5f6506 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards f99fe88ee9 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 56864feda3 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards ec42cf2229 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 10531e9927 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 30e1edc724 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards f91e629a13 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 5a76bcc828 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 9412e5853c 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 6e1382658a 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards e63c889494 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards f0412bf560 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 8f7a927670 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 0e9af6bd1c 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards a04c393ce0 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 382f534915 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards b2be42565e 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards fc0aabcf36 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 069688c068 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards f011bd5650 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards e9e884ea86 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards f00c129283 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards ed9cc9b379 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 370688a24c 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards a51a561269 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 1b363b020d 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 45ed2030fe 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards e27ab4918f 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards b30b62f42b 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 9210ee6215 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 6f1c182a1b 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 41ef52353b 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 7e201ff13e 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards a0a23e0438 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards e4fe04c99b 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 85820443f2 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 4292540224 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 542d72e536 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 24db890b80 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards d3ae270705 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 0f82c7a82f 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards c52ebb793b 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards aa1210dbc1 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 211c3142e7 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards deec42cecb 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 7740009629 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 971095ec5a 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 0a91f3303f 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 171d22db4f 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards b6fc51da5f 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 8fc9814d89 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 548c70a50d 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards a3962e2316 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new fa2eba3abf 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new e7d9cf1ae5 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 648bb38f28 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 4ea4427767 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 8b5e3d3291 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new b2dd9179cb 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 8de2e91baa 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 000ee159d9 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new a8e3355632 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 4ab0fa5721 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new dca74602ae 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 0e79f3305c 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 34b653d6b2 259: onsuccess: #2075: 1: Success after glibc: 2 commits new c5e2549070 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new d2bf5379d4 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 51ab67b3ab 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new f4520e6e8a 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 7983456315 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 2d986d684d 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new aa238ed20f 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new d8ad50e757 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new e7fa75ce24 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 1d09dc1552 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 0e1d0391ad 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 37b263af83 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new a01680f22a 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 9052abf1d4 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new ca3b04da81 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 4f3dce7591 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 6063acfd7c 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 525dff966a 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 70f5e92afc 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new f105bc0b35 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 8dc5b92a9d 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new e300175f28 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 526573222f 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 24bfe2f708 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new c4f83aa6a8 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 98ea183ffd 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new aee3670e44 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 2057d90ab1 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 152e956aae 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new f421c0a998 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new d283e2dd0e 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 69c79dc452 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 11b0aec9fd 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 4c786c5e47 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new cbdd69030c 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 1e01c94ada 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 8a9fa998df 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new a8168d6ae7 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 8f1ca79af4 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 25025be39a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 6be5776620 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new b610955113 301: onsuccess: #2118: 1: Success after linux: 16 commits new 45ed7737a6 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new eace8801dc 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 1f62cac0c3 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 1e51bbc37f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 53d821608e 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new aa340e7613 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 01f69176c9 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 050cd1ff47 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 8b27564bac 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 3aac1d9b6e 311: onsuccess: #2130: 1: Success after gcc: 4 commits new d935232ea3 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new f217b6e58d 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 7cbdf1f032 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new dbf7c8df34 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 5da457b0fd 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 0ab2d837a6 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 14ec847cec 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new ccb890a747 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 68d970f443 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 7e07ccf74f 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 875a44bfb2 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 21a22d79ee 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new c606e19332 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new d97b0a705c 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 96fbd6a630 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 0238974eb5 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new d02974e9d8 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 17b713e27c 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new c304658684 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 091473f66e 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 84cf22f6a2 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 35160937c2 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new e78355e6f2 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 9fc7a864d0 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 4af79fbb2a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new db90266ef3 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 4917f9f824 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new e104652c31 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 29d53a2e54 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 1c1455cc4b 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 8c0e2121c0 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 276caafa71 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 3aad061547 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new eb00cc2d60 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new e491e77bae 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new e591fea4ea 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 64ec5ca78f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits

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 (f2d9fc75e4) \ 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 1816 -> 1832 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31632 -> 31744 bytes 04-build_abe-stage1/console.log.xz | Bin 91888 -> 91572 bytes 06-build_abe-linux/console.log.xz | Bin 9436 -> 9432 bytes 07-build_abe-glibc/console.log.xz | Bin 236660 -> 236596 bytes 08-build_abe-stage2/console.log.xz | Bin 229280 -> 227652 bytes 09-build_abe-gdb/console.log.xz | Bin 39020 -> 38968 bytes 10-build_abe-qemu/console.log.xz | Bin 31960 -> 31776 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2868 -> 2632 bytes 13-check_regression/console.log.xz | Bin 5144 -> 5628 bytes 13-check_regression/results.compare2 | 24 +- 14-update_baseline/console.log | 42 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2689544 -> 2668688 bytes sumfiles/g++.sum | 8 +- sumfiles/gcc.log.xz | Bin 2254864 -> 2275464 bytes sumfiles/gcc.sum | 2409 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 896256 -> 894868 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213996 -> 214112 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 444492 -> 436748 bytes sumfiles/libstdc++.sum | 2 +- 36 files changed, 1275 insertions(+), 1270 deletions(-)