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 011953ded5 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 0e3f328871 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards b6f4031d57 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards bf45ed385b 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 558fd87a24 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards b6a2162443 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 54acecdb99 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 0f8ddb0977 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards a157cdcbc4 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 4a94a24bdc 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards ee56f93120 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 2fc67913ff 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards d48db54271 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 63b827ff58 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 250d18e431 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards be448f4ff4 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 4bc2178e32 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards ffa80428c9 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 11ca92851e 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards eb9bd19ed0 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards c188e5ceba 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 3d34bad264 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards ac18b46267 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 1791844d80 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 7d85f175b8 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 68dc2b179c 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 9477f56586 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 5775bd6ca6 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards c5e55039cc 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 4099686627 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 9fc75bc66d 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 56ffd4ba76 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 6439a1b3a8 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 94bbbb3808 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards c63553776a 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 54bc304a00 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 01fd8c3c00 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 62392eed8e 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 34c4711b4d 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 99f20f6f3a 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 8f9bec66a1 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 7ee5050f5e 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards c56ab2f5b6 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards ca2e055450 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 89cb5662c6 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 7b02ac7e43 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 64b7bc03f8 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards b038b9b368 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards c560d4b576 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 6c0bf0cb49 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 41deeefbe8 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 64ca78d8a5 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 88688f06c7 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards b9e5c834bc 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards d0ccba987e 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 9ec2ed91ae 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 8dd1b61797 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards d237017520 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards af95ea87ee 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 9ff4d64e95 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards b89e76b25b 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards ea8ec6011b 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 5beb011ce2 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards c40821dd8f 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards aea5f069bf 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards ad697eb2f4 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 1ff72c7921 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards caae327590 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards d64227411f 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards e1b5effb30 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards f8b5a8ed7e 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards ae27a12b73 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards f7fa4078c4 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 934d652c38 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 4f53423d0a 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 726938f9a9 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 06e2deedb3 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 1ca624d973 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards d640c6f5e9 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 2e2dabb058 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 4f46ed8c0b 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards f3c051383d 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards d66a786cf8 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 3601705e27 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 53facf6534 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards eaf566e0d7 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 6c949e63f9 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards c201b82494 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 4e1a6d4141 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards cd213625c8 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards f0e93b7456 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards d312da1301 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards a9086843dd 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 7585b6d078 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards f5d308da82 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards c08dc87e75 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 8b56eaaca4 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 436eda5ab9 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 2215b76fb8 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 37fe71e67f 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 96cbf1d4d0 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new d9f817beb4 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 088d415ac0 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new cceaa0b6dc 231: onsuccess: #2047: 1: Success after gcc: 4 commits new e7646de6ad 232: onsuccess: #2048: 1: Success after glibc: 2 commits new b896d0d54a 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 0a2ab7ca53 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 875d4830f0 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 8707760c49 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 62e3aac06d 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 2002f45642 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 6eaecf47c9 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 3cee528728 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 663628c632 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 2221eeff99 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 24de462ef3 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 4b9371f2cf 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 034a6eee4b 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 993edb028c 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 86b7c1eb7b 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 6b80c73e39 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 6042261b83 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 3d654f013a 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 00f3445083 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 20533f61bb 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 93925a7492 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 65279cc36a 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 8f95568e6b 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 0b700a8fee 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new a98847b772 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new a84892e30d 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new b0c4ef1dcb 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 54e0df4f9e 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new c8d14b0b06 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new eb5854c1b2 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new eea19aff23 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new be9d755fa7 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 4c31b370db 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 4a772219be 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 8b7e512f08 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 4e0a8cf5c2 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new d63b7fa1b0 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 7110e5e18e 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 011fbe3d42 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 45bfe6e9d9 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 6d20d87016 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new ded1a92c29 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 09ea5b61cd 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new c7ef222da1 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new e0fa9aeb8d 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new ad15732959 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 882f9e7f9e 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new b58db66fe6 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new f8b6cfc8b6 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 9eb94b3e3c 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 0e671adff8 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new c671b47f9f 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new c8c13c828f 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new c0c964424a 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 0fb266bb28 287: onsuccess: #2103: 1: Success after gcc: 9 commits new db5a6fe0a7 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new f3710d2082 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new bcae2826f5 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 2a5fd14855 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new f112e1c1e3 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 7a7e6fadac 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 27e5463822 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 09966b60d3 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new b5910c5afa 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new aef5ae7961 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new da761c82ae 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new e8db473db9 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 5255509b40 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 5bcd1d36c7 301: onsuccess: #2118: 1: Success after linux: 16 commits new 5782970074 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 36ef57ebad 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new f8b80f610d 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 6aca9a452e 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 75efffd385 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new cabbaaf35f 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 072475a712 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new fe7b19a6ac 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 55dd4b47d2 310: onsuccess: #2129: 1: Success after binutils: 4 commits new fdf9f6706f 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 1c73f2f232 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 9fa59de056 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 90b25752f5 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new adae995ee9 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 6ab80acb08 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 7d130b9927 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 7cebd212f2 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 5429679aa1 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 6efd6c7abe 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 9bb46d6b75 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new e1307159c6 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new c3d5470468 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new c2ff99e71d 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 4d38e2c6f3 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 0f612ae57c 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new d4b1ec6bda 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 4305dd3696 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new f19a219703 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new eefb55bb74 330: onsuccess: #2150: 1: Success after linux/qemu: 36 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 (011953ded5) \ 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 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32144 -> 31772 bytes 04-build_abe-stage1/console.log.xz | Bin 92200 -> 92776 bytes 06-build_abe-linux/console.log.xz | Bin 8700 -> 8420 bytes 07-build_abe-glibc/console.log.xz | Bin 236868 -> 237328 bytes 08-build_abe-stage2/console.log.xz | Bin 228068 -> 228528 bytes 09-build_abe-gdb/console.log.xz | Bin 39536 -> 39604 bytes 10-build_abe-qemu/console.log.xz | Bin 30964 -> 31196 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2524 -> 2516 bytes 13-check_regression/console.log.xz | Bin 5828 -> 5808 bytes 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 34 +- 14-update_baseline/console.log | 50 +- dashboard/dashboard-generate.sh | 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 | 28 +- sumfiles/g++.log.xz | Bin 2692740 -> 2664336 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2242880 -> 2277292 bytes sumfiles/gcc.sum | 2464 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 895972 -> 899920 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213960 -> 213948 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2676 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 442452 -> 440792 bytes sumfiles/libstdc++.sum | 2 +- 36 files changed, 1321 insertions(+), 1321 deletions(-)