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 413d592062 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards dc78b06b15 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 7bf5da7c0d 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 11819f3295 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 855cf26439 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards e2b6728ea1 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards caf484a6a0 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 1adfc065e4 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 1bbed4add0 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards e942c5c91b 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 1491d8f7db 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 6f89910d40 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 10143ac2fa 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 06a59a2025 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards d145ecfa4e 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards f9593092ab 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 5668d6f405 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 13724b65b3 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards ed273a15ee 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards e49cacafb0 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 6bcbcb1a91 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 91792ee226 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 9ac044f7d6 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 081cad49a8 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 73269c1968 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards a948050243 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 87b4abcaa5 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards f0ca65eba5 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 30115e9bf8 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 838e70d97f 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 3063618a16 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards a4fc1a9355 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards dd75af96b3 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards dcbd8d6270 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 64680ab714 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 41d04e9321 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 7b9b90892a 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 5f59b7bb0e 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards c406c07da2 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 495e5a364a 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 34247f2bd1 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 6574bc8021 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards a87f8dfcd0 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 7f5d929f8c 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 67c3ec68c8 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards f9a15b1b3d 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 07d476bdb6 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 0583c446c0 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 1f018e0676 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 580732a0d2 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 815c5370da 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 4013e272c6 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 004495709e 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 6a03e55117 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 9434ad0b1d 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 921beb0fca 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards f758829337 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 51aa600c10 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 8251d91cdb 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 9c7eeba343 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 6373477317 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards c315c2686c 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 08decbcddb 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 99317c0efd 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards e8a5c75c2b 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 8202546d9d 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 5159810fcb 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 4d781dbb9f 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 8326e4bb32 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 90308832c0 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 52330ac1c6 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 54d583c7a2 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards f3970c34e9 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards b9d2482f1a 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 220e062f96 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 6b51c3ca7c 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards fb96f39018 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards dc11d9b663 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 95056b306b 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 271a295f9a 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 5df196101a 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 4d00ba9c5d 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards d0a588f4bf 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 180f110d5a 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 17155778ad 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards b2b4a0392d 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 063990721b 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 1d5894bfdf 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards c34111983b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards e99714551e 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 92fdb0f864 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards ff79e792d3 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 138697b5a0 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 3c783a617f 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 8b244a70b6 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 3675a08e9c 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 29e2f8e42e 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 5ab3662dca 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards ff35778232 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 0e326fd202 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards dd31928532 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 8e0dc8a10a 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 5ab3d0f2ae 294: onsuccess: #2110: 1: Success after gcc: 17 commits new d1b704ed08 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 2e8a289015 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new fdf1a81cd8 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new b0a9c19cdb 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 3cad6cd796 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new ca0618214e 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 98a509fe10 301: onsuccess: #2118: 1: Success after linux: 16 commits new c5e6f3950e 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 8802346f65 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new ac9eac4fa1 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 0918d833cf 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new bd80ea487c 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 565e1af7f5 307: onsuccess: #2124: 1: Success after gcc: 2 commits new cb6dbc7eba 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 61b069cb63 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new ae8de6e05d 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 439510ef54 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 2e315f7273 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 2058b150a9 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new c9dc16407e 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new ee7064c8db 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 8fe05a28b3 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 197fac0f06 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new ebe16b16f9 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new e608b70a34 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 1f9769aad9 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new dffdfb22e6 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 7c40e545e0 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 46bfc2dc05 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new dd10ebcae1 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new acb45673d7 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 7ff10f18d9 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 74927e2c9d 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 8e79577323 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 1f6adb2484 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new b0d4cd5fb8 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new e2961469bf 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 320d2dde9f 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 79098446a3 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 225a501e00 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 5db9d9db21 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 55c5344738 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new bd09e6641a 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new f415aa3dc5 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 1f4f017217 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 70f00368ac 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 63ee3a2382 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 6479c3ad32 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new a5fd35b27c 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 8d9bd05012 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 3f7f397716 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new c046be4604 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new bad2624dd8 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 690fd56d34 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 489104d226 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new c9bafbf688 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 6efd54d300 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new f2174a946b 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 9bb8338965 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 3808fe44af 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new b7f8705c1a 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new ce6f8c8ff9 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new bb8be903ee 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 791dc1fb34 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 3e7c3e8f1a 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new f825f01b01 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 115b1b0c38 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 658bf43159 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 1285d7f32f 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new d49d5e633d 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 016137e2df 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 35fc099774 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new f815245ee2 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 5d8de43feb 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 4aaba214bf 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 67430074d1 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new ecfe1bdb20 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 92891c7ddb 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new fc819d4a41 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 74d26debdd 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new adca36e8eb 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 239bb5919a 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 111fc0f9e6 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new e4057e2733 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 17890ec499 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 798fde396d 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new bd0e85c24f 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 525ffff0fe 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new ff162d7006 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 1f7aad88ae 384: onsuccess: #2205: 1: Success after gcc: 2 commits new c377543dd8 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new b987c162b1 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 1a498b9ea3 387: onsuccess: #2208: 1: Success after gcc: 2 commits new c2fb2768b6 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new d6a2db3b3e 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new ee33458eee 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new b152ad49aa 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 7460576b54 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 7ac452cd6a 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 36c89e1d93 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits
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 (413d592062) \ 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 1800 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 30884 -> 31776 bytes 04-build_abe-stage1/console.log.xz | Bin 91724 -> 92844 bytes 06-build_abe-linux/console.log.xz | Bin 8676 -> 8744 bytes 07-build_abe-glibc/console.log.xz | Bin 237048 -> 237864 bytes 08-build_abe-stage2/console.log.xz | Bin 228604 -> 230756 bytes 09-build_abe-gdb/console.log.xz | Bin 38104 -> 39096 bytes 10-build_abe-qemu/console.log.xz | Bin 32244 -> 32140 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3920 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2648 -> 2812 bytes 13-check_regression/console.log.xz | Bin 5984 -> 6280 bytes 13-check_regression/mail-body.txt | 27 - 13-check_regression/results.compare | 31 +- 13-check_regression/results.compare2 | 156 ++- 14-update_baseline/console.log | 66 +- 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 | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 2642732 -> 2650316 bytes sumfiles/g++.sum | 78 +- sumfiles/gcc.log.xz | Bin 2194796 -> 2226972 bytes sumfiles/gcc.sum | 2158 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 894156 -> 895324 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214480 -> 214544 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438088 -> 444944 bytes sumfiles/libstdc++.sum | 34 +- 38 files changed, 1375 insertions(+), 1264 deletions(-)