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 8814c231be 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards c6870c9a7a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 18cdca8537 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 7e1dcee376 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 13f9370e7c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 2f3bccb9d3 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 61b1367c96 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 6052990780 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 5ce507b6dd 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards cfd2c49ec7 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards bf59315026 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 0877834bc7 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards c975db6f7b 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 324c1483c9 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards d5f098d983 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 4995faaa82 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards b81883f0f8 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 07b4f79657 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 6554c83ff7 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8d54374ec8 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 6a6acdf150 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards bd06e55048 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards e3406b279b 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 5af9de8091 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 01f1e772ea 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 58d1326417 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards c33337cbcb 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards a0ad344cae 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 948e22ece1 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 100a6b30a8 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards f15708bf6f 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 03fd1c1649 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards ce10c6d2d0 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards d4ef755e61 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards b3a983375f 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards fc6751a62e 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 2304408033 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 6e1406bade 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 7d6709ac80 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 264b6070c8 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 7209e15d85 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 0ed9e52e6b 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards ce208149e5 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 66ebee1e9d 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 99224ce984 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 087da8064f 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards a751ebbfb6 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 32d8b1c36e 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 11f2a7d560 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards a23b7f9db2 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards a01e99dbf0 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 22a4034027 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards ad78cff61c 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards d4028c7c39 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards ec2039f851 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 54999114c8 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 76b7ec9f94 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards a5e7312561 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards f417a2bb37 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 071eede2b0 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards b6a6e4f90c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 75239af78d 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 0ea48c59f4 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 771d2cdc17 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 53cc5b7046 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards f279d32f14 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards cfcc3dc229 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 4979046725 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 280b1636be 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards cd1492e873 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards eaf7aa629e 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards d280e86226 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 265a22f6e7 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 9804567c88 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 99a647a865 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards e22d3e6cdf 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards cb8857245a 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 3ab0a4a5a3 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 5890bf8cc7 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 970eb63c12 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 8b930ad75d 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 70e3aeee58 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards dafb365c7b 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards d4232b0c93 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 84d456b246 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 04b00c5752 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 2eaab2bae4 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 57d68e49ff 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards b74e17af35 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 46da6b42ec 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 0235ee01f0 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 8a90e9864f 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards d903fa451d 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 394b9defc4 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards a2db70e6e6 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 1f04812c80 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 434610c259 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 6d9eb76708 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 27a049f1f3 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 6076050cbe 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 4d42e7f695 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 3820fcbf4b 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 6203907340 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new f6c5832dcf 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 582e5a102e 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new c26e7934a3 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new eebbbefc05 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 3b49915972 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new e63c73d9e6 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 391b71a89e 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 3543b8fbfd 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 479a5ccdb0 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 01d3f88f55 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 05f9e3af16 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new d5c269859e 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 13b3a91ff9 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new cb63b29f79 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 6e65d5e15c 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 25917ff1e7 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 2f8ed2691b 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new f3598d5eea 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 11a521144c 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new cd20565550 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new b873d37ed8 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 47e67d19bd 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 5a139db57c 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new bb9496739b 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 6834f86eef 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 1410411783 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 9feffa509c 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 23c8ebf66b 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 8e4d648cc6 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 182a92c2f3 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 68953a3cd0 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 7bba4fef91 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new fbc295bd1e 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 3a1d8c9619 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 0f05e0c962 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new f51956f217 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 1d655ad839 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 000e74fa19 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new b8741c7140 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 7891277db1 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new a7ee4e035a 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new d96a70a05f 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 995a26ba23 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 2750036f9a 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 1903ff6ec7 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new b93d82d7b6 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 4f6f47c31a 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new b17e865bda 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 2ada35ef5a 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 2ee3a7a32b 294: onsuccess: #2110: 1: Success after gcc: 17 commits new c63845edd7 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 91586a6d1b 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new f40e3a08e8 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 5fe09ed4bf 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new ea4970f00f 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 62514e7a2b 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new d5092ae76a 301: onsuccess: #2118: 1: Success after linux: 16 commits new 8af80c6483 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new e98d5de71f 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new acb259daf4 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new bb5056e86b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 706bd6e528 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new dd409bfa47 307: onsuccess: #2124: 1: Success after gcc: 2 commits new cade1e53a8 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 3971ce6f6c 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 331bbbf28e 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 631e398778 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 5f273cfc05 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 90d5d3b4f9 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 5345756547 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 3f62da0584 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 8b88640f42 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 4362733bfe 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 7a79eb7342 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new f408c3d8b9 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 1ccae392ee 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new dc9a37bc30 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new b91d6ff321 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 8328e94084 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 17f9482136 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 2b3612a2e5 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new d39ab7e888 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new fc46d42bb2 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new dc32c5e4ed 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 509598bc9a 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 4c2484b532 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 59649dc5bf 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 7565d110bb 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 5db98d7f82 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 49cbd7eff7 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new ea46232a81 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 63ef871612 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 37ea842f74 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 2283646b17 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 7286244547 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 365210a19d 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new eb05a81241 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 9dd844b8c1 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 63eb5dba01 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 02c0e25477 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 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 (8814c231be) \ 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 1800 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31956 -> 32128 bytes 04-build_abe-stage1/console.log.xz | Bin 91504 -> 91796 bytes 06-build_abe-linux/console.log.xz | Bin 9296 -> 8736 bytes 07-build_abe-glibc/console.log.xz | Bin 236396 -> 236384 bytes 08-build_abe-stage2/console.log.xz | Bin 228052 -> 228092 bytes 09-build_abe-gdb/console.log.xz | Bin 39268 -> 39572 bytes 10-build_abe-qemu/console.log.xz | Bin 31476 -> 31228 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2624 -> 2612 bytes 13-check_regression/console.log.xz | Bin 5212 -> 5964 bytes 13-check_regression/results.compare | 20 +- 13-check_regression/results.compare2 | 18 +- 14-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.xz | Bin 2692244 -> 2691504 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2252124 -> 2253956 bytes sumfiles/gcc.sum | 2260 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 899100 -> 891828 bytes sumfiles/gfortran.sum | 7 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214192 -> 214024 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437496 -> 433640 bytes sumfiles/libstdc++.sum | 2 +- 37 files changed, 1228 insertions(+), 1215 deletions(-)