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 b1cc252521 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards da3ef6bcc6 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 84cb9b12d2 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards f63613a5ba 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 6e95431c51 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 0b520796f9 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards b67a10ec01 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 996df75641 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards a63d890cf0 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards fc730376c4 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards ee01a6ce65 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 412ecb2b00 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards a5c68a5a06 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards bd1af3166f 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 8428e9b94f 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 0d61023eb9 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 0bb5099d9f 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 07161d8a37 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 7eeb58f24b 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 5ac663d2a5 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 2e9369e328 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 347db1c12e 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 400c205dbb 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 548470737f 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 5b5add4204 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 7ade4245e1 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards b07481a81b 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards b7da19a4e4 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 5142642672 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards e8df69c1ce 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 441ff838b4 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards db8c9c2874 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards c54a596f6f 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 13f7a5b9b7 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 9436cbdc06 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards b8aef0d1b6 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 4cdf4ea972 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 2410f85ddc 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards c00eefd66a 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 512cb4f33a 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards f1c5fe70cd 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards c8004aedbd 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 7b35a41a72 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards caad4c2614 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 660588a3c4 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 0b80214d47 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 13b031b946 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 8575bd2546 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards cc626bd701 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards abeac8f03e 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 7e679913ea 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 281c08a56b 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 6b7c60625e 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 168af6644e 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 45cdef615a 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 5792ec23a9 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 3826adeb49 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 19b80bb3d6 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards e9def42954 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 5e0eb3f3a0 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 55bce7a5ae 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 28ca8cec20 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 673dbeae6b 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 6e45ea23dc 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 5aa1b6783b 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 4d5e311d6b 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 128e75602a 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards c49aeaf18b 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 792a5c3026 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 041d26b68c 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards d2c2a19f98 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 37cec5bb6b 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 0f1f42cc07 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 1a47dcc233 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards fa396c2abb 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 1d3ac6a64d 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 32667a1c11 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards a22b1013ec 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 0166d71715 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 40c2a955d1 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards 9b9b55225b 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 14f82c8327 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards 2fe33565bf 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 897031bf40 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 8f007f5990 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 84254e0b8e 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards 3feec61c07 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards a7fe2d839b 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards f7c4b3ddfd 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 49110a8af8 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards e2c9a1d6af 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 795b198093 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards e22e4c7838 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards ce13833c13 212: onsuccess: #2022: 1: Success after linux: 3 commits discards cf325421b1 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 50c173e491 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 6fea5291af 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 2b0e5b4e84 208: onsuccess: #2012: 1: Success after linux: 12 commits discards c95d6270d0 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards ede6664e1d 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards ea08551b4a 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 6d039066b8 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 5b85b52c3a 206: onsuccess: #2007: 1: Success after gcc: 2 commits new e679e411d4 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 5bdb436d96 208: onsuccess: #2012: 1: Success after linux: 12 commits new 5fabb292b1 209: onsuccess: #2014: 1: Success after binutils: 12 commits new d3855e24d6 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 6fe0227e9e 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 29fbb0ad90 212: onsuccess: #2022: 1: Success after linux: 3 commits new 2470f5cbcf 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 0a5afe126a 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new bdbf8a6385 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new f81f13029a 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new f4382deb2d 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 211a0a4541 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 185da74460 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 3a71419ec1 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new a0821a3e66 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 896b53ad68 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 98db805a49 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 1786dd46a7 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new d7d67b0a72 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 90c802c8d4 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new c59bea9f26 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new 638fa5b09b 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 2728edb892 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 3b2a1f9d1a 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 29db1ace3c 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 2414c1a854 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 3c7c0f4a23 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 5397289cb3 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new a44c15f501 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 2bf61558ab 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new c034738ace 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new d32cbacd26 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 67ec1afc2a 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 9d9986f0bf 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new adb08a1337 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 6f0893a5a0 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new ba43e11bcb 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new f3876c1ac7 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new c39853dc4c 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 8c9c65ca27 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 1a6d6bd33c 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new e77b888c34 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 56427a9745 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new f8a1021048 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 3cad71238c 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new b8fd535e46 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new c41f6566f9 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 10d3d368a1 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 09f84ad701 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 2c323f8646 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 4f646fd9b5 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 4000b18be9 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 62e5dae348 259: onsuccess: #2075: 1: Success after glibc: 2 commits new ff03aa7f51 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 9a8cd63a9b 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 2d7eeb88eb 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 74e1d64207 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 0904360e3b 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new da91f40229 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 6ca3befdcb 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 626463c00a 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new bea6a3f4f1 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 4af7609e38 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new daf28eebbd 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 9815207f54 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 36b8c7259d 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new a6635c0686 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new ab7416e3fc 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 1f3b9f9b2e 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 3ff02b983e 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 5b6946afd0 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 00530df6ab 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 232599190b 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 868ecbd511 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 59edf08229 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 5f72323d30 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 81989eb3f8 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 8621a0b26f 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 2e5749a260 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 8ac4bf83bb 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 236caabdbf 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 52594a7941 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new bbd9bab8dd 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 378f0a4e93 290: onsuccess: #2106: 1: Success after gcc: 2 commits new d9d6198641 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new e0481b7026 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new f3e2a0d1cb 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new f661e2c63d 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 77f56f885e 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 8f257d0f9a 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new ca78165a56 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new ad79b550c6 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new ce286ddd60 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 1097e64ee4 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 2e19544a35 301: onsuccess: #2118: 1: Success after linux: 16 commits new 1c91fc2a04 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 8a01639348 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 400cee89ec 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new ed861bedf2 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new ee7562ba91 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...]
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 (b1cc252521) \ 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 1776 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31908 -> 31928 bytes 04-build_abe-stage1/console.log.xz | Bin 91456 -> 91936 bytes 06-build_abe-linux/console.log.xz | Bin 8752 -> 8748 bytes 07-build_abe-glibc/console.log.xz | Bin 236616 -> 237100 bytes 08-build_abe-stage2/console.log.xz | Bin 228196 -> 229376 bytes 09-build_abe-gdb/console.log.xz | Bin 39120 -> 39340 bytes 10-build_abe-qemu/console.log.xz | Bin 31780 -> 31360 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2488 -> 2752 bytes 13-check_regression/console.log.xz | Bin 5504 -> 5972 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 66 +- 13-check_regression/results.compare | 29 +- 13-check_regression/results.compare2 | 28 +- .../results.regressions | 73 +- 14-update_baseline/console.log | 48 +- 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 | 68 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 40 + sumfiles/g++.log.xz | Bin 2667104 -> 2685008 bytes sumfiles/g++.sum | 6 +- sumfiles/gcc.log.xz | Bin 2224964 -> 2245352 bytes sumfiles/gcc.sum | 2502 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 890516 -> 893084 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213924 -> 214088 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434720 -> 429720 bytes sumfiles/libstdc++.sum | 12 +- 42 files changed, 1497 insertions(+), 1436 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy mail/mail-body.txt => 13-check_regression/results.regressions (72%)