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 1cb52bbf23 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 5c1c55587c 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards ab5ccc8dfd 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards d0ee14ae3a 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 288d9833a9 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards a08d405f04 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards b4f31199d5 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards e389b01979 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards b43500b1a8 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 7d80492d2d 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards a2f81b0ee0 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 0ee2a3ee9f 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 001d27c1b0 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 0a89c39283 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 9c5d7645db 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 7fcb1580b8 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 6268d9412a 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 3904eb4c73 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards ef3a9f9278 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 258c13c8e7 301: onsuccess: #2118: 1: Success after linux: 16 commits discards ec52532452 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 2a527a5b25 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 49a834e11c 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards a815bf6bbf 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 5e44ad45ab 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards aa20d3c2b3 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 72ecb7d4a2 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards e2cf14f68a 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 70082ae672 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 79b35432d6 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 8baa816ca8 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards f37e47b0f5 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards ba64e35c88 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards c41f902b8a 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 700aad5e64 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 39d7edce20 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards c0b0d7953a 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 46fad27064 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 7a384b59b5 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 494c149e03 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards f7ac24ccfb 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards c6d9e40811 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 6665115a2c 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 81248d900d 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 42cc6a9b9f 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards f628f1f66e 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 9821594a90 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards ef17772b78 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards fd628a25c7 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards d897955bf7 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards fea61ebef3 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards ba840d0c2f 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards c2b620f141 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards b529c10835 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards a516314442 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards ef6875b050 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 1a7d26282f 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 8a06225d9f 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 7309c861ba 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 0016ed3b94 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 93ad0f36d8 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 309253c890 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 40b331cd33 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards c63e9f05a5 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 6dc3464e5c 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 3aaa9f5edd 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards a36063eefe 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards b315da0b12 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 8a9e1fbd51 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards a05b583126 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 300e8c7878 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 707df119d7 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 158089b823 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards fffeaef8fd 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 949ca684f2 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards d5eddd1f85 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 4cfcc80668 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards c82122fb2f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 5c92639ee0 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 3671f66f12 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 5eb12da50d 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards c7860231e9 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards b415e8bea8 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 6e6a23b256 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards fed28d749c 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 463c5e3d87 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 4f20052063 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 209dd6d552 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 55ddc2af01 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 933497ed9d 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 3592dd5e30 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 18338b0a12 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards 9bf0fe91da 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards bc8ee669a9 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 492a0f872d 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards f7ddfb07de 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 8fc29fd5a3 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards ccabc1793c 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 23421c030f 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 3e96b7badd 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards e6396192a2 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 3d641c9fba 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 48376393d0 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 73d3efe2e7 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new ad53738dbd 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 697a0d8206 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 092c083b5c 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 458ea5c870 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 61643e9901 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new b5a2859212 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 9ca686d3b7 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new cc2be5ead3 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new b6ce9e09d2 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 667137594f 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 9c89c9e7f5 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 47587548d0 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 553c38e5b2 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new d1c23d6949 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new e67e75781e 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 4f8dde9004 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new f511ad6ad9 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new b42d53ec4f 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new d16b9e3cc7 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new b94508f8a6 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 94d2b21974 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 1ffb6c9c7c 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 4497738683 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 7da8728ec2 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 2b7fd9d7fd 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 796959357a 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new ea48e429c5 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new db793f9da0 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new ce9d2289ab 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 45c1da5828 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new b800d7e76f 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 0d80c47684 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 03c873536a 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 340e7fd48c 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 3a7b3558f7 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 1d9d6d0f02 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 738d276ccd 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 86c1eb8069 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 4582761732 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new fc5788222d 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 865638e35c 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 20ac33173d 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 48ca671af1 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new cf3c71d8a4 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new f60f8ee98b 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new a3ee3ba7a3 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 38fe27019d 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 8f1e387528 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 131d935ac8 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new d94eb87fcd 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 17567287a1 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 5123a24375 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 3ca9c1baf6 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 93dd80ca30 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new d0fad4a60a 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new d807a6f25c 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new f4411e5b32 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 42de54056c 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new f066ba5b3b 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new cd51239264 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new a6cc7a4b13 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new cb2097002a 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 73478d6ad4 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 78901c5349 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new fa0adc6563 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 6cef5c44fa 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 5225961ee3 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 366a37e442 290: onsuccess: #2106: 1: Success after gcc: 2 commits new df0637ec9f 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 1f5f01faae 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 8dee5ee18c 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new b5462c20e2 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 93c0f3732a 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 8754f5aafd 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 2783c21893 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new a96ab96172 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 0cd01ad959 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new c8b5b369fa 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 74e234cd75 301: onsuccess: #2118: 1: Success after linux: 16 commits new 9cc6b5498c 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new cd3aea663f 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new b9bed5b719 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 952e2a951d 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 314a2b9aa4 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new d14a5453fa 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 02b2a68ce8 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new bef249e48e 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 917a5fde47 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 2ba2604ee5 311: onsuccess: #2130: 1: Success after gcc: 4 commits new c5b0ca6609 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 8a696fa83c 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new a6e4994a39 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 8ec9f72a3b 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 9bbc8ccde6 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 62288d9dd8 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new bf7838f29b 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 41d5cc3a2f 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 65f32e1bc2 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 078496ace4 321: onsuccess: #2141: 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 (1cb52bbf23) \ 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 1740 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31864 -> 32848 bytes 04-build_abe-stage1/console.log.xz | Bin 92080 -> 91540 bytes 06-build_abe-linux/console.log.xz | Bin 9000 -> 8636 bytes 07-build_abe-glibc/console.log.xz | Bin 237372 -> 235800 bytes 08-build_abe-stage2/console.log.xz | Bin 228872 -> 227840 bytes 09-build_abe-gdb/console.log.xz | Bin 39360 -> 40300 bytes 10-build_abe-qemu/console.log.xz | Bin 31260 -> 30808 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2804 -> 2740 bytes 13-check_regression/console.log.xz | Bin 5820 -> 7568 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 28 +- 13-check_regression/results.compare2 | 51 +- 13-check_regression/results.regressions | 28 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 +- results | 28 +- sumfiles/g++.log.xz | Bin 2673260 -> 2661064 bytes sumfiles/g++.sum | 52 +- sumfiles/gcc.log.xz | Bin 2267288 -> 2271376 bytes sumfiles/gcc.sum | 2372 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 893996 -> 893080 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2268 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214112 -> 214016 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432472 -> 441512 bytes sumfiles/libstdc++.sum | 12 +- 44 files changed, 1440 insertions(+), 1361 deletions(-)