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 fc73ce81b5 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards b6258097b4 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards ae8500ad7a 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards b321423c80 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 51664e612c 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards deddf1cad0 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 3363e60ccc 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 29665682cf 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 74d3a8db12 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards c8f2a4ee21 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 2f053617d8 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 098580b8c4 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 1002bc80b4 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 85a0f79dba 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 1491a5c75a 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 81639dc8cb 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards c2787c4ff3 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 9e3db43353 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 8200594595 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards d61272cfb4 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 7587ec76d2 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards f112427d96 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 222c3216de 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 60664551dd 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 2da6a69941 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 72213139f8 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 39355cc4e6 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 9bb26c5342 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 64f5645a2e 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards ce7c31d00d 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 740427ecb5 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards b2d4e99eca 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 55943ffe4a 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 403d6d3892 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 1cb1fe1651 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 7d12371ab6 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 725858cfd7 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 34e3da00a9 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards ad9db6ea29 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 3d87b1363b 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 137b194627 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 05d71bd388 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 22741202e2 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards f28be8ca5b 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards f1edec01cd 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 3549361201 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 2f81ee47c5 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 357933fff7 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 0f3c47c7ab 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards ad2102a4eb 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 7b59b0759e 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 42ab0afd92 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 096fe94267 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 6d3eb220a9 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 829f5dd35d 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards d51d83ab5e 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 2b5533cfab 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards c7c42f07bf 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 94aee477e9 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 0ed8ee2e85 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards ad5a513f30 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 9ff537e970 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 8139ff3176 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 25c8310b07 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 70492304f8 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 25659537d7 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 2bb2af14ed 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 14c3bd99b2 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards a45f75977e 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards fe4a842d7b 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 39b50072aa 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards f14004070d 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards e21cd6176b 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 95a4aca392 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards ef4c7a0806 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 5552d13398 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards be4c22ca2d 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards f957799646 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 810ac7894a 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 15a513970e 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards c386a11bc9 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 22ca1110ae 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards a9e5934d1d 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards b2a5d4af37 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 92913a433a 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards 56654e60a7 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 59ce5b91e4 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 4630526032 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards ad566b54dc 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards c36350672f 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards 64cfeb0d8c 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 5d44838417 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 2c7dd6b20a 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 78a42356b4 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 6950b0a408 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards 81adfd77c6 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards ac4a8e5ea5 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 2f1410b3ac 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 052907ab9c 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 7431cd9c73 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards bd2a8d4054 208: onsuccess: #2012: 1: Success after linux: 12 commits new 0d99c35fd9 208: onsuccess: #2012: 1: Success after linux: 12 commits new 3106fed558 209: onsuccess: #2014: 1: Success after binutils: 12 commits new b56364c01e 210: onsuccess: #2017: 1: Success after binutils: 6 commits new fd3f41f90c 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 2c021bf0e7 212: onsuccess: #2022: 1: Success after linux: 3 commits new 15edd4bd2c 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 0836ee546c 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new c2bf818b36 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new a4460e9608 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 315d47ea4e 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 3085fea37c 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 7ebcaa303c 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new e09881cb37 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 998e8df259 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new d8bc2516fa 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 2342b85723 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 5ed31384fe 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 8d5ea26093 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 1bb56e88bf 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new c625255a6c 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new a058d794f3 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new c48fe4ae08 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 4aafc150a6 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new f57a93e7d6 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 2d78047657 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 2bf1aeb367 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 1af94aace6 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 6566c8c78c 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 9c3dd2a8cb 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 0612bb43ee 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 7ea9be270d 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new b8bd0a36ee 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 0ce71c750d 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new e7ef2244f0 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 4a4b265681 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 9218452b8f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 9a6b26bc58 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new b234c1af9a 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 6c4e611a9a 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 55f5ec6723 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new e4595dbfec 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new d4100035fd 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 47d68d4276 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 69e7027f8e 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 4b35656eba 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 30285f6059 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 62ad6e3b3b 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 4e9951aa47 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 755fc62566 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 504b6e34f4 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 6a388eb44b 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 4d418abae3 259: onsuccess: #2075: 1: Success after glibc: 2 commits new afe1bba11d 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 767e8a66ce 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new ac58f4ddef 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new e2645e5285 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 2272c81410 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new fc0cd7c9e9 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 09c8b99be5 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new bc37db0bbd 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new cea36ee2df 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new eef0b10d63 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 9a6cb3527e 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new a20bbb3dc1 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new aeed047018 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new b7cc2003bc 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new b33518a8dd 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 3183cbd859 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 41b379e563 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 65563899a6 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new e79950c84f 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 6faab78220 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 5221205c6f 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 666e573565 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 93d65afddd 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 3732917eb8 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 00a8326053 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new f93921cd41 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 906c1e4f79 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new c9cecf51b9 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 2406c76e88 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new bb261757bc 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new fee1c12b10 290: onsuccess: #2106: 1: Success after gcc: 2 commits new e7ad44eb73 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new ac1b00ec7a 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 8ab6103a7e 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 7e2e4d1254 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 1c54d414cf 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 8a3ed08e32 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 81c89f36fa 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new bcf7f11bb0 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 73d9318102 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 33d3e955e1 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 733fa3f7de 301: onsuccess: #2118: 1: Success after linux: 16 commits new d1a8cec3bd 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new f26a260834 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new c4a992986a 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new a0de011813 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new cbd409f3b1 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 947e16ed3c 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 4afc43d439 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 98227226ba 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/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 (fc73ce81b5) \ 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 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31828 -> 32356 bytes 04-build_abe-stage1/console.log.xz | Bin 91316 -> 92112 bytes 06-build_abe-linux/console.log.xz | Bin 8364 -> 8380 bytes 07-build_abe-glibc/console.log.xz | Bin 236344 -> 236932 bytes 08-build_abe-stage2/console.log.xz | Bin 227868 -> 229192 bytes 09-build_abe-gdb/console.log.xz | Bin 39256 -> 39688 bytes 10-build_abe-qemu/console.log.xz | Bin 31132 -> 31476 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3924 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2504 -> 3028 bytes 13-check_regression/console.log.xz | Bin 6320 -> 6084 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 27 +- 13-check_regression/results.compare2 | 34 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 26 - sumfiles/g++.log.xz | Bin 2684368 -> 2659016 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2224500 -> 2230876 bytes sumfiles/gcc.sum | 2362 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 893336 -> 896072 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213820 -> 214008 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 430888 -> 438008 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 1335 insertions(+), 1387 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions