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 5ae7ff64a9 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 953b3397bd 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 91a4fc911a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 432cc52821 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 95da556c09 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards e28c724f07 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards f14ea69936 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 5434ba7116 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 35c6767f2a 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 4c7a1f0e20 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 4e24a2dab0 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards dbcf8397ff 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 0cbcec8abd 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 832b817f66 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 434a3b8eea 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 1ac3eccc38 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards fff0a4f88a 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards d90604c7eb 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards acbdccb50c 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 6fa7409453 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 9576cf4264 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 5e665521b5 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 688c4323b1 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards bd126979ff 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards aaa8378978 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 8792cce1da 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards d6ac12ddc2 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 75814287c9 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards da455c7e7e 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 81ea259355 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 9ca9dceb49 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards b21319372c 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards ccdc3b9f7e 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards bbe06a1e0e 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 641f382f18 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 6a2f0d1fab 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 491f1bc6ae 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards dac956f779 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 4e6a2ba6f2 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 429f5b3859 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards ef790308e8 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 98b9740d85 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards be35cc2897 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards e3fc8edbb0 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 6f7b7c5cc0 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 2dba1011c6 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards e2f579ac5d 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards b1c740af36 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 08bd99862b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 1bf4224569 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 82dab11056 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards a7495bd211 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards e113bbccdb 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 81571f6656 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 376014573f 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards d4671f6601 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 4bba4f2406 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 25878bd7f2 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 4a8fa53af8 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 5029b3a22b 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards b604285ab3 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards e30e52bba9 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 7b673f0b1e 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards db9c813656 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards b79e480f19 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 3747081052 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards ae8348240f 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 00afd88e76 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 114a2377b1 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 5b8b8df07d 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards f8691b543b 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 1dd02434f7 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 3e4fafe548 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 4a63f816a6 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 402d71e751 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 48fb606573 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 39bc5e9cf7 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 260a24758d 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 3c4f6497ef 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards e8521a3a2a 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards f36346c5bc 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 9752ac849e 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards d68bd21bda 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 12e6ad540b 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 606f344c2c 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards b7c47dea38 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 7f1f1dd62a 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 3080f4ab3f 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards b3cf99b57f 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 292f1be58b 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards f6815c99ca 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 5482c101c7 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 6a7d08aa09 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards fd40f3ded0 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards f40cfee96c 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards cb8cce3145 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 59a4a2fb34 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards c0197ace4c 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 5f1e15e42f 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards cd39f6403a 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards d164b31494 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new cbf8ae07e6 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new aaf5baab6b 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new ace61daf1a 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new da2213cabf 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 239b88e39e 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new cfa6f213d1 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new abd4ff9fd7 259: onsuccess: #2075: 1: Success after glibc: 2 commits new c10704ff79 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 84b38e9072 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 5307d1d086 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 570ee11033 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new c51a13fa38 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 722e8ca80c 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 9d6860866a 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new b38cdfc0f4 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 4ae88e9511 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 4aaf8ee526 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 0133826faa 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 0268933fe1 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 0c1dbf23b5 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 92eb173717 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 4bfe4ae00a 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 8bb5ca23cf 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new d26b5f21ba 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 73db0cb356 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 8c1c070b2a 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new b37b8b3a41 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new df53f39e1d 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new fe34d21ae6 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 5c4a0babc6 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new ef50f8a744 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 9338a466e4 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 61c284c5cb 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 818d85b583 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new eb10ff2d20 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 56908cd7f6 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 7eae978024 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new f5d830cf29 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 840d264b54 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 70fc17c230 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new adc6b2d5f1 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 0ecaed706d 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 36578db7da 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 009cf8359b 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 5adfc3a043 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 60c3853a05 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new a60d72aed9 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new a9e7a2dfb6 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new e834fdad42 301: onsuccess: #2118: 1: Success after linux: 16 commits new 1bcdee96b9 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new ae8edaccfb 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 91b4a49c04 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new fe9dc055f2 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 65d60e6d7f 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new d9c3e0d810 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 955064e4f6 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new c8287799ef 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new e67a38c416 310: onsuccess: #2129: 1: Success after binutils: 4 commits new a1435c4041 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 678a6d853d 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 9753475810 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 1bf0c38909 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new ce889c5cb0 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new f5c29b7312 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 964bf20119 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 387d7c1191 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new f9a994476d 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new dea55629c8 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new ca07987d9b 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 21a4cfe965 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 5fd35f8e0d 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 41cd357880 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new c128844fc2 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 3a30fd82f8 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 70923c75e8 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 79a644302c 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 91a9c8e6f4 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new bbd7a7743e 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 394e58e340 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new c60144afb2 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new ee5816513d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 48d32735ad 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 562b68bbd2 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new a00e668827 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 27b786effc 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 1e2ec317e2 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 67eb18b095 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 0ffebd7685 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 7178f31bbf 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new c8bdbb7a27 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 2a3659f0a0 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 1ac919ca6c 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 5c8a9da14e 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new dd9cb313bb 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new ad7f44e650 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 80454c6e8f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new fb567ce0f9 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 387e270c71 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new d2a4cc3713 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 08de91f2a8 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 5acd011ffb 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 98f70443af 354: onsuccess: #2174: 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 (5ae7ff64a9) \ 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 1796 -> 1820 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 31544 -> 31868 bytes 04-build_abe-stage1/console.log.xz | Bin 91952 -> 92604 bytes 06-build_abe-linux/console.log.xz | Bin 8764 -> 8852 bytes 07-build_abe-glibc/console.log.xz | Bin 236496 -> 237612 bytes 08-build_abe-stage2/console.log.xz | Bin 228620 -> 229120 bytes 09-build_abe-gdb/console.log.xz | Bin 38908 -> 39200 bytes 10-build_abe-qemu/console.log.xz | Bin 31924 -> 32264 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2592 -> 2668 bytes 13-check_regression/console.log.xz | Bin 5620 -> 6068 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 12 +- 13-check_regression/results.compare2 | 4 +- 14-update_baseline/console.log | 66 +- 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 2692108 -> 2668484 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2245452 -> 2267360 bytes sumfiles/gcc.sum | 2146 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 895432 -> 897408 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214048 -> 214200 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432016 -> 434304 bytes sumfiles/libstdc++.sum | 2 +- 39 files changed, 1165 insertions(+), 1217 deletions(-)