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 219ef39e4e 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards f0fff08d58 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards cc9b0bfede 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 25a84d0936 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 10061a5f9d 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 1587529d35 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 2980733413 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 8428c8f2c0 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 98511389a7 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards c84c48fa21 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 3f56766078 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 99522919d7 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards efe2edfe45 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 59e35530b4 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 576da713d2 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 4e59198449 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards de088c305e 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards d0eaa90d1a 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 8f007dacc0 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 61ef3e7ef2 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 6edf1c9ff9 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 14ca5f3197 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 75fcc4a285 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards ea71827080 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 53527e043a 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards be70753388 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards cac7dc150d 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards ce7748ac3c 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 9d71b792ec 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 2d1d42bbd1 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards d0755f1bb2 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 3f1be86e8f 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 1e782e5365 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards e9dc9776f1 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 80f6705aa6 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 79283a421e 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards e50e1d13da 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 92b621449f 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards f8852a48dd 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 50214a179c 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards bda996c9e1 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 5f5777a423 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 62eea2367a 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 465bce28eb 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 37c24e51e4 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 80d4247eb3 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 9244165a26 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 0b25f38ddb 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 72871ae79d 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 88ff5984a4 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 3dab253b8b 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 2a0916f1b3 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 2e42531fa7 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 7a9cf8dae4 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 2518087576 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 632ffe2f6f 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 9c65ed1d24 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 4181954622 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 1b21bc7535 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 5281dcb0af 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 3760585e6c 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 381b10dded 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 82399af005 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards e8a5205926 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards e801081b1e 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards ab89431d12 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards c2b27521c3 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 3c7a46b368 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 3f57d57c7e 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards c16f3ade75 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 09c9176401 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards dce93d3025 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards d53639996c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 21610718c6 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 314f0fba90 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards d75941804b 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards bbc9693e5d 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 8a48e6bfab 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 9bfa0c813b 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 95dcf7a179 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 2fa5a95334 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards de1a011d3b 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 240c36ea43 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 7070a87729 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards f8cb46e44c 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 3309bad612 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 5008f0d809 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8bac8553b5 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 910e8cf532 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 3672c8687b 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards c37b47c4da 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 3f343088be 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 41e06da79b 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 6a8621d5aa 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 97ef8a0312 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 4955c368bc 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards aadac72e99 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards a46fc9883f 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 3897023cac 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 68abad3dff 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards d481e9bbe6 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 045d4bc6d0 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 1aabe0a561 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new df03a28bf1 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new b1e4219760 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 6538052271 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 146e4a5ae4 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new b10b3ec19a 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 1cf1ad6ed2 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new af6cc0f4c1 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 2ded95e890 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new a8713bf307 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new fa87acaf82 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 993a56e741 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 3132c7fd95 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 6d3b63fd2a 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 9a458b5164 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 3453181405 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 159625ab62 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new c0fa10766f 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 77d749e446 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new e0921fe7b5 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 1c72f385bc 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 9e5eb54cc3 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new e46dfb4e9b 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 67066a3ff9 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 25faa06a7e 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 55ab03f840 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 8aff8a4da8 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 7418bb258c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new ca41fca909 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 296f1e27d4 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 29eaececfd 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 02620eacad 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 4d22dd5271 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 10c475dad6 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new eb7b49fca3 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 8913011ad4 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new a9d97c90a5 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 25a030b8b8 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new f7814d7d46 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 1d94f30bb0 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 5cf0ae1a72 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 2a83fd8c7d 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 3a8a8e78f8 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new deecbce075 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 710685e9ae 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new b2a02e7a2f 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 13e2e44b99 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 5b0418e446 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 761659b75e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new d0a92f03bf 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 4459ed4c5e 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 79d897949e 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 3c96ea8913 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 383f269fec 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 9c47aa35e8 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new f6a292813d 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new fc8ea142e4 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new eaef1ff35b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new c29a92737b 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new ed357d0e5d 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 1b6e379ef1 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 6fc3e4d9fc 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 4b42efc7b7 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new cc6cbb5dcd 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 3454fbd857 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 6e8f7a801a 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 8065272ce3 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 82df26c928 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 0f8ccda7cc 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 376bc825b7 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 082883eb24 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new d2def8b7d5 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new eff066a7c3 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 35c0934976 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new a1254ff8af 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new a2a2d30f72 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 1945871c4a 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 95ecfce834 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 8d58451207 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 66066f6589 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 4c57c18d92 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new b0117ae5da 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new cf969470aa 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 078f7ae32a 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new ab9e92c399 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 6b4538f577 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new fa1e8fe655 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 1ef9f1f9dd 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new b99a1de220 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 3d88f38ed7 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 3907f27b71 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 8fd7ced69a 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 5c86163de1 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 3695b749cc 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new eb89f6e605 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 59bee58524 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new db62506d0a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new d48f7576c6 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 948a2944b0 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 9bbfb022fe 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 5b73b6acf3 412: onsuccess: #2233: 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 (219ef39e4e) \ 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 1804 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30912 -> 31532 bytes 04-build_abe-stage1/console.log.xz | Bin 91688 -> 91904 bytes 06-build_abe-linux/console.log.xz | Bin 8932 -> 8892 bytes 07-build_abe-glibc/console.log.xz | Bin 236652 -> 236664 bytes 08-build_abe-stage2/console.log.xz | Bin 228160 -> 228120 bytes 09-build_abe-gdb/console.log.xz | Bin 38124 -> 38980 bytes 10-build_abe-qemu/console.log.xz | Bin 32648 -> 32848 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3056 -> 2744 bytes 13-check_regression/console.log.xz | Bin 5184 -> 6544 bytes 13-check_regression/mail-body.txt | 40 - 13-check_regression/results.compare | 14 + 13-check_regression/results.compare2 | 46 +- 14-update_baseline/console.log | 46 +- 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 | 42 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 2629296 -> 2644164 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 2223852 -> 2188520 bytes sumfiles/gcc.sum | 2454 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 897324 -> 890096 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216984 -> 216984 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 442036 -> 440208 bytes sumfiles/libstdc++.sum | 32 +- 39 files changed, 1365 insertions(+), 1385 deletions(-)