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 8ae16f97b1 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards a2ae2ee67c 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 13b7a87e84 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards b2eb9f9313 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 9607307f70 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 09656ecfb8 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 8d532d71b0 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards b3cb87b1ac 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 56d6a0aa1d 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 4cd28a0310 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 0fcce08ff3 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards de14e3ac5f 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards ba30cc08bb 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 59117281b1 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 25237d8ca3 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 800a69a86d 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards cc6d3b197a 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards acdf729579 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards ff2cf7b2e1 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 9bd9b5f7bc 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 5f3e0f30af 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards f4aae3b70b 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 556c39796f 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards c56f832fa1 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards cd4a585241 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 55c8ea0df7 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 6cfeac3776 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 1a840ea6fe 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 91635bf7a8 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 8f343022ae 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards da3c2ff076 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 28670972be 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards d8e597ac4f 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards d4d85940a8 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards b92aecd10c 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards b1826db4a0 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards b8069f386c 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards d4714c9e6e 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards ef9d7c1df4 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 79b6c9511b 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 0ca49a870e 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards fc20dba488 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards d0b47ee62d 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 0e65557489 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards e06c8129fd 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards a52ae37bfa 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 2ef24cd6be 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards cdc0da8d1a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 9679f562b5 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 1e7be316ac 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards f790be27b2 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 1fcc8444b1 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 64f2b5a26f 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards d961a8b14a 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards fc1e50c410 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 904b52ebc9 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 703f2cf581 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards d20d67e309 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 67237a3046 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 2ac81e0c96 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 036cfe5a50 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 06970d5c16 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 7bec491f1f 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 2eba49fc25 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards c87aa7495d 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards a36a19e80e 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 3d87ae196a 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards fc6dde3baa 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 203213dc51 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards b6a7e10b41 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 27134575a0 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards b5c4f445c5 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 9e5110776d 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 5315ace778 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 68c3ea877d 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 861dddf5a2 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards f5b39884dc 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards baf28109fb 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 2779a3f494 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 081eca3503 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 88e0137bf2 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 7077c3d257 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 1fbe86d5f1 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards c9ed8b3be5 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 68ba36ba76 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 03d1cd7dfb 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards abd24959bb 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards a3e3689566 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards bd000735c9 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 62042e316f 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 0b0e00baa4 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 1da706d239 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards f8178a17e6 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 1a14d7ca56 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 7f8a6fa834 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards c04923148f 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 326a8b8293 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 501897582c 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards a95ee1fa29 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 46b8d5714d 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards ac2c6f2c3d 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 8f03773cd9 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new b1c2a3c4ef 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 5c877888d6 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 71e1f028df 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 5efc5f3799 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 06fd1ebc5b 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 662e5e86c2 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new a06a6d2106 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 7152201260 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 990dbf57a5 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 8c37c81ba6 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new fdc2efa2c2 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 126494ab4d 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 29a7bd5595 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new d398c4d647 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new a48e5bb469 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 35cbb461b3 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 38d64db621 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 1a1dff1124 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new a2331b137e 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 302776fc4c 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 51d25599d2 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 117ecdfa9e 301: onsuccess: #2118: 1: Success after linux: 16 commits new 8e0f2a2caa 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 9254bb2a95 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 717769314e 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new dcf9aedd8f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 05c00e63b4 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new a1abd52b19 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 48303af927 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 100c5bed58 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 5e3cd088aa 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 5c87742a95 311: onsuccess: #2130: 1: Success after gcc: 4 commits new be30d98236 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new ab33e67079 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 6756fe00ae 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new c1efae1e5a 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 6db225ba6f 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 381099e3da 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 94c69e35ce 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 007a02a593 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 8853da5227 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 226c3bac75 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 6635ec04d7 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 75c85a2270 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 8de862b4b3 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new df83083ce9 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new e22e3a5feb 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 7e48d73740 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 4c7794b206 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 746403d77e 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 67c85eb561 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 2c2abadb41 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 2b6914644e 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new e2e1174d07 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 6a695ff5b1 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 16eb5b73dc 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 60973efba2 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 72e3d3d1b3 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new e20d2f9b91 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new e502ae275b 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 430385b99e 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new e59aef22e6 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 9d449d44d3 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new db85138b62 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new c82da63f2f 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 849c92a30d 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new a6009ba2de 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 8a2db9d400 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new d82972d28f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 6ef7614923 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new aa896c09dc 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new d18c738d47 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new e3c8587546 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 01525088bd 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 46c671f1bb 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new ef6354e64e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 70aed267c5 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new c89716d056 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 9cf60a095d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new de01bcf28d 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 08bb61b1a9 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new b7ac50a573 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new f335998590 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 44ab5483b1 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new d14909de0e 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 83d8900889 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 8e0a9ffbe0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 266d02e526 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 313d2ede3d 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 83df08b678 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new ff95f8e2d3 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 980a41b7ca 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new e16afdde0e 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new e3cb43811e 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 8bc4b08049 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 2693a40854 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new b249595f86 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 4a342ab5e2 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 089b781634 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new aff771b461 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new a977f2b46e 380: onsuccess: #2201: 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 (8ae16f97b1) \ 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 1756 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31260 -> 30856 bytes 04-build_abe-stage1/console.log.xz | Bin 91856 -> 91704 bytes 06-build_abe-linux/console.log.xz | Bin 8560 -> 8980 bytes 07-build_abe-glibc/console.log.xz | Bin 235796 -> 235844 bytes 08-build_abe-stage2/console.log.xz | Bin 228920 -> 227452 bytes 09-build_abe-gdb/console.log.xz | Bin 38624 -> 38112 bytes 10-build_abe-qemu/console.log.xz | Bin 31792 -> 31800 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3124 -> 2632 bytes 13-check_regression/console.log.xz | Bin 6496 -> 5728 bytes 13-check_regression/results.compare | 14 - 13-check_regression/results.compare2 | 34 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 2666272 -> 2667840 bytes sumfiles/g++.sum | 20 +- sumfiles/gcc.log.xz | Bin 2191752 -> 2196680 bytes sumfiles/gcc.sum | 1984 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 890648 -> 893752 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214392 -> 214336 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 441400 -> 442836 bytes sumfiles/libstdc++.sum | 34 +- 38 files changed, 1101 insertions(+), 1115 deletions(-)