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 7bc763ee21 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards bdcddcca28 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 3ddfc806b3 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards d21483c01c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards c242bc8336 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards a68aab3d3f 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards a633e0c1fb 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards df6b79428e 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards c55887bd70 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 22adbce366 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 14f5bc69ee 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards d89e2980a6 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards f6a62c895f 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 3271690b8b 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 9a0719b996 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 601d1c1943 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 350082c777 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 67bcadc2c4 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 9c893c28b8 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 2c30e3dc63 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards d2d45aefdd 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 7e4bd53340 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards cd1b460e84 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 026ab31667 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 37b0ac18aa 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards d4770e882d 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 6ec5f0f8cc 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards b318dda81d 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards d4cdf146d0 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 1962211de5 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 4306eb3976 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 95e5091d66 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 1036498a9f 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards a39f50a361 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 32749529fb 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 9ba2c9f3b5 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards c454ab3588 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 9cc3adce5a 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 7f1214cff2 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 8e95001a83 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards a2780b4fc3 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards ff02c4a303 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 234fa3c882 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 0211b7d030 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards ac4691a4ee 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 770c1f5efc 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 30f5c244ed 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 7f697d67aa 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 24a2ff792c 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 5193f1a616 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards e66f63ee73 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 33a664c6ad 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 6d8a98bc4e 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 6d22bcb86f 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 0b0b470d36 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 5ac0b60a9f 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 2189ec8002 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 2f03a3296f 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 474269801a 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 786e51ef9c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 519c6822f3 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 5fa206c888 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 02848c1dc5 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 2eb7c56023 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards c13390586a 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 6441c48d73 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 8da040aa78 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 6723929448 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards d5f95a3985 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 158ea4a86d 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 555e52b030 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards dbe32509b5 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards a47d3ff5c5 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 6b9b1890ea 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 57f78eb158 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 58c5f9a607 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 59813fe789 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 7c86a854f8 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 1f434da895 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards b6ed2a187b 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards ed73d9c698 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 0ed8eaf04e 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 21ec6a9c7f 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 6afdcc296d 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 1431c8a4fd 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 566cd6ddab 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards e6402fb90f 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 62b1d64034 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards ccb70fc398 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 7f3b3b4020 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 52177740d8 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards a8fc523fc7 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards e830270b72 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards bd2c0abf9e 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 95ac7c0483 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 96d84601f8 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards f9982b9c4d 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 01080bb874 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 3f707f7385 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 6f07448658 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards cefa8ddd1f 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 2291bacdce 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 4d42e7f695 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 6076050cbe 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 27a049f1f3 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 6d9eb76708 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 434610c259 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 1f04812c80 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new a2db70e6e6 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 394b9defc4 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new d903fa451d 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 8a90e9864f 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 0235ee01f0 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 46da6b42ec 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new b74e17af35 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 57d68e49ff 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 2eaab2bae4 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 04b00c5752 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 84d456b246 259: onsuccess: #2075: 1: Success after glibc: 2 commits new d4232b0c93 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new dafb365c7b 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 70e3aeee58 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 8b930ad75d 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 970eb63c12 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 5890bf8cc7 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 3ab0a4a5a3 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new cb8857245a 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new e22d3e6cdf 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 99a647a865 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 9804567c88 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 265a22f6e7 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new d280e86226 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new eaf7aa629e 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new cd1492e873 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 280b1636be 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 4979046725 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new cfcc3dc229 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new f279d32f14 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 53cc5b7046 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 771d2cdc17 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 0ea48c59f4 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 75239af78d 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new b6a6e4f90c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 071eede2b0 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new f417a2bb37 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new a5e7312561 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 76b7ec9f94 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 54999114c8 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new ec2039f851 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new d4028c7c39 290: onsuccess: #2106: 1: Success after gcc: 2 commits new ad78cff61c 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 22a4034027 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new a01e99dbf0 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new a23b7f9db2 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 11f2a7d560 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 32d8b1c36e 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new a751ebbfb6 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 087da8064f 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 99224ce984 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 66ebee1e9d 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new ce208149e5 301: onsuccess: #2118: 1: Success after linux: 16 commits new 0ed9e52e6b 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 7209e15d85 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 264b6070c8 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 7d6709ac80 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 6e1406bade 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 2304408033 307: onsuccess: #2124: 1: Success after gcc: 2 commits new fc6751a62e 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new b3a983375f 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new d4ef755e61 310: onsuccess: #2129: 1: Success after binutils: 4 commits new ce10c6d2d0 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 03fd1c1649 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new f15708bf6f 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 100a6b30a8 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 948e22ece1 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new a0ad344cae 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new c33337cbcb 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 58d1326417 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 01f1e772ea 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 5af9de8091 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new e3406b279b 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new bd06e55048 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 6a6acdf150 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 8d54374ec8 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 6554c83ff7 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 07b4f79657 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new b81883f0f8 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 4995faaa82 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new d5f098d983 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 324c1483c9 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new c975db6f7b 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 0877834bc7 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new bf59315026 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new cfd2c49ec7 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 5ce507b6dd 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 6052990780 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 61b1367c96 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 2f3bccb9d3 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 13f9370e7c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 7e1dcee376 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 18cdca8537 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new c6870c9a7a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 8814c231be 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 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 (7bc763ee21) \ 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 1752 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31636 -> 31956 bytes 04-build_abe-stage1/console.log.xz | Bin 91496 -> 91504 bytes 06-build_abe-linux/console.log.xz | Bin 9284 -> 9296 bytes 07-build_abe-glibc/console.log.xz | Bin 236100 -> 236396 bytes 08-build_abe-stage2/console.log.xz | Bin 227956 -> 228052 bytes 09-build_abe-gdb/console.log.xz | Bin 39388 -> 39268 bytes 10-build_abe-qemu/console.log.xz | Bin 31124 -> 31476 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2484 -> 2624 bytes 13-check_regression/console.log.xz | Bin 6952 -> 5212 bytes 13-check_regression/results.compare2 | 82 +- 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 2687528 -> 2692244 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 2249912 -> 2252124 bytes sumfiles/gcc.sum | 2572 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 896548 -> 899100 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214056 -> 214192 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438696 -> 437496 bytes sumfiles/libstdc++.sum | 2 +- 36 files changed, 1364 insertions(+), 1432 deletions(-)