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 dcf5658e28f9 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards febac8759620 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 27ce5776a03d 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards 04c242880981 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards 781376baff9a 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 4020745159dc 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards 3da8d17dec44 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards 7b8168b0cd39 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards 7f639cdb371e 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards f162822aae55 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards 4e2dee2c579c 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards 78a2ba414027 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards b97cc3dbc1aa 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards 60b7c4d518c9 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards 5ec05c0d1daf 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards 710a8c13e29a 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards 298f4847faee 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards bc80da2e762d 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards 262c330b3362 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards e9e9571d025f 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards 78cf9d505909 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards 0507f889671d 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 0e1139234b5f 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards cbdc28f27a79 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards 49392e00875e 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards 2826b0d99638 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards 080e60c14d81 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards 7bd6260db639 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards ba8943ef2fe1 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards 51fee33944c9 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards c1d057c6bc9f 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards 2a33fa61725d 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards b8b0e5dafd7e 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 5aa37b3ae15a 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards fa1b148d270b 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards 895ad9a90ebc 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 7aa20fd80267 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 743174f7cf1a 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards 0c88804be871 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards 748a54491e62 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards 8bec4ba18d93 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 2b0e838e13cd 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 016fae10e818 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 185a65fcb2a5 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 7fdc696b4a51 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 9596a9e6fa2c 208: onsuccess: #2012: 1: Success after linux: 12 commits discards db9b19fed4a0 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 8a484e746ab1 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 73a74fd83ff2 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 3f6862b9c732 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards 2b33ef6fff4a 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards 150c3888f763 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards 8215fef5e7aa 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 2cc63c740301 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards 5ff8c86a0c3c 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards ed52fb2c4875 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards 9d8473b46862 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards 7a67d7143a8b 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards d78d6cbc4a0b 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards bcc0bb771a77 194: onsuccess: #1995: 1: Success after linux: 517 commits discards a3f6ee86dabf 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 2483afd4d0bf 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards c712b46b4db1 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards f4e8928ccef2 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 21276550072f 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards 888146eb438a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards 9c2b985458ff 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards e26a19959d47 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards fb319bdd598e 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards c845c0099ada 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards 543ca4f78032 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards 2d2a99aa1b16 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards f0d025a63bd3 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards ba8e662d2273 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 26fdd5fff464 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards ace8f0c0ab98 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards 8c08414840ce 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards 8d2a84410afb 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards d249fc4c145b 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards b5f75b47ac38 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards 3ea09f035a7d 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards 3e1ea3e53654 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards 824443d1fe66 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards 716becf2f3b0 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards b682642e0f2e 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 69e957a4fa50 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards ed40133b2fe2 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards 33974e92b21e 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards 6bc5062a60a3 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards a240176bcdca 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards 15e2b147a636 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 6a4d46a935d4 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] discards 1e766bd2642a 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] discards 0f81ce12a626 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] discards 678d8b9459cc 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] discards 77f603456480 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] discards 208afc47f418 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] discards 330cbf76158c 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards bacf771f2814 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc [...] discards f29004dbcd84 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 6c65e9a723cd 153: onsuccess: #1754: 1: Success after gcc: 2 commits new b58282736ce7 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 2c239248b1e2 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new d6fd331e47a2 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc [...] new 04b4aef3ddf5 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 0d28e622e146 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] new b4aebfac1eed 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] new ab5b8913c74d 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] new e8ececdab702 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] new f4e98a656dc4 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] new 6bdde449b5e1 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new 8fe0d5119671 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 6008ddbeaeee 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new d2dcb7c32b71 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new 17279a8e4fe8 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new 3f905b7a2b8e 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new 191078908178 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new 1720c08edb7a 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new 6d661f6575f9 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new 03ffa447eb4e 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new 48ed51670070 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new ee454b5dcb15 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new 262afb9393d4 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new 24e9423fb294 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new a49e95c8fc7f 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new 5221df41f95b 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new 91e41451ad6e 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 7afb32c0d417 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new eef56e1a59e0 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new 8e0f0d5cfba7 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new 2f2fb7fdf2d6 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new a9dad2577d6f 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new badc310383a5 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new c943dc4e986d 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new 97d8c49766eb 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new ee243dff2c09 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new f80658e6d6c7 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 2c30cdc57b8c 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new 4c4b73d3b859 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new 0375a80b1cb4 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new b6970b507021 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new b4e43e6ab05f 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 324e7a5c6e8a 194: onsuccess: #1995: 1: Success after linux: 517 commits new 6f8008938eb0 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new 04792caca8f9 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new a72d15fb4f2f 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new a0cb6ca26ba3 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new 7ec465be41f7 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 2f92baa63bf3 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new f8c4304cb2e2 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 0ed5450dceaa 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new 6b4c91b46d46 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new b066c1f1d8fc 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new 509c701acc71 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 150b79713175 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 2e5946785826 207: onsuccess: #2010: 1: Success after gcc: 4 commits new f0f94c5b8ffa 208: onsuccess: #2012: 1: Success after linux: 12 commits new 9fae6161d046 209: onsuccess: #2014: 1: Success after binutils: 12 commits new ee8cda9636d7 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 938b5ade6d31 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 3cdd7127f081 212: onsuccess: #2022: 1: Success after linux: 3 commits new d5d3dce433fa 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 74f5d8245a37 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new f6e4e798881c 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 806904a73680 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new b2eccc331121 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new 25b91dd81676 218: onsuccess: #2030: 1: Success after gcc: 5 commits new e9f0231daa0c 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new 710a7e8ba7f0 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new 4f160da579ab 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new dbce49caa73e 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new 291ecf63102a 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new c340dbd5323a 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new 1cf22a7720d2 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new a8c374c5d695 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new 9ed44aee82ce 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new eddee0477684 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new f81902565df3 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new 82096e68740b 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new 43ed2a445f7e 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 2a0d1c323b5b 232: onsuccess: #2048: 1: Success after glibc: 2 commits new dcb2399a7619 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new 7d798bf40529 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new 68ea60206077 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new fd64b7bcb324 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new 4730a8d5c32e 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new bc93d7d63cdd 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new 9505f1fe111e 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new 5fa715192293 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new 7bff5e067fb0 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new d233ba726f51 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 74b76193d977 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new 8a9e7663a437 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new 0ad7c30035ef 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new 6ffdc3001efb 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new 831fb92d0807 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new ce23c28598eb 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new 4801cfd96956 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new 16ff98c2ee33 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new 78536669889b 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new 690b372a9b04 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 4c8b3d82ac8f 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 389be4e5fdc7 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...]

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 (dcf5658e28f9) \ 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 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 32500 -> 31940 bytes 04-build_abe-stage1/console.log.xz | Bin 92416 -> 91996 bytes 06-build_abe-linux/console.log.xz | Bin 8640 -> 8668 bytes 07-build_abe-glibc/console.log.xz | Bin 235908 -> 236460 bytes 08-build_abe-stage2/console.log.xz | Bin 226696 -> 227764 bytes 09-build_abe-gdb/console.log.xz | Bin 39608 -> 39056 bytes 10-build_abe-qemu/console.log.xz | Bin 31632 -> 31388 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3108 -> 2512 bytes 13-check_regression/console.log.xz | Bin 5800 -> 5868 bytes 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 59 +- 14-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_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 2658392 -> 2692756 bytes sumfiles/g++.sum | 4 +- sumfiles/gcc.log.xz | Bin 2246692 -> 2246300 bytes sumfiles/gcc.sum | 2312 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 915388 -> 897972 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214012 -> 213964 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2672 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 440516 -> 443384 bytes sumfiles/libstdc++.sum | 8 +- 38 files changed, 1251 insertions(+), 1278 deletions(-)