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 9100aaa008 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards d4cc92a24b 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards b302d6829f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards c3cef7d8a4 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 0d9e7e85fc 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 14b625a324 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 1253805c29 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 0ce7f0e41c 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 45aae30f98 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards a7282ca1c0 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards c1da56b55f 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 4a00834482 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards fc3c953a7c 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 2cfafdbe3c 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 9530ee574e 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards b4a6c492b4 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards e6b008b895 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 3677b304a8 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 8beb631c0b 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 2d3ccc5fd2 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 91e4709155 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 030b68fa33 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards be875fd551 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 9128c28d52 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards fe3a3ac73a 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 1dfffd2608 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 317d1192da 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 7e7c5e9db2 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 070240d720 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 53eddcecec 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 9b35e53d2f 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 18503d0253 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 5fb33db80a 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 6ad3d6a748 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards c0da2636f6 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 1b779e6f35 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 78dec07495 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 5e55d3cfcb 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 3d2db25622 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 0cf1d99cdf 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 437d52685c 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards e9ea8cca42 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 3f10e287d2 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards b970bdac14 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 3a002ccaab 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 329fd4391b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 9359e5a099 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 998e115cfb 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards af78b771c5 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 74e434acdd 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 6e44a1a7f8 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 5a92c26c4a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 18e9f7f6fb 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 6958fef786 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 2890ae8c46 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards c1f869b13b 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards d6e5796ec5 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 03eddddf7c 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards b94639cef5 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards c3a8e1b95b 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 5c69583a44 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 6fecfb9e90 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards c9f3caf337 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards e8f56ba207 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 582f7cd61a 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 6467c4920a 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 4a3dcb5bef 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards ab718d3dbc 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 945eeddaaf 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards bb34d36ed2 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards c5d21e4488 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 2b6979a5a6 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 374aed70f5 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 29c30ce701 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards b40bdd77e5 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards bc9b44ee3c 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 8815ed32a3 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 8979972978 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 206c24c098 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 63ac8c24d7 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 96832c9d72 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards f987513783 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 6e57aae863 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards f974fbbf59 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards cec5e570f0 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards f39777f4be 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards f4121eb8bc 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 828009a026 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 8882cb3f24 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 7a69a82639 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards a12a704894 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 3af3765975 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 314ce1155d 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards b7270ccd99 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards b9645ea1c0 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards f487357957 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 07866d81bf 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards cc0110c7a9 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 721085db23 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 862df96257 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 4a395b4857 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 3e127526e6 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 315d85dbbe 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new a26037e2b7 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 3ae8c3b5a7 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 806d9cbc28 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 22c7c12d29 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 1a0ea0e73f 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new debd05ea18 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new e3506dff60 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 8f1fcb40a0 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 07d6530378 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 820716b2bb 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 95e96a9691 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new da61cb65d5 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 0ed48fe69b 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 7221a67df8 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 6f03f45a7f 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new d0a7222a5b 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new fdb9432e6b 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new a604acf403 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 82cba8e35a 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 5da0c52bef 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 67a6458b71 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 0932afa440 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new a0680f041c 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 263746b716 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 5203b19c92 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new b388bee479 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 66616696cd 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 005ac44862 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 31b0513b1c 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 0e1ffd4366 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 16f1a6524a 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new cc148f7b0a 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 67fa0e6602 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new c2b0f8f5e8 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new e3b8bd6add 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new cae69f9054 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 742df23e52 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 9c9be62036 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new e6722cda96 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 9ca5290bf7 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 6387470029 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 37cb920791 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 4e9cbd4d71 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 56c7be7d66 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 5732d2e906 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 2d644268b5 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new d576532be2 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 385b015ac8 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new f8f2e7b407 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new c236c368f7 301: onsuccess: #2118: 1: Success after linux: 16 commits new 4cbf65a782 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 0a06bed8b1 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 089992126f 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 24b58ee717 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 2d67449214 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 15996cfeba 307: onsuccess: #2124: 1: Success after gcc: 2 commits new fdfa42ac91 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 7821f64f0b 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 2e3489df85 310: onsuccess: #2129: 1: Success after binutils: 4 commits new d824c8bb52 311: onsuccess: #2130: 1: Success after gcc: 4 commits new d14a93528b 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 58c53f24a6 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 1272dbda12 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 233a22bf5d 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new daeb5c0b3b 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 570921c09b 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 40917e0318 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new d6867d365a 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 6f0f166f46 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 7ac3370bda 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 938a565bdf 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 894d2fb8ca 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new c6989e0f6c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 0e3d441b70 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new e446d8aed0 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 6dd9c49d5b 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new da5fbeddbf 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 11cd0e6b45 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 8ea654fb4b 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new ad4b37b9dd 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 1a6e9cb55f 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 5a11e8fee1 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new fed540622f 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 09c657a7bb 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new d1f4c63635 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new bb76af3378 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 6600f99d4e 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new ad36b9b5bc 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 751e379956 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new baa924a4f5 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 67ad9883d9 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 49178cba03 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 61b3b6dfd2 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 45e56e4b84 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 7bdc209988 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new e7231f543c 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 70985dfe72 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new b80b3a6130 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 00e65f419c 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new a6656870fc 351: onsuccess: #2171: 1: Success after gcc/linux: 15 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 (9100aaa008) \ 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 1804 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31388 -> 31544 bytes 04-build_abe-stage1/console.log.xz | Bin 92132 -> 91604 bytes 06-build_abe-linux/console.log.xz | Bin 8760 -> 8660 bytes 07-build_abe-glibc/console.log.xz | Bin 236664 -> 236720 bytes 08-build_abe-stage2/console.log.xz | Bin 229304 -> 229124 bytes 09-build_abe-gdb/console.log.xz | Bin 38904 -> 39044 bytes 10-build_abe-qemu/console.log.xz | Bin 31972 -> 32004 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2940 -> 2620 bytes 13-check_regression/console.log.xz | Bin 7316 -> 5992 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 28 +- 13-check_regression/results.compare2 | 167 +-- 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- sumfiles/g++.log.xz | Bin 2700616 -> 2670956 bytes sumfiles/g++.sum | 35 +- sumfiles/gcc.log.xz | Bin 2245964 -> 2242860 bytes sumfiles/gcc.sum | 2170 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 900300 -> 891476 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214088 -> 213996 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 444264 -> 434860 bytes sumfiles/libstdc++.sum | 8 +- 37 files changed, 1215 insertions(+), 1355 deletions(-)