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 492b4280ed 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards afcaf18c9d 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards b846a27db5 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards de975d8efb 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards a742e2d190 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 6492212010 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 4f1f848de9 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 163bca96eb 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 30672d26b2 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 554c7da41c 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards a128889cb8 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards eb0edb197b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 86f7dc2572 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 5142cd04fb 301: onsuccess: #2118: 1: Success after linux: 16 commits discards f4beea77ee 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards a4d5965f56 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 7d04ebbd6b 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards da016e4e86 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards f934cdd84e 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 261cee29e9 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 1fd0f6e2c4 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 87a8a7ece2 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards a0f0cb4826 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 8f35990bc5 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 260759a908 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards fa860d2647 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 567d1bab9b 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 2de9cb4518 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 7d69cb40cd 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards acaf908e00 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 8ef73596d1 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 318fd144bf 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 28e7ab3181 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards cd8bafdd23 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards ed05aefda1 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards b54d500014 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards e2d1eaf296 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 6e86715ba8 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 28b58b063e 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards aa95f56ddb 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 8c60324f4a 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 9e80f1160b 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards f1f367c753 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 71546096fb 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards f5ecc80df6 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards f9f84fd81a 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 103a9f9b52 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 233b4b49d7 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards aa79b5d757 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 91aad27114 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 25a05e8d68 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 115a1b8a6e 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 8e5e1643fa 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 7ea9133797 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 8f2261da2a 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards d209af998f 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards ab877c022b 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards e20c954a19 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards c6664ef1c5 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 41dde10c31 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 7714171576 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 8c1ed1d4bc 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards f6c2c5cc45 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 7201792279 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 0f2e8dd4db 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 6a0bce8afa 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 047a23ab53 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 00a5ec79a8 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 95beb160a6 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards f7b735076f 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 57021ec01b 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 95d30bc6a6 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 325cdad067 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards f39ed8ada6 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards e5695ff7ac 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards a1638086c5 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards d9ed2aebba 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 8fc8e1398e 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards a69aec8010 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards ea8a299002 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards f475640d1f 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 2c45602d8d 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 423c0b46be 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 75acdbd5ae 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 30096ea62b 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 79274b3ef7 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards 662cae62fa 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards e6d4ea1f1a 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards b84562b564 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards 8cd2e1b7bc 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards b6a5b440b6 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards d16b69cca9 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 5a1f4fad4f 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards b58472b251 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards df4a9476a0 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards 4d0984eae5 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards 05925fdb09 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 13ef46ec04 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards caa9df437c 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards f45424e644 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards a982abfc82 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new dcc286c187 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new da1e107fbb 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 5f11590aa7 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 629893d80b 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new e6734e4ff1 218: onsuccess: #2030: 1: Success after gcc: 5 commits new e2634fc51e 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 2131b78a63 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 1d0228ff5b 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new c50f933f45 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new fe744b257d 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new c4baf28e6b 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new d336e71c6f 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new c30d549e91 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 100c542f79 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new 4f8c4f21e1 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 75ad5b342d 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 716ae2cc46 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new eb3638accd 231: onsuccess: #2047: 1: Success after gcc: 4 commits new f349a5d2f4 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 7b45fd473e 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 3a0fdd9f4f 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 7ba30331fd 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 381a105a96 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 49c29d1ba5 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new c1c91dd959 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new e7676b715f 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new ed7f75477b 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new a99cba6c15 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 0be190aabe 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 8be7e4abb0 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 11414fa4c7 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new a89a9b4eb1 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 72350aad11 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new a32eed31fb 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 2180a77926 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 7a4f682e87 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new d3b68b4350 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new a69f228772 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 3723202bd3 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 496d2af673 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new b836f9ae5c 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 35cd54e759 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new eb2b163348 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new d8807c4420 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 15d243b3a5 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 457e84e1e1 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 3d1ea20852 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 8ec856c0cf 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 5dbe5c9516 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new d3f4461b8d 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 76f833e84b 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 54618b5796 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 992e15511c 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new f58f6e2fb6 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new a2fa905859 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 2bbc90259e 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new ce4cdf7f12 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 251a992d9b 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 5a0c2dcd4b 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 4c7ed007c6 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new af952f8540 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 875fc19062 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 330a0c1dcf 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new d484f26a64 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 30d1d7ace9 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 65ba914a61 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 790bb9357c 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 6f85bae0d0 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 8b863f3d31 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 8a89af6cf7 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 2652285f5c 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 7a5367e762 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new d00898a51c 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 85f8a95b5b 287: onsuccess: #2103: 1: Success after gcc: 9 commits new c2f18d9312 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 76a967d6ac 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 949fb087b3 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 05623a8a6f 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 52723fa5c8 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new f284a28a3c 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 991a709ed5 294: onsuccess: #2110: 1: Success after gcc: 17 commits new d1810b93f9 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 4c30a407cc 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 8d73144036 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 9f4e0cdf79 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new fc1756ea35 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new c7bf2c0c7d 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new aaad974f10 301: onsuccess: #2118: 1: Success after linux: 16 commits new 7d60e9578a 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new edc5c3265f 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 8ce8ee4552 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 484b1b030a 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new a1ca0b2899 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new ba91394ee4 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 759e446713 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new bb08fdff06 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new e95dd53223 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 54e5a976d9 311: onsuccess: #2130: 1: Success after gcc: 4 commits new a86dc6fc69 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new a88857310d 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 75b89bff1a 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 656d4aefce 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...]

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 (492b4280ed) \ 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 1784 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31832 -> 32336 bytes 04-build_abe-stage1/console.log.xz | Bin 91592 -> 91864 bytes 06-build_abe-linux/console.log.xz | Bin 8876 -> 8880 bytes 07-build_abe-glibc/console.log.xz | Bin 236208 -> 236884 bytes 08-build_abe-stage2/console.log.xz | Bin 229216 -> 227840 bytes 09-build_abe-gdb/console.log.xz | Bin 39328 -> 39768 bytes 10-build_abe-qemu/console.log.xz | Bin 31484 -> 31180 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2648 -> 2572 bytes 13-check_regression/console.log.xz | Bin 5852 -> 5572 bytes 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 4 +- 14-update_baseline/console.log | 66 +- 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 2663928 -> 2687724 bytes sumfiles/g++.sum | 10 +- sumfiles/gcc.log.xz | Bin 2264084 -> 2234272 bytes sumfiles/gcc.sum | 2050 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 888800 -> 895880 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214176 -> 214052 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 433664 -> 437096 bytes sumfiles/libstdc++.sum | 2 +- 37 files changed, 1103 insertions(+), 1103 deletions(-)