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 c7187a55c9 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 5292200bda 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 1636f678af 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 420af044cc 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 0c5445c5ad 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 58240ae879 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 5750a97984 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 4b11263e3e 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 7773ab3bd7 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards ad8412fb79 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 5e1f8f1bbc 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards d88dfd560c 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 2a0be7c3ed 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 921ccb386d 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards cf82e3b2e4 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 8f9c8fd12a 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards aae9b5ed8b 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 829a976460 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 61f6b274d8 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 2f17805214 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards c69be627ed 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards c8fb31040f 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards acd928cf9b 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 1427032605 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards f024e5f666 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 9057682f47 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards fbf7978c93 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 85a2ed520c 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 8b7691b4d8 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards c0f9186071 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 19f222bf60 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 0f345d3f0e 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 2d8383cfd4 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards ad4d782023 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 9e3e14bb34 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards ffe5b6c005 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 311b8acebd 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards f3ea1559e8 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 798214bf96 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards d3f7d63b17 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 1282600116 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards fc369b6fca 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 5669fbc4b4 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards ea7d26b3c5 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 3366808bda 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 1f15bcac38 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 2101e8550d 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards d98d560ce9 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards a80253b276 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 4d5e99084d 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards fdd78a3d96 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards a5abf35abb 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards a99b400e1f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 17f1cb35c0 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 0f8918a9c8 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards f4439fadde 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 866b51e2fc 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards bab108e7ec 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards edb6cb6b57 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 5383f56b46 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 21d7e5477d 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 00bbed839d 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards c2a4dc636b 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 70fa8caba1 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 9b2ec62a96 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards fac97877f2 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 455229b3b3 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards 55aa67feb8 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 33ceb801f7 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 533e88acd6 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards 3969d59b46 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 0ca65098af 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards a4489d85d7 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 6bf6c08107 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 08b92779f0 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 2397f6f5aa 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards 3daf30a8a2 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards 5c6e30f23b 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 7d58d891e5 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 21df161ab6 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards ee6182bd7d 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 2409a3dd9c 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards 3627fb1a32 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 01a2bb7e4c 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 54d1e474b1 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 58db2fbd74 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 878ce6b057 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards f23e349643 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 8775f7bd7d 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 0c43993594 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards db50a244fd 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards eee1c30b2a 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards bb4e64789e 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards 435f3c3f6d 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards 9cdd7aeae5 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards fee9a018d4 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards 399c88c6fb 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards e11dcccd4b 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards 8f452caaaf 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards 82c26988e1 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards fe0ece29d2 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new 3c04281a1a 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new 30d5a06f6e 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new 3e094d7083 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new bbf0989bc8 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new f822bffaea 199: onsuccess: #2000: 1: Success after gcc: 5 commits new b40be70a78 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new 8b748d1bd3 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 60af1ec950 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new fabd7b44b4 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new 22f14bdcaf 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new 7dc863a353 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 980a98c9b9 206: onsuccess: #2007: 1: Success after gcc: 2 commits new e9b8053f29 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 22dfad6bf1 208: onsuccess: #2012: 1: Success after linux: 12 commits new ed4fd0204c 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 934d3e06ce 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 007b2180e9 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 490e9dfb86 212: onsuccess: #2022: 1: Success after linux: 3 commits new b23bb85185 213: onsuccess: #2024: 1: Success after binutils: 3 commits new a0e626d782 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 60e2e898f7 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 39aafb65c5 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new b5265fb350 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 45b1dd2ad8 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 0b656b74b9 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 005b68faf8 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 4bb6776fb9 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 563ead932d 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new da168d2335 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new b7c76f8ce9 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new eb39951e26 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new b944766563 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 019a3027fe 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new c46182308b 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 9e9b83d528 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 9c696f641d 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new d2d784ebaf 231: onsuccess: #2047: 1: Success after gcc: 4 commits new aa19d60b6f 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 7ac38471a6 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new d7943fbdf5 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 46ffed4c75 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new fe066a4b56 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new fb24ed3ca7 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 54ef50d73a 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 5e05ab1e24 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 60cb7ec3d1 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 27b0c61ba1 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new f496a81c39 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new b9066a494b 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 74141bf4e0 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 3fb7d0507c 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 4b2ab07b57 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new a5309b2237 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 25503933fe 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 5e94bb3777 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 5488c671bb 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 9a5648f13f 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 2069cb305a 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 18ce260883 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new c3b7cbffc2 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new abdad8e814 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new c6fe9aac53 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new c69b794c5f 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 69242ed0c0 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 0d83e35265 259: onsuccess: #2075: 1: Success after glibc: 2 commits new a5d8bad8c3 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 7412a6319f 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 4a7f039bf5 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 3171914a05 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 1b6bc9c4f1 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new f6230089f8 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 28f16971df 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 9aa4163b42 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 31442170dc 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new b074b9f01f 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 1d49ac0e0d 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 4e1bf52313 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 79a97b57e8 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 90b5b4fcc1 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new d435ff305c 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 1ccd03d9f3 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new b8caf49254 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 97ffd84405 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 02db615817 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new f431909dc2 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new ccbb162927 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 16cdb91f0d 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 6c9acfe8cd 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 4442732eed 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new ffa6e1235e 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new b04fca9bc9 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 15fc5059b8 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 63cc03724f 287: onsuccess: #2103: 1: Success after gcc: 9 commits new ca426d366d 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 823e0c7711 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new f2040184cb 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 922866259b 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new b3500ce306 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new c0d9ebf088 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 0c0acf4be7 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 9e991b76f5 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new aa3d7068fc 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits
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 (c7187a55c9) \ 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 1728 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31752 -> 31836 bytes 04-build_abe-stage1/console.log.xz | Bin 91560 -> 91712 bytes 06-build_abe-linux/console.log.xz | Bin 9276 -> 9240 bytes 07-build_abe-glibc/console.log.xz | Bin 236420 -> 236852 bytes 08-build_abe-stage2/console.log.xz | Bin 227952 -> 228396 bytes 09-build_abe-gdb/console.log.xz | Bin 39160 -> 39068 bytes 10-build_abe-qemu/console.log.xz | Bin 31068 -> 31116 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2488 -> 2716 bytes 13-check_regression/console.log.xz | Bin 6380 -> 5868 bytes 13-check_regression/fails.sum | 3 +- 13-check_regression/mail-body.txt | 53 +- 13-check_regression/results.compare | 22 +- 13-check_regression/results.compare2 | 26 +- 13-check_regression/results.regressions | 22 +- 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 55 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 22 +- sumfiles/g++.log.xz | Bin 2658940 -> 2673288 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 2228672 -> 2228856 bytes sumfiles/gcc.sum | 2214 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 893204 -> 905436 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214072 -> 214168 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439748 -> 433348 bytes sumfiles/libstdc++.sum | 12 +- 40 files changed, 1294 insertions(+), 1263 deletions(-)