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 c7a5664e6c 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 4c9ac0a5c2 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 0a7f978bcd 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 419bef5c30 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 194f7602bb 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 7177e6cbe8 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 9b1974e742 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards bb60065698 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 072d0c6920 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 0759d7f0db 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards a2978b6248 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 80a7ef7576 301: onsuccess: #2118: 1: Success after linux: 16 commits discards e0af129974 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 113b7eddcd 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 9aad3f59d9 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 81764af875 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 4e159a1b27 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards bd614638cc 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards b90e035795 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards ccc978d911 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards badef1c1a7 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 007b983415 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards d49edae7de 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 93c073bf53 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards ffa1105aa4 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 59699414fe 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 95d4b185d6 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards e2f40ddd12 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 1590d00369 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards a8ba6caf64 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 93a1541034 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards d2c8cd0b4e 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards f26bc9b44e 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 7b5852b783 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 94f76d8141 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 87b1619176 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 888a20a79d 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards eace91b276 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 4113b74dce 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 686ae03eb3 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 970140567e 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 775c25a740 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards c00fe5f976 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 63b76be3ac 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards fb16448a86 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 70a11f70a6 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards c9ceb63062 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 4fac948265 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 20447b3d94 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 3d3fbd58b8 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 777fad4579 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 038772e497 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 48189882b8 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 65145a9501 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards b8913d8a63 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 5f5d5af499 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 34ac5eee81 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 8179eb2239 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 202b06a355 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards c1978e4d70 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 95034251da 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards f40698d352 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards e1e3e4afa3 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 0ff40956ee 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 1a21f1f620 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards eeb578e54d 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards fa08c185d3 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 1d88c096d3 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 69458b6878 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 83d1a6bda7 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 0ede6f89c3 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards ed257a038e 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 67d9b38ee7 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 17976fde76 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 8a3892687a 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 8a6dc55c8a 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 8916d8d6e5 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 9a2d616689 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards f2860e0c14 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 4e341cf2a0 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards cfb03db4d5 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 1d159a2dce 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards f2a1f7c7e9 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards cd9cc8de45 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards 4ad0b946cf 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 285734f114 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 186bee5e47 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards 56bc3db748 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards ab98cb61fd 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards ecdcf20c4e 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 29f814c5a5 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 8fe79ab67f 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 39dd552305 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards f4cb582227 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards 571c219d90 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards a3e2649f8b 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 0835092709 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards ed2e7226d0 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 21a3e097a2 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards f3d0866f0f 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards b81a6ff328 212: onsuccess: #2022: 1: Success after linux: 3 commits new 9150d7ab67 212: onsuccess: #2022: 1: Success after linux: 3 commits new daa9ce28eb 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 7f69b1852f 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 3854befe1a 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new fec85e69f4 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 115ddaf00a 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 7bf051aeb4 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 94b495a59f 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 3d4113a7de 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new a5ae1861ce 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 2f04662168 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 699754a597 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 077793b9ae 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 65b3c03012 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 4bb876ef4a 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 6fa3405029 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new 93a3de532a 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new b06b5dbc1e 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 000f5398d9 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new dc3eef1d53 231: onsuccess: #2047: 1: Success after gcc: 4 commits new e86d482b5b 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 0044e23fa3 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new ed50b08654 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new b8a2f6e491 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 7c8078cb6c 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new d90650567d 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 5b40f6bd13 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 6e6b2dbbb7 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new b102658e16 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 33d00c4cb8 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new b743226b1a 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new ccada5228e 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 31f6fa6c8e 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new de951e01de 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 577a5e77c6 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new e968c68876 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 0866425963 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 740eb5fb8d 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 6e29d9add5 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new f6ae13e925 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new a8f51a5b4f 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 24b2dc4cd3 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 812b05c84d 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new ca0f989ca3 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 17f6dc485a 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 6c0708f012 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new eb05679fef 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 832b1bfc4c 259: onsuccess: #2075: 1: Success after glibc: 2 commits new ae9ae1f19b 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 2dc2eb7e5f 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new d4f006ae41 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 5ba550b86e 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 8b451e4e54 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new ad7317ea7a 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 1ea24dff63 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 64cb57ca3a 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 31927b9645 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 237c95d32c 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new ea2d89bdf6 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new f519d85c61 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 31d7f47e03 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new b223492671 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new d29e4d1190 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 9c34004c6b 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 061acf42fe 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new adb0155ef9 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 81acb4a762 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new aad021d5d0 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 2abc13e1ec 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 008ddf0e3d 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 1822ed62c9 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new ba94aa65db 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 0a323ffdda 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 26e14a93aa 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 671ddf9872 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 98ff8c2096 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 3019dec539 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new b941825ad4 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new ef58b6c61a 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 71a6403d99 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 2d291ec89b 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new a09dba96d3 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new f9c945adb2 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 7ff8120beb 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 9bafc1e1d1 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new a7eb69d248 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new bea1ef91ca 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 236f91ccf4 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 27619d82d3 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 55c512d898 301: onsuccess: #2118: 1: Success after linux: 16 commits new f96b42ef60 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new bc5581f0f1 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 63fff1b4c0 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 1e5f984d5a 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 8330ba8ece 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 1d75d569d0 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 3020d721d3 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new adb16ec6d6 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new b748bb341f 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 7f39351fb0 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 9c34b5b2c1 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 8ba539d4b2 313: onsuccess: #2133: 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 (c7a5664e6c) \ 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 1780 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31812 -> 31696 bytes 04-build_abe-stage1/console.log.xz | Bin 92164 -> 92168 bytes 06-build_abe-linux/console.log.xz | Bin 8536 -> 8872 bytes 07-build_abe-glibc/console.log.xz | Bin 236592 -> 236444 bytes 08-build_abe-stage2/console.log.xz | Bin 229004 -> 229180 bytes 09-build_abe-gdb/console.log.xz | Bin 39656 -> 39204 bytes 10-build_abe-qemu/console.log.xz | Bin 31724 -> 31608 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3216 -> 3316 bytes 13-check_regression/console.log.xz | Bin 4808 -> 6956 bytes 13-check_regression/mail-body.txt | 27 - 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 28 +- 14-update_baseline/console.log | 40 +- 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 | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 37 +- sumfiles/g++.log.xz | Bin 2686036 -> 2689720 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 2235876 -> 2238212 bytes sumfiles/gcc.sum | 2248 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 890576 -> 897376 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214076 -> 214132 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437280 -> 434868 bytes sumfiles/libstdc++.sum | 8 +- 39 files changed, 1239 insertions(+), 1256 deletions(-)