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 a9552352f1 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 393b0890d7 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 98ae7d4307 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 74ffc54ce0 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards addccfa993 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards fee1d4d3aa 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 2778dad7f5 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards c8353f1fdf 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 20b75f9efc 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 3ba12416d2 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 87994d6379 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 6d7c9702fe 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 30120c4101 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 7073f906d8 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 7322aec07e 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 763fbd0bb0 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 74e98be1ef 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards d3ed75032c 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 32714eeb8b 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 662d3f2365 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 4c1da77ff3 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 8db9a8ffba 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 59e21ac51a 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 970e944549 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 864c31cd02 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards c29cae786f 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 98a979ef72 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 239b6f3a38 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 6dfc78caf4 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards d8891f65b0 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 7a90aee219 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 82e4a17b46 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 558d5c2c20 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards e77e9e6f2f 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 5e6ac989a6 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 139e408e40 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 61062b9bac 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 7abacf219d 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 18f323c997 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards d1725be785 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards d16b3f8e9b 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 0fd92fe0f5 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards ff095c4117 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 909ca1c9b1 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 5545e466f5 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 72d52ed706 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 1861ab0553 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 2b2b8d0002 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 146084a584 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 377c9c221b 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 2f593773e2 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 92c407233b 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 861dd2a20b 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards a4a5cf5fae 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards f9cee80d47 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards aad4f293f3 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 0ce082d1fb 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 973c248a1f 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 6c41c2b41a 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards f87d966800 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards f6f0b40cfc 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards d5445ee412 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards f9fc404b14 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 222ceddbcc 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards c7d6e15cfe 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 8bcaf8f4cc 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 11f687e066 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 6f00583a29 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards a8e89a3007 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards b748a6f228 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 1ecab91260 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 1cbee4869e 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards de7905b755 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 944d4ce862 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 0adf08b840 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards cbc425d1e7 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 10f500f5ec 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 088aaac256 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards a18b0f12e0 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 07db004136 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 75758ef441 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards c6eb1f2cd9 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 82318a0d23 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 183c29b71f 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards f8688027fa 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards b837fdc5d7 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 113e1713b3 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 77e92921de 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 972c8a6360 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards d4dbdaac93 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards a23b8cf755 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards f913960630 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 0ee3929927 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 1c96942871 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 58bfd2fd89 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 37c0d1df6b 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards f9d8b44e15 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 3f49102510 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 2f9d507ce0 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 20de081720 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 7d0a4026ff 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 89c8a4bf3a 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new e0b2b65174 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new a267944624 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new f646824914 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 2a6c9dfaff 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 97c17db283 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 0d7a2fd7ec 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new f55e2fbfe0 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new eb5eb1ff7c 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 8a3895c88f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new a5b1e70b55 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 32c3a758cb 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 7c25e5a70c 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 9d4e9cd722 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 202b910a85 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new b9375d3ca1 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new d685195b9e 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 853252b25e 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 1a214778ba 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 71c418b74c 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new f1b60865ef 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 389d16c991 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 2ad6d1ba03 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 8b6e9429d2 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 80bc6b6cfd 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new ccb446fe21 259: onsuccess: #2075: 1: Success after glibc: 2 commits new bc12d028a1 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 4253ac0135 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new a0fc97bf5a 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 4974d40a31 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 68612c0774 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new b3e12a4e18 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new d7c6c8b27a 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new b2aa6ca667 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new baab32f936 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 7010dc88ca 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 7cb203519a 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 50429ba6b4 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 2d7d957c57 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 4f100bc9f6 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 9a5b5badf6 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 2e01c97d29 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new bd45e7d167 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new f6d56fcab3 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 1f55ae1446 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 4c25e3697d 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 1b4a4ec46c 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 84fa5401c1 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 48b7d621a7 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 7f81faf12e 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 1805214376 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new c15fba167b 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 197ee46f10 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 293c82ed2c 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 5c005fd03b 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 4d5cc4902e 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 09207e18a9 290: onsuccess: #2106: 1: Success after gcc: 2 commits new a6c94e563c 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new d12d59b158 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 9b6c79a83b 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new ad70d5f6cd 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 43e79fa656 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 73c8cc25dd 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new b48ba59a0e 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 8266e90d24 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 10fee3c5cb 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 25b0f3e9c1 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new c8875409af 301: onsuccess: #2118: 1: Success after linux: 16 commits new 26ff1d8d63 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new a0dd2b552b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 1dae772ba9 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 33880d1c00 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 5999acd65b 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 51be4a2409 307: onsuccess: #2124: 1: Success after gcc: 2 commits new ce864aaf21 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 44c5b9bcad 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new da2873c29d 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 91913d1e52 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 6bb28d23f3 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new d3c50991c6 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 6e5f08e41b 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new a514862b01 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new cec10db4a9 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 4cadf6fd24 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 09db7e8d5e 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 6f6ebab54e 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 548af2a8e6 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new d36aaa4e0c 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new c9780de633 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 60c576b8df 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new b61fe7d567 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 49bcc5e5dc 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new cf5cc45f64 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new cae854a3f7 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 6027ccd7f3 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new d9818ee6b2 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new f9878b8298 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 9338e15de5 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 80f979de21 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 83fd6f2f1e 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 2b4c468bbd 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new a249403a4a 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 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 (a9552352f1) \ 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 1812 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31740 -> 31804 bytes 04-build_abe-stage1/console.log.xz | Bin 91240 -> 91452 bytes 06-build_abe-linux/console.log.xz | Bin 8776 -> 8768 bytes 07-build_abe-glibc/console.log.xz | Bin 235836 -> 236120 bytes 08-build_abe-stage2/console.log.xz | Bin 228336 -> 227872 bytes 09-build_abe-gdb/console.log.xz | Bin 39268 -> 39364 bytes 10-build_abe-qemu/console.log.xz | Bin 31588 -> 31556 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3916 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2476 -> 2484 bytes 13-check_regression/console.log.xz | Bin 6168 -> 5200 bytes 13-check_regression/results.compare | 20 +- 13-check_regression/results.compare2 | 56 +- 14-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- sumfiles/g++.log.xz | Bin 2688412 -> 2668456 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2246984 -> 2268824 bytes sumfiles/gcc.sum | 2358 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 902152 -> 894336 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214060 -> 214204 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439220 -> 444864 bytes sumfiles/libstdc++.sum | 2 +- 36 files changed, 1267 insertions(+), 1309 deletions(-)