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 8e447a7299 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 359e07f04c 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards f3889e6c6a 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 01f7ed8501 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 38e5e782d4 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 09de92b125 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards eb769092ce 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 5262f91347 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards c0cb5b3d71 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards fd3a641a54 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 08c5e5d941 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards e56c637dc4 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 80bc929ad4 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 70b31e330e 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 0468ba3fa1 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards cad0b98c2c 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards a2712c8874 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 4c19130205 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 044f06534a 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards e2f2dc4c59 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 28205b888d 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 6d624561f7 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 7e6eb0b0c2 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 3c88b2ad91 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards e375f8884f 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards fad8433bb6 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 521e4feee6 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards becf514fe0 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards f5941e2288 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards d0f9544b43 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards bc1d2aed99 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 4173b81873 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 91ccfc60d8 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 4f22ce2dbe 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 61970d7b85 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 4d1c830bf9 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards e3d83e7f79 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 511d68d144 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 937e328789 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 0102079085 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards a7aac1131f 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 6f64c9328e 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 409f091ac8 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 659aeb6287 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 25d9ef12d5 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 6e269021b2 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 7bdb46bcf4 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 79a5d106e3 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 4d75c283ef 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 95c1c2deca 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 7694e0a089 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 7083fec66c 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards b98fe41836 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 01a19568d1 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 892a6802ad 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 9da0478741 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards a02622b496 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards ec8c544acf 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards e8c9b2873a 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 691826c286 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 3f229dfdcc 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards cbe2e8d0a5 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 09d01eb8ed 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards bcadfb2593 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 6d479963bc 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards b8b0ded3e0 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 152690ed85 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 3cfbca7091 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 53cf2c11ff 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 75fc71480f 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards e45867b804 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards bd515ee2d9 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 52d7a97b1d 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards e161b3eff4 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 64e30b28a5 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards c5f6761f73 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 3093d5c122 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 0687ddfdff 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards bfeccbdf70 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards bd82ea059c 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards ad71d234f5 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards cf3b02e4c6 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 1c3fd78c3e 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards f16f8c0344 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards d3cccd4bc9 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 0e0d5f2159 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards f375f42012 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 3d57750ef9 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 054b2836fd 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 8ecddf6b94 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 87a1f30d82 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards a65462e458 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 1944b575ff 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 5a5a422eb7 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 6ddafa64b5 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 19cd24fc07 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 104a31d2a6 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards e2b1f7aa75 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards df9b7610ee 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 0fbf9f8e25 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards a742b86c3a 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 491c892665 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 2be0047a4b 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new b7c436ffd6 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new deec8aba51 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 6c56fb6a58 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 93288efad1 231: onsuccess: #2047: 1: Success after gcc: 4 commits new afd89847f9 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 4c9a2e469b 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 98d436669f 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new eb653621ea 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new e6b76749eb 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new aaa1109b07 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new a1ff373d09 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 1fd5478a6f 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 0789d25a7d 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new eec6a4eb79 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new b9367b764e 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new f759329cf9 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 5229f7ece5 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 1057602b9f 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 96638408c6 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new db6f856594 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 02c834d192 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 151fd5a701 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new b43e6f57d9 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 6e2f28426b 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 48e82347a8 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 38c3f0be0f 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 27070e8c30 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 74ab68369b 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new cf5c5e0871 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 26652e7fa5 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 2f449c667a 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 59ecdccff3 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 111de3c310 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new cdd43a30da 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 435f8b0b15 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 2c144b2f72 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 62163893f0 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new c79c6578e9 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 68f7b2a428 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 22370251b1 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new dc7e9e2abe 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new c1d3152538 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 2aae54cb37 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 3096843590 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new b2dc0ea528 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new caaf55c7ee 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new c48ddffbfb 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new bd57928028 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 8b0ee36ba3 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new a84fb90836 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new a501f8aed9 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 7c5621e0ac 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new a62f5d3c73 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new fdedc291c3 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 04678670ea 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 8478a892df 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 994185771e 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new db486ac397 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new dbc0e529ea 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 483d3aa347 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 5173c9cc0a 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new e868ba18d2 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new fe98d65f1d 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 3952330c57 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new ad3c56ba53 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 61ff9dfd54 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new bdb32c7a28 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 40f46f5ee9 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 655edf6e28 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new eeea2e1054 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 9a667303d0 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 54c7453bae 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 5371fafd1f 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 4e5d4b0545 301: onsuccess: #2118: 1: Success after linux: 16 commits new 58dbc6bb12 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 596507b6ca 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new ed540afcd3 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new c9c8538175 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new ce988183c9 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 6b93147339 307: onsuccess: #2124: 1: Success after gcc: 2 commits new ac847043dd 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 6f9381758b 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 4a626fdf67 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 695dd949de 311: onsuccess: #2130: 1: Success after gcc: 4 commits new ae94290bee 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 8d7dff8bf9 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new f593f8223a 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 3ced79c627 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new f8ec0e3f45 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 6a6052a2d6 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 27ce58616a 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 3212c1e449 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 31b241e2c8 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new e757937714 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new e6b25e802c 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new fe2ce1fc28 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 6861a9fdfd 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 19bde315a4 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new aaef5dd56c 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new a169ffd4db 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...]
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 (8e447a7299) \ 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 1800 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 31868 -> 32216 bytes 04-build_abe-stage1/console.log.xz | Bin 92164 -> 93080 bytes 06-build_abe-linux/console.log.xz | Bin 9096 -> 9112 bytes 07-build_abe-glibc/console.log.xz | Bin 237060 -> 237804 bytes 08-build_abe-stage2/console.log.xz | Bin 228700 -> 230732 bytes 09-build_abe-gdb/console.log.xz | Bin 39472 -> 39448 bytes 10-build_abe-qemu/console.log.xz | Bin 31668 -> 31492 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3916 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2536 -> 3316 bytes 13-check_regression/console.log.xz | Bin 7068 -> 5216 bytes 13-check_regression/mail-body.txt | 47 - 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 34 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 49 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- sumfiles/g++.log.xz | Bin 2665048 -> 2659084 bytes sumfiles/g++.sum | 34 +- sumfiles/gcc.log.xz | Bin 2258928 -> 2280920 bytes sumfiles/gcc.sum | 2408 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 893980 -> 893364 bytes sumfiles/gfortran.sum | 12 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214008 -> 214020 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 430056 -> 430296 bytes sumfiles/libstdc++.sum | 6 +- 36 files changed, 1309 insertions(+), 1415 deletions(-)