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 eefb55bb74 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards f19a219703 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 4305dd3696 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards d4b1ec6bda 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 0f612ae57c 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 4d38e2c6f3 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards c2ff99e71d 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards c3d5470468 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards e1307159c6 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 9bb46d6b75 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 6efd6c7abe 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 5429679aa1 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 7cebd212f2 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 7d130b9927 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 6ab80acb08 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards adae995ee9 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 90b25752f5 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 9fa59de056 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 1c73f2f232 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards fdf9f6706f 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 55dd4b47d2 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards fe7b19a6ac 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 072475a712 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards cabbaaf35f 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 75efffd385 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 6aca9a452e 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards f8b80f610d 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 36ef57ebad 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 5782970074 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 5bcd1d36c7 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 5255509b40 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards e8db473db9 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards da761c82ae 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards aef5ae7961 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards b5910c5afa 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 09966b60d3 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 27e5463822 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 7a7e6fadac 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards f112e1c1e3 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 2a5fd14855 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards bcae2826f5 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards f3710d2082 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards db5a6fe0a7 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 0fb266bb28 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards c0c964424a 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards c8c13c828f 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards c671b47f9f 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 0e671adff8 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 9eb94b3e3c 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards f8b6cfc8b6 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards b58db66fe6 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 882f9e7f9e 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards ad15732959 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards e0fa9aeb8d 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards c7ef222da1 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 09ea5b61cd 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards ded1a92c29 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 6d20d87016 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 45bfe6e9d9 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 011fbe3d42 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 7110e5e18e 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards d63b7fa1b0 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 4e0a8cf5c2 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 8b7e512f08 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 4a772219be 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 4c31b370db 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards be9d755fa7 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards eea19aff23 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards eb5854c1b2 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards c8d14b0b06 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 54e0df4f9e 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards b0c4ef1dcb 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards a84892e30d 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards a98847b772 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 0b700a8fee 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 8f95568e6b 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 65279cc36a 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 93925a7492 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 20533f61bb 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 00f3445083 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 3d654f013a 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 6042261b83 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 6b80c73e39 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 86b7c1eb7b 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 993edb028c 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 034a6eee4b 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 4b9371f2cf 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 24de462ef3 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 2221eeff99 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 663628c632 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 3cee528728 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 6eaecf47c9 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 2002f45642 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 62e3aac06d 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 8707760c49 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 875d4830f0 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 0a2ab7ca53 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards b896d0d54a 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards e7646de6ad 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards cceaa0b6dc 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 088d415ac0 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new c5a112f2f9 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 32d3e8683e 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 2a4c297260 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 73a54029f1 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 286ef8a40e 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 301a84dea0 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 0282e260e3 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 1c06135100 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new b779424afe 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new af502ac991 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new dee4c6f864 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new deddad9d60 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new b4651d9950 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new ef397a8b06 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new cb26f28255 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new fdc8fb6412 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 334a2dcfca 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 6f7bb77ddd 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new e491f05296 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 41a79fb908 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new c10f2b887f 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 06776b4847 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 94a18a94e6 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new b7bf699875 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 976a5ff5f4 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new ca19f004b3 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new d3975cb25f 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 46de7e5625 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 25df02b800 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 31c813f950 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 94a1a7f073 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new cd10a40f57 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new a9b9d729fc 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 05ed6a6578 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new c089e00c9b 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 71f23016f6 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new e61906e6c4 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new edc39a85f9 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new faab4337ff 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 7fbb54afaa 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 2b6692ce8f 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new ff1b304ab1 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 7ef91c8099 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 36e0fe9f08 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new b01d2bd424 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new cc1c23f90f 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 1514478d77 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 2853154f81 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new f32744e2c9 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new cefff32f10 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 2d9285d874 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new e3d49828e9 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 0c341d0329 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new b781e80a16 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 61a5bc2d06 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new bdf33f2733 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 705873095c 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 4f13cb9798 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 550f407d8d 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 4738706f9d 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new b609e7e23a 290: onsuccess: #2106: 1: Success after gcc: 2 commits new a33ee69481 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 17ece19a44 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 4fcc9f7592 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new b57681061c 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 2c91695907 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 9d30d68bde 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new dad2571b0b 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new ba47694c0b 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 28991e877b 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new b2bf52f1f1 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 6101ae3bbe 301: onsuccess: #2118: 1: Success after linux: 16 commits new 65ca58b370 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new c96c26c932 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 2cbfe395b1 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new f9ab1a930d 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new f5c7aa780e 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new c0f66dc6fb 307: onsuccess: #2124: 1: Success after gcc: 2 commits new feaf7d8958 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 09e50f9f20 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 87b8261676 310: onsuccess: #2129: 1: Success after binutils: 4 commits new d0dd2c6bae 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 3c07404450 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 2c8a2e69f1 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 29759c9b82 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new ba3fcf3fa3 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new fe4835c6bd 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 9f87cdaf2f 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 942334c4c3 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 48ff6547fd 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 4a0ea75684 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new d656f03902 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new a84ccbdf63 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 82858a858d 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 09aaf27060 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new cb7ada5f6d 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 9b9e17f8c4 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 9b979e700c 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 8b973b0ed3 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new f0c30da4b6 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 7d5280a92c 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new cf67a15c72 331: onsuccess: #2151: 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 (eefb55bb74) \ 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 1764 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31772 -> 31900 bytes 04-build_abe-stage1/console.log.xz | Bin 92776 -> 91520 bytes 06-build_abe-linux/console.log.xz | Bin 8420 -> 8848 bytes 07-build_abe-glibc/console.log.xz | Bin 237328 -> 236140 bytes 08-build_abe-stage2/console.log.xz | Bin 228528 -> 227356 bytes 09-build_abe-gdb/console.log.xz | Bin 39604 -> 39308 bytes 10-build_abe-qemu/console.log.xz | Bin 31196 -> 31064 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2516 -> 2496 bytes 13-check_regression/console.log.xz | Bin 5808 -> 5668 bytes 13-check_regression/results.compare | 12 +- 13-check_regression/results.compare2 | 20 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 2664336 -> 2687580 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 2277292 -> 2257788 bytes sumfiles/gcc.sum | 2424 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 899920 -> 895788 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213948 -> 213976 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 440792 -> 435780 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 1301 insertions(+), 1309 deletions(-)