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 646b053a7f 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards a0df453a28 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards cf169c4d93 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 54a9552afc 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards f91b3ed9a5 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 3cf9343ac5 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 2701deffa9 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 2797bc6a0a 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 38b8eb6e30 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards fdc1122c8a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards a27060051c 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 32c6cdd5ce 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 29747260a0 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards fee8bc0404 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards c545704baf 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards b587af8789 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 8ac10480e2 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards ab66d4fc4c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 70412d2f58 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 581380767a 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 203c59616d 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 7211769ed5 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 6c60470563 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 166bfaf983 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards c80c8e0ad7 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards edd523d8df 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 16383186a1 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 2bb7e27734 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 7eabd23d6a 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards c4efa65d26 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 20a507df4b 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 80d05d0858 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards f1f416a63a 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 7632ef6b9d 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards c621a39092 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 6a247e29bb 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards f803664b08 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 7d1a8d2b42 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards d289af6f89 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 8debdb7aa1 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 7263fb1d31 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 3b7e80d0bc 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 7d73d44051 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 705172a87c 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards b35ae24de8 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards c69258f14e 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards f33ab5f8e3 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 805e4adc90 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 0e99c48edf 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards be90f395dc 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 7cbe8b145b 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 77229854c5 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 462cee8d88 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 18e2eae8da 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards b54d0b3076 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 384ae5017c 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 953ebd29bd 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 7eae872dc0 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 6cb80736f3 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 870bf09e75 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards d6a3e2b114 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards a1814291c0 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards f0c9840d4e 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 3381d15874 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 4d98009521 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 293106e532 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 62ef65baf3 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards adaf79cd85 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards c9203cef6e 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 49b804f600 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 91cf370f18 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 5e04af9c87 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards c97fb8931a 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 66091e94f1 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards e8c9dd3341 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 2d76458302 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 525b09a193 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 26b2086fca 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 345dc5dba6 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards ac9eed1980 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards e0a78362ad 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 25dcfa8eb7 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards f48650a98d 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 212dfced0f 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 11de73abaa 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 91823cbd05 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 8d239093f3 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards ee952509ae 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 1d7e485765 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards d5dae12f5c 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards b1e37a2ea2 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards a81c4e7c61 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards d91462282c 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards bc8e609fe9 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards af88f90609 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards e1b4ed71d7 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards ed6e2971c7 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards e8c23d56f0 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 9b329fd0eb 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 161df35835 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 60e5bed64e 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new e8b33a1f90 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new cefa8ddd1f 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 6f07448658 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 3f707f7385 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 01080bb874 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new f9982b9c4d 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 96d84601f8 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 95ac7c0483 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new bd2c0abf9e 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new e830270b72 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new a8fc523fc7 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 52177740d8 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 7f3b3b4020 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new ccb70fc398 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 62b1d64034 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new e6402fb90f 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 566cd6ddab 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 1431c8a4fd 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 6afdcc296d 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 21ec6a9c7f 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 0ed8eaf04e 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new ed73d9c698 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new b6ed2a187b 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 1f434da895 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 7c86a854f8 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 59813fe789 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 58c5f9a607 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 57f78eb158 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 6b9b1890ea 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new a47d3ff5c5 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new dbe32509b5 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 555e52b030 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 158ea4a86d 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new d5f95a3985 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 6723929448 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 8da040aa78 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 6441c48d73 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new c13390586a 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 2eb7c56023 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 02848c1dc5 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 5fa206c888 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 519c6822f3 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 786e51ef9c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 474269801a 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 2f03a3296f 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 2189ec8002 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 5ac0b60a9f 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 0b0b470d36 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 6d22bcb86f 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 6d8a98bc4e 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 33a664c6ad 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new e66f63ee73 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 5193f1a616 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 24a2ff792c 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 7f697d67aa 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 30f5c244ed 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 770c1f5efc 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new ac4691a4ee 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 0211b7d030 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 234fa3c882 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new ff02c4a303 301: onsuccess: #2118: 1: Success after linux: 16 commits new a2780b4fc3 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 8e95001a83 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 7f1214cff2 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 9cc3adce5a 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new c454ab3588 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 9ba2c9f3b5 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 32749529fb 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new a39f50a361 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 1036498a9f 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 95e5091d66 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 4306eb3976 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 1962211de5 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new d4cdf146d0 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new b318dda81d 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 6ec5f0f8cc 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new d4770e882d 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 37b0ac18aa 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 026ab31667 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new cd1b460e84 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 7e4bd53340 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new d2d45aefdd 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 2c30e3dc63 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 9c893c28b8 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 67bcadc2c4 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 350082c777 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 601d1c1943 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 9a0719b996 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 3271690b8b 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new f6a62c895f 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new d89e2980a6 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 14f5bc69ee 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 22adbce366 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new c55887bd70 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new df6b79428e 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new a633e0c1fb 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new a68aab3d3f 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new c242bc8336 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new d21483c01c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 3ddfc806b3 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new bdcddcca28 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 7bc763ee21 342: onsuccess: #2162: 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 (646b053a7f) \ 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 1784 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 32080 -> 31636 bytes 04-build_abe-stage1/console.log.xz | Bin 91816 -> 91496 bytes 06-build_abe-linux/console.log.xz | Bin 8564 -> 9284 bytes 07-build_abe-glibc/console.log.xz | Bin 235956 -> 236100 bytes 08-build_abe-stage2/console.log.xz | Bin 228592 -> 227956 bytes 09-build_abe-gdb/console.log.xz | Bin 39524 -> 39388 bytes 10-build_abe-qemu/console.log.xz | Bin 31780 -> 31124 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2908 -> 2484 bytes 13-check_regression/console.log.xz | Bin 6020 -> 6952 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 34 +- 13-check_regression/results.compare2 | 96 +- 14-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- sumfiles/g++.log.xz | Bin 2690064 -> 2687528 bytes sumfiles/g++.sum | 32 +- sumfiles/gcc.log.xz | Bin 2243212 -> 2249912 bytes sumfiles/gcc.sum | 2202 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 899784 -> 896548 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214052 -> 214056 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 433140 -> 438696 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 1266 insertions(+), 1274 deletions(-)