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 98f70443af 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 5acd011ffb 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 08de91f2a8 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards d2a4cc3713 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 387e270c71 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards fb567ce0f9 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 80454c6e8f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards ad7f44e650 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards dd9cb313bb 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 5c8a9da14e 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 1ac919ca6c 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 2a3659f0a0 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards c8bdbb7a27 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 7178f31bbf 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 0ffebd7685 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 67eb18b095 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 1e2ec317e2 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 27b786effc 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards a00e668827 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 562b68bbd2 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 48d32735ad 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards ee5816513d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards c60144afb2 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 394e58e340 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards bbd7a7743e 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 91a9c8e6f4 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 79a644302c 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 70923c75e8 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 3a30fd82f8 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards c128844fc2 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 41cd357880 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 5fd35f8e0d 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 21a4cfe965 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards ca07987d9b 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards dea55629c8 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards f9a994476d 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 387d7c1191 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 964bf20119 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards f5c29b7312 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards ce889c5cb0 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 1bf0c38909 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 9753475810 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 678a6d853d 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards a1435c4041 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards e67a38c416 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards c8287799ef 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 955064e4f6 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards d9c3e0d810 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 65d60e6d7f 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards fe9dc055f2 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 91b4a49c04 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards ae8edaccfb 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 1bcdee96b9 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards e834fdad42 301: onsuccess: #2118: 1: Success after linux: 16 commits discards a9e7a2dfb6 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards a60d72aed9 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 60c3853a05 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 5adfc3a043 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 009cf8359b 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 36578db7da 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 0ecaed706d 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards adc6b2d5f1 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 70fc17c230 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 840d264b54 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards f5d830cf29 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 7eae978024 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 56908cd7f6 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards eb10ff2d20 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 818d85b583 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 61c284c5cb 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 9338a466e4 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards ef50f8a744 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 5c4a0babc6 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards fe34d21ae6 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards df53f39e1d 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards b37b8b3a41 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 8c1c070b2a 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 73db0cb356 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards d26b5f21ba 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 8bb5ca23cf 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 4bfe4ae00a 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 92eb173717 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 0c1dbf23b5 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 0268933fe1 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 0133826faa 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 4aaf8ee526 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 4ae88e9511 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards b38cdfc0f4 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 9d6860866a 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 722e8ca80c 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards c51a13fa38 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 570ee11033 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 5307d1d086 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 84b38e9072 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards c10704ff79 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards abd4ff9fd7 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards cfa6f213d1 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 239b88e39e 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards da2213cabf 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards ace61daf1a 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards aaf5baab6b 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 1637a4ed97 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new d6e50cf927 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 6dc390b63e 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 7033bc42bc 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 7b139c3d37 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 84363ca0f0 259: onsuccess: #2075: 1: Success after glibc: 2 commits new df6e0e77d9 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 77df4d521f 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new bc7a3f1838 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 9596de9ac1 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 9f1188e619 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new bae0955a72 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new a301c1d869 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 5181435569 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 29f248c141 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 2e86d555a0 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new ace9e2f5f8 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 0b1320b33f 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 84fa122204 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 3007d850e4 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 5109350336 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 476e7d4326 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 21d725f40f 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 5ddddca560 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 5edfe816cc 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 6033e5aad2 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 203de9c2ab 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new cb8bfe0de9 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 45ead76530 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 79e0887708 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 61e25423bd 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 248df88ac6 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 053bc4faa7 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new f1d9404103 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 383353bb0b 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 21e6ab3768 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 88615de8d1 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 08213c04c4 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new b509f272b9 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 783e97ed8c 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 810cdc2bd7 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 90c83adfc7 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new c7cbc3cb04 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new d83f16c506 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new fd8e2288bd 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 89886ae647 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new c21ea91863 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 59208a00ab 301: onsuccess: #2118: 1: Success after linux: 16 commits new 47140889a6 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 54d8a3325f 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 9b22c49b19 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 958e452f0f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 4de9a44ae9 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 7b9f3b6d32 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 3cc8fdc28c 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new b2c29babe4 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 8adb8d613a 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 89e74b3b20 311: onsuccess: #2130: 1: Success after gcc: 4 commits new fca4a7e170 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 338be4d515 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 886ff12250 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new cd8cfeddbb 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new cae459a612 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new ba02b6fe2b 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 24266699dd 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 6f6c621aa7 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 2dd6acb727 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new b582291c4b 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 08fd32f261 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 004dc3657f 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 598e69c54e 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 3a18a06bf3 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new d4d26e1972 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 14b2a02587 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new d161c5ad31 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 98a70bc5b9 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 9d84a3ce34 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 7380a5dc2c 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new d0d34be69d 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 9f06019dde 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new c9cc1f65dc 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 0178ea85ce 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 4e731c8ef5 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new a88b20a031 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new ec95fbaad4 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new a3414f91f1 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 4c20a69357 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 710bf20501 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 9b0e81c44c 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 42e8a2a21e 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 45e9763f9f 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 0fafa31435 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new d86a0ed08e 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 06068cc790 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new e640cb5e7a 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 908e4f8365 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 4fc759d844 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new c3f2bdd5a9 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new b971f3ee16 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 5f1eee3bb1 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new d3aa0aff71 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 6c824d0be8 355: onsuccess: #2175: 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 (98f70443af) \ 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 1820 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31868 -> 31860 bytes 04-build_abe-stage1/console.log.xz | Bin 92604 -> 91356 bytes 06-build_abe-linux/console.log.xz | Bin 8852 -> 8348 bytes 07-build_abe-glibc/console.log.xz | Bin 237612 -> 235928 bytes 08-build_abe-stage2/console.log.xz | Bin 229120 -> 227904 bytes 09-build_abe-gdb/console.log.xz | Bin 39200 -> 39072 bytes 10-build_abe-qemu/console.log.xz | Bin 32264 -> 31980 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2668 -> 2472 bytes 13-check_regression/console.log.xz | Bin 6068 -> 6376 bytes 13-check_regression/results.compare | 22 +- 13-check_regression/results.compare2 | 30 +- 14-update_baseline/console.log | 66 +- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- sumfiles/g++.log.xz | Bin 2668484 -> 2676688 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 2267360 -> 2280396 bytes sumfiles/gcc.sum | 2192 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 897408 -> 894036 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214200 -> 214120 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434304 -> 436612 bytes sumfiles/libstdc++.sum | 6 +- 39 files changed, 1228 insertions(+), 1196 deletions(-)