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 a169ffd4db 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards aaef5dd56c 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 19bde315a4 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 6861a9fdfd 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards fe2ce1fc28 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards e6b25e802c 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards e757937714 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 31b241e2c8 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 3212c1e449 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 27ce58616a 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 6a6052a2d6 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards f8ec0e3f45 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 3ced79c627 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards f593f8223a 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 8d7dff8bf9 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards ae94290bee 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 695dd949de 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 4a626fdf67 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 6f9381758b 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards ac847043dd 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 6b93147339 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards ce988183c9 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards c9c8538175 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards ed540afcd3 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 596507b6ca 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 58dbc6bb12 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 4e5d4b0545 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 5371fafd1f 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 54c7453bae 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 9a667303d0 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards eeea2e1054 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 655edf6e28 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 40f46f5ee9 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards bdb32c7a28 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 61ff9dfd54 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards ad3c56ba53 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 3952330c57 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards fe98d65f1d 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards e868ba18d2 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 5173c9cc0a 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 483d3aa347 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards dbc0e529ea 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards db486ac397 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 994185771e 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 8478a892df 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 04678670ea 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards fdedc291c3 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards a62f5d3c73 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 7c5621e0ac 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards a501f8aed9 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards a84fb90836 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 8b0ee36ba3 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards bd57928028 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards c48ddffbfb 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards caaf55c7ee 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards b2dc0ea528 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 3096843590 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 2aae54cb37 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards c1d3152538 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards dc7e9e2abe 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 22370251b1 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 68f7b2a428 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards c79c6578e9 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 62163893f0 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 2c144b2f72 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 435f8b0b15 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards cdd43a30da 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 111de3c310 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 59ecdccff3 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 2f449c667a 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 26652e7fa5 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards cf5c5e0871 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 74ab68369b 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 27070e8c30 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 38c3f0be0f 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 48e82347a8 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 6e2f28426b 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards b43e6f57d9 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 151fd5a701 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 02c834d192 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards db6f856594 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 96638408c6 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 1057602b9f 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 5229f7ece5 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards f759329cf9 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards b9367b764e 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards eec6a4eb79 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 0789d25a7d 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 1fd5478a6f 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards a1ff373d09 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards aaa1109b07 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards e6b76749eb 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards eb653621ea 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 98d436669f 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 4c9a2e469b 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards afd89847f9 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 93288efad1 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 6c56fb6a58 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards deec8aba51 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards b7c436ffd6 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 2be0047a4b 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new e6239a2153 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new e5373ab25c 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 6e37ac949b 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new cbe4ddc206 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 4bf8f10c60 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 3f0753cd1a 232: onsuccess: #2048: 1: Success after glibc: 2 commits new bf4b8503ff 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 551fc885ce 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 71a148434f 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 51be210952 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 9d5eb2a487 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 85a19aaac9 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new bb62fe9848 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 9fb8594157 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new ceb0148947 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 545139869c 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 636485bb76 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 56565cbd8b 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 4268ff125a 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 3294aa2931 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 99d6a78e3d 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 6204b496cb 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new d9f2de0381 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 4b35088261 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 5377044391 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 7b138d715f 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 31797fdbb9 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 33bf6dcd5e 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new c2a96fa9ca 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 5012fb437a 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new bba07774de 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 2f8b6e9644 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 5c677526aa 259: onsuccess: #2075: 1: Success after glibc: 2 commits new e179729ce4 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 163ae05f55 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 7f09867264 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 9af1464b6e 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new fac7628b60 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 952d305e98 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new ce79a6cb5b 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 03b283bf6e 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 6e305e0af3 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 88270d4d4c 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 14e26ee0e8 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 6d165aff0b 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new bce30a9207 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new dc2cc44f43 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new c87b988684 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new b3d0795611 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 6f240c95d9 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 707f187aae 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new b5f0e9d02b 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 58499e01b1 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new efff1b63f9 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new b57d26e89b 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 9a2ccdf1ea 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 1560f9e900 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new f2b0a0492b 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 157e93d511 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 095d65ba74 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 002577dd13 287: onsuccess: #2103: 1: Success after gcc: 9 commits new cbf54b9a37 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new cf5011a06c 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new a6672c5f72 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 26567978dd 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 4a45ad45bd 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 281ed17b7e 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 6707838404 294: onsuccess: #2110: 1: Success after gcc: 17 commits new b77271993c 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 22bca62422 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 1ad73a3c0b 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 1e28039e54 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new e594d03bad 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 7538108428 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 34b0ec3627 301: onsuccess: #2118: 1: Success after linux: 16 commits new e2b3a39439 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 3b64602905 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 87e9c6546b 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new aca95207e3 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 488b320440 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new af7bedfb45 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 5860de09c4 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new d428edd3ed 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 0d1cabaf22 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 5f0eca285c 311: onsuccess: #2130: 1: Success after gcc: 4 commits new e3cf57c430 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new f46d763be4 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 26d1d8b8e0 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 4b9e574c7e 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 0cc5aa48c1 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 3c39fae6c1 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new c1bc3579cc 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new e4183ac01f 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 23f52cf36d 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 9af2e70c7d 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 3d6f8ef822 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new bce2b23642 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new f6371eb4d0 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new bbccae9988 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new b761d3db0d 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new cc06afe0f8 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new c260a4404e 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 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 (a169ffd4db) \ 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 1812 -> 1820 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 32216 -> 32120 bytes 04-build_abe-stage1/console.log.xz | Bin 93080 -> 92336 bytes 06-build_abe-linux/console.log.xz | Bin 9112 -> 8704 bytes 07-build_abe-glibc/console.log.xz | Bin 237804 -> 237388 bytes 08-build_abe-stage2/console.log.xz | Bin 230732 -> 232420 bytes 09-build_abe-gdb/console.log.xz | Bin 39448 -> 39492 bytes 10-build_abe-qemu/console.log.xz | Bin 31492 -> 32156 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3316 -> 2960 bytes 13-check_regression/console.log.xz | Bin 5216 -> 6440 bytes 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 37 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_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 2659084 -> 2663980 bytes sumfiles/g++.sum | 4 +- sumfiles/gcc.log.xz | Bin 2280920 -> 2248192 bytes sumfiles/gcc.sum | 2096 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 893364 -> 900684 bytes sumfiles/gfortran.sum | 12 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214020 -> 214032 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 430296 -> 446328 bytes sumfiles/libstdc++.sum | 8 +- 37 files changed, 1145 insertions(+), 1152 deletions(-)