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 8ba539d4b2 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 9c34b5b2c1 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 7f39351fb0 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards b748bb341f 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards adb16ec6d6 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 3020d721d3 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 1d75d569d0 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 8330ba8ece 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 1e5f984d5a 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 63fff1b4c0 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards bc5581f0f1 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards f96b42ef60 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 55c512d898 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 27619d82d3 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 236f91ccf4 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards bea1ef91ca 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards a7eb69d248 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 9bafc1e1d1 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 7ff8120beb 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards f9c945adb2 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards a09dba96d3 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 2d291ec89b 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 71a6403d99 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards ef58b6c61a 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards b941825ad4 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 3019dec539 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 98ff8c2096 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 671ddf9872 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 26e14a93aa 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 0a323ffdda 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards ba94aa65db 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 1822ed62c9 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 008ddf0e3d 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 2abc13e1ec 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards aad021d5d0 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 81acb4a762 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards adb0155ef9 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 061acf42fe 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 9c34004c6b 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards d29e4d1190 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards b223492671 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 31d7f47e03 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards f519d85c61 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards ea2d89bdf6 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 237c95d32c 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 31927b9645 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 64cb57ca3a 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 1ea24dff63 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards ad7317ea7a 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 8b451e4e54 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 5ba550b86e 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards d4f006ae41 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 2dc2eb7e5f 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards ae9ae1f19b 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 832b1bfc4c 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards eb05679fef 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 6c0708f012 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 17f6dc485a 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards ca0f989ca3 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 812b05c84d 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 24b2dc4cd3 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards a8f51a5b4f 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards f6ae13e925 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 6e29d9add5 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 740eb5fb8d 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 0866425963 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards e968c68876 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 577a5e77c6 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards de951e01de 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 31f6fa6c8e 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards ccada5228e 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards b743226b1a 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 33d00c4cb8 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards b102658e16 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 6e6b2dbbb7 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 5b40f6bd13 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards d90650567d 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 7c8078cb6c 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards b8a2f6e491 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards ed50b08654 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 0044e23fa3 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards e86d482b5b 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards dc3eef1d53 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 000f5398d9 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards b06b5dbc1e 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards 93a3de532a 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 6fa3405029 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 4bb876ef4a 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards 65b3c03012 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 077793b9ae 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards 699754a597 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 2f04662168 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards a5ae1861ce 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 3d4113a7de 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards 94b495a59f 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards 7bf051aeb4 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 115ddaf00a 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards fec85e69f4 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 3854befe1a 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 7f69b1852f 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards daa9ce28eb 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 2c3aa17e25 213: onsuccess: #2024: 1: Success after binutils: 3 commits new a982abfc82 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new f45424e644 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new caa9df437c 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 13ef46ec04 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 05925fdb09 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 4d0984eae5 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new df4a9476a0 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new b58472b251 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 5a1f4fad4f 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new d16b69cca9 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new b6a5b440b6 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 8cd2e1b7bc 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new b84562b564 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new e6d4ea1f1a 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new 662cae62fa 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 79274b3ef7 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 30096ea62b 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 75acdbd5ae 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 423c0b46be 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 2c45602d8d 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new f475640d1f 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new ea8a299002 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new a69aec8010 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 8fc8e1398e 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new d9ed2aebba 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new a1638086c5 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new e5695ff7ac 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new f39ed8ada6 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 325cdad067 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 95d30bc6a6 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 57021ec01b 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new f7b735076f 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 95beb160a6 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 00a5ec79a8 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 047a23ab53 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 6a0bce8afa 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 0f2e8dd4db 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 7201792279 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new f6c2c5cc45 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 8c1ed1d4bc 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 7714171576 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 41dde10c31 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new c6664ef1c5 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new e20c954a19 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new ab877c022b 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new d209af998f 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 8f2261da2a 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 7ea9133797 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 8e5e1643fa 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 115a1b8a6e 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 25a05e8d68 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 91aad27114 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new aa79b5d757 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 233b4b49d7 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 103a9f9b52 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new f9f84fd81a 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new f5ecc80df6 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 71546096fb 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new f1f367c753 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 9e80f1160b 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 8c60324f4a 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new aa95f56ddb 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 28b58b063e 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 6e86715ba8 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new e2d1eaf296 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new b54d500014 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new ed05aefda1 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new cd8bafdd23 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 28e7ab3181 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 318fd144bf 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 8ef73596d1 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new acaf908e00 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 7d69cb40cd 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 2de9cb4518 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 567d1bab9b 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new fa860d2647 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 260759a908 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 8f35990bc5 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new a0f0cb4826 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 87a8a7ece2 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 1fd0f6e2c4 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 261cee29e9 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new f934cdd84e 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new da016e4e86 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 7d04ebbd6b 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new a4d5965f56 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new f4beea77ee 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 5142cd04fb 301: onsuccess: #2118: 1: Success after linux: 16 commits new 86f7dc2572 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new eb0edb197b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new a128889cb8 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 554c7da41c 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 30672d26b2 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 163bca96eb 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 4f1f848de9 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 6492212010 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new a742e2d190 310: onsuccess: #2129: 1: Success after binutils: 4 commits new de975d8efb 311: onsuccess: #2130: 1: Success after gcc: 4 commits new b846a27db5 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new afcaf18c9d 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 492b4280ed 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...]
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 (8ba539d4b2) \ 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 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31696 -> 31832 bytes 04-build_abe-stage1/console.log.xz | Bin 92168 -> 91592 bytes 06-build_abe-linux/console.log.xz | Bin 8872 -> 8876 bytes 07-build_abe-glibc/console.log.xz | Bin 236444 -> 236208 bytes 08-build_abe-stage2/console.log.xz | Bin 229180 -> 229216 bytes 09-build_abe-gdb/console.log.xz | Bin 39204 -> 39328 bytes 10-build_abe-qemu/console.log.xz | Bin 31608 -> 31484 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3316 -> 2648 bytes 13-check_regression/console.log.xz | Bin 6956 -> 5852 bytes 13-check_regression/results.compare | 14 - 13-check_regression/results.compare2 | 28 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 2689720 -> 2663928 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2238212 -> 2264084 bytes sumfiles/gcc.sum | 2012 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 897376 -> 888800 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214132 -> 214176 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434868 -> 433664 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 1087 insertions(+), 1117 deletions(-)