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 a249403a4a 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 2b4c468bbd 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 83fd6f2f1e 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 80f979de21 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 9338e15de5 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards f9878b8298 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards d9818ee6b2 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 6027ccd7f3 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards cae854a3f7 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards cf5cc45f64 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 49bcc5e5dc 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards b61fe7d567 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 60c576b8df 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards c9780de633 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards d36aaa4e0c 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 548af2a8e6 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 6f6ebab54e 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 09db7e8d5e 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 4cadf6fd24 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards cec10db4a9 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards a514862b01 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 6e5f08e41b 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards d3c50991c6 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 6bb28d23f3 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 91913d1e52 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards da2873c29d 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 44c5b9bcad 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards ce864aaf21 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 51be4a2409 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 5999acd65b 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 33880d1c00 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 1dae772ba9 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards a0dd2b552b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 26ff1d8d63 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards c8875409af 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 25b0f3e9c1 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 10fee3c5cb 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 8266e90d24 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards b48ba59a0e 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 73c8cc25dd 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 43e79fa656 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards ad70d5f6cd 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 9b6c79a83b 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards d12d59b158 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards a6c94e563c 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 09207e18a9 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 4d5cc4902e 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 5c005fd03b 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 293c82ed2c 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 197ee46f10 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards c15fba167b 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 1805214376 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 7f81faf12e 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 48b7d621a7 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 84fa5401c1 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 1b4a4ec46c 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 4c25e3697d 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 1f55ae1446 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards f6d56fcab3 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards bd45e7d167 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 2e01c97d29 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 9a5b5badf6 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 4f100bc9f6 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 2d7d957c57 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 50429ba6b4 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 7cb203519a 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 7010dc88ca 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards baab32f936 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards b2aa6ca667 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards d7c6c8b27a 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards b3e12a4e18 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 68612c0774 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 4974d40a31 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards a0fc97bf5a 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 4253ac0135 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards bc12d028a1 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards ccb446fe21 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 80bc6b6cfd 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 8b6e9429d2 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 2ad6d1ba03 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 389d16c991 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards f1b60865ef 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 71c418b74c 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 1a214778ba 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 853252b25e 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards d685195b9e 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards b9375d3ca1 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 202b910a85 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 9d4e9cd722 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 7c25e5a70c 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 32c3a758cb 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards a5b1e70b55 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 8a3895c88f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards eb5eb1ff7c 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards f55e2fbfe0 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 0d7a2fd7ec 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 97c17db283 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 2a6c9dfaff 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards f646824914 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards a267944624 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards e0b2b65174 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 977bebcebb 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 23793002ee 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new a71e7ecb2e 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new abd685a435 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 881459eace 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 84863c0ca2 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 453748c11c 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new b0372c8893 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new eec4882010 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new dcacea044c 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 8f1db6120b 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new a1e92deae3 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new d93f3e93e6 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new cfa292190b 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 4f09fec9e9 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 177e30f788 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new a0e9141722 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 73a6e0e2f9 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 72fb18f872 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 85b8b33497 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new bdbe6bd119 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 77cbb60cfb 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new d09e12fe12 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 6a0d4f0b8f 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 3e04b4886f 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 4d3e7ca6ab 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 74800c6304 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new c6ee954d07 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 0774e468c1 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new de596fa09d 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 49d8f549e4 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new a3eb0375ca 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 9843a25626 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new fe9b3d8920 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 379f311e8b 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new c466d6b5de 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new cf20b01f53 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new aeb44f8c0b 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 61a5c60339 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 5d8962cc6d 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new f1c80ac746 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new f366a18668 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new b355fa1d39 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 139bdeddae 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new f16fc3a7af 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new bcdc712f67 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new a7f6cb800e 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 90a8de08cf 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 27e02f3659 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 541912f36c 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new bf58b78d10 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 9d5d56ccc7 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 5b3f930434 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 778009044b 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 23dd1bfc24 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 1c029b60bf 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 2e96daeefc 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 6340e5b359 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 4f5da5d4e7 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new ba7761119c 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 57e1e4fe9d 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 85600fee9e 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 8b198673a7 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 1f5304bb82 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new dbd26104af 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 9cf5943abb 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 903cc3ded2 301: onsuccess: #2118: 1: Success after linux: 16 commits new 43fcde4877 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 08eff115e7 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 7e967ea171 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 293f77eca9 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 7ddaaba8db 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 881dee4049 307: onsuccess: #2124: 1: Success after gcc: 2 commits new d8e8dc4ad6 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 85d2ce6cde 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 15858c7411 310: onsuccess: #2129: 1: Success after binutils: 4 commits new be35bd6b0e 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 7700c58c46 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new b2eede7b4e 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 0774ffe7a9 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 1791e53f4e 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 1e8154bc13 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 3353050a65 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 6f301045de 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 95a93b6acf 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new b6cd850423 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 2e0592fd8b 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 7bb6e334db 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 00b602ffbc 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 0d2ce2868f 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 621f9eddaa 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 006a32574c 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 34b646d3e3 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 62b49de642 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 89209e7f07 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 5436fa58e5 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 58a5b2b2da 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 4fb2ac06d5 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 73dd4a3d4b 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 23f59eba11 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new c1c56b9012 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 9266bb9237 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...]
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 (a249403a4a) \ 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 1772 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 31804 -> 32196 bytes 04-build_abe-stage1/console.log.xz | Bin 91452 -> 92460 bytes 06-build_abe-linux/console.log.xz | Bin 8768 -> 8628 bytes 07-build_abe-glibc/console.log.xz | Bin 236120 -> 238432 bytes 08-build_abe-stage2/console.log.xz | Bin 227872 -> 231468 bytes 09-build_abe-gdb/console.log.xz | Bin 39364 -> 39764 bytes 10-build_abe-qemu/console.log.xz | Bin 31556 -> 31708 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3916 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2484 -> 2744 bytes 13-check_regression/console.log.xz | Bin 5200 -> 6376 bytes 13-check_regression/results.compare | 12 +- 13-check_regression/results.compare2 | 32 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- sumfiles/g++.log.xz | Bin 2668456 -> 2665288 bytes sumfiles/g++.sum | 12 +- sumfiles/gcc.log.xz | Bin 2268824 -> 2267784 bytes sumfiles/gcc.sum | 2406 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 894336 -> 895804 bytes sumfiles/gfortran.sum | 12 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214204 -> 214024 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 444864 -> 439012 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 1311 insertions(+), 1293 deletions(-)