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 735ed65148 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 06acba9d12 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 007db34804 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 67f5f69fed 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards ed504dd967 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 0fcf68bce0 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 55b134b20a 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards f934e6e439 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 3f346df29e 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards db39088e15 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 05a8cf86bd 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards db35fee8f6 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards e02cf5b6a5 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards e98433c259 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards f1226b1e0b 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards bdd8e82eff 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 8d73cb6c10 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards bdf66e48aa 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 43709a6d43 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 66e6ed057f 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 6ea18c4e11 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards abab2a34e4 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 3831295f99 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards d5c7129ffc 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 1c0d678b53 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards f41011dd23 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards c5a41b8c4c 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards a5b96de83a 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 1f0a1ca065 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards fab9ffa6a0 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 4a47c53363 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 0d145e2035 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards ad32bd0011 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 48f13a2495 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 702d49a0a0 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards e4868502cd 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards e0e776ebc9 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 12c4d31657 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 4c5f5f93ec 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards ea7f0f780c 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards bc9a7cd934 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 7eac67c17e 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 6687cc8d75 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 853cc30d7d 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards f9957f9dbd 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards fdf7b2c944 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 83385cfd51 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 93ff829810 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 84cb40823e 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 87a096c4a4 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 5d5a2ea797 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 37a57e938c 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 80b5215ded 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 58897fa6d9 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards d07a0343a6 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards d059746c2b 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 7a68f66647 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards e6b6937a0b 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 54f143fffb 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards f94f9a1ab2 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 3cda9abcc5 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards b45709bc58 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 4101ea38f9 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards dc1b764ee1 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards eaf3da2d32 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards a6f9892134 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards d8f34ff0f0 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards c06e61b0b0 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 25f776dbcd 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards e5520413d1 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards e1cdf564fa 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 5f8c0f4128 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards a0c349b424 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards a5220cee5e 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards f2326bf861 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 5425da1f0e 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 6d1110d474 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 012265c79d 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 012becb5ca 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 0fae75659a 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards cfdf888181 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 68c4d13002 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 4c132d5f77 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 68d881ea64 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards ff3741e38f 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 3405a19338 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards f8704c1f0d 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 465cc5919e 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 8aab6b6289 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 432552691c 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards fd5357a35f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 099193d5ad 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards de5a99844b 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 0f034136d1 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 2a1479e0db 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 004eb159aa 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards a38e19056b 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards a7f715be50 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards edac5765d8 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 9067c7955b 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards f8285c2808 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new f259694af4 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 7d0a4026ff 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 20de081720 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 2f9d507ce0 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 3f49102510 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new f9d8b44e15 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 37c0d1df6b 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 58bfd2fd89 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 1c96942871 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 0ee3929927 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new f913960630 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new a23b8cf755 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new d4dbdaac93 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 972c8a6360 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 77e92921de 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 113e1713b3 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new b837fdc5d7 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new f8688027fa 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 183c29b71f 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 82318a0d23 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new c6eb1f2cd9 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 75758ef441 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 07db004136 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new a18b0f12e0 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 088aaac256 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 10f500f5ec 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new cbc425d1e7 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 0adf08b840 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 944d4ce862 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new de7905b755 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 1cbee4869e 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 1ecab91260 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new b748a6f228 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new a8e89a3007 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 6f00583a29 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 11f687e066 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 8bcaf8f4cc 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new c7d6e15cfe 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 222ceddbcc 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new f9fc404b14 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new d5445ee412 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new f6f0b40cfc 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new f87d966800 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 6c41c2b41a 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 973c248a1f 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 0ce082d1fb 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new aad4f293f3 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new f9cee80d47 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new a4a5cf5fae 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 861dd2a20b 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 92c407233b 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 2f593773e2 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 377c9c221b 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 146084a584 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 2b2b8d0002 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 1861ab0553 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 72d52ed706 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 5545e466f5 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 909ca1c9b1 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new ff095c4117 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 0fd92fe0f5 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new d16b3f8e9b 294: onsuccess: #2110: 1: Success after gcc: 17 commits new d1725be785 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 18f323c997 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 7abacf219d 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 61062b9bac 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 139e408e40 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 5e6ac989a6 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new e77e9e6f2f 301: onsuccess: #2118: 1: Success after linux: 16 commits new 558d5c2c20 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 82e4a17b46 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 7a90aee219 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new d8891f65b0 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 6dfc78caf4 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 239b6f3a38 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 98a979ef72 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new c29cae786f 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 864c31cd02 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 970e944549 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 59e21ac51a 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 8db9a8ffba 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 4c1da77ff3 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 662d3f2365 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 32714eeb8b 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new d3ed75032c 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 74e98be1ef 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 763fbd0bb0 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 7322aec07e 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 7073f906d8 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 30120c4101 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 6d7c9702fe 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 87994d6379 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 3ba12416d2 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 20b75f9efc 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new c8353f1fdf 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 2778dad7f5 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new fee1d4d3aa 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new addccfa993 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 74ffc54ce0 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 98ae7d4307 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 393b0890d7 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new a9552352f1 334: onsuccess: #2154: 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 (735ed65148) \ 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 1808 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31912 -> 31740 bytes 04-build_abe-stage1/console.log.xz | Bin 91488 -> 91240 bytes 06-build_abe-linux/console.log.xz | Bin 8836 -> 8776 bytes 07-build_abe-glibc/console.log.xz | Bin 235652 -> 235836 bytes 08-build_abe-stage2/console.log.xz | Bin 228624 -> 228336 bytes 09-build_abe-gdb/console.log.xz | Bin 39484 -> 39268 bytes 10-build_abe-qemu/console.log.xz | Bin 31196 -> 31588 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3916 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2492 -> 2476 bytes 13-check_regression/console.log.xz | Bin 6192 -> 6168 bytes 13-check_regression/mail-body.txt | 35 - 13-check_regression/results.compare2 | 60 +- 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 | 37 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 2690552 -> 2688412 bytes sumfiles/g++.sum | 47 +- sumfiles/gcc.log.xz | Bin 2245440 -> 2246984 bytes sumfiles/gcc.sum | 1973 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 900076 -> 902152 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2268 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214076 -> 214060 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 444200 -> 439220 bytes sumfiles/libstdc++.sum | 10 +- 38 files changed, 1125 insertions(+), 1161 deletions(-)