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 565c1665b5 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards fbe323866f 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards fa2c343581 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 6a02f5be01 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 85f9f9540f 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 88d50cac5e 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 20a8d15349 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards bcd9d973c5 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards b9587c45cb 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards bf17506bd6 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 65a0bb5ff7 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards a05f8863a6 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards f0639057af 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 9a4d9c400c 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 2d82445700 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards fad873106a 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards b6a6b0ec04 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards a201cb4792 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards fa07fddada 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 98f60bfc37 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards eba9dea928 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 36114d6146 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 4fcaa36007 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards f072a91ca2 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards b136ae038b 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards a968d64489 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 144b8339f7 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards a566afaf17 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 46831be7a4 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 2e10e75358 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 9e97b7da93 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 3e42c5b138 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards d007b8f42c 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 51060b5545 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 96e2fdaf94 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 264a2dc7f1 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 14b343806c 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards ea1fb208e0 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards e02c1fcf1f 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 38673073d6 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 074d84578e 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 0a3d839eb4 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 3ce6129bd3 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards ceda12a531 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards d94531648b 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 5d9183f64f 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 4a92ee4df4 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 5ace509c76 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 1af22f6258 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 31610e33ae 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards c69c620a86 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 7a9fb447de 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 3d402be068 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards cde5b2eb62 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards a7f4cd342c 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards 1b54401175 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 25e5dfe251 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards e80d6c342e 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards 82a1eff8dc 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 934b312ab3 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards 3645ebcebf 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 093a59e86d 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 6d6f73a61a 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 266edc3741 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards 895bc9bb95 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards 8264936576 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards d233299d86 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 3a9269cf57 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 98a4b53b04 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards f305398cc6 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards 88d968deed 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards deb905273e 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 40e5462978 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards fce9a416b2 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 966e664259 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 1413cda999 208: onsuccess: #2012: 1: Success after linux: 12 commits discards bf8c930ac0 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards afaeb5ba85 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 281935ae4a 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 613fa804d9 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards cd9e561d1d 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards 7605c312b4 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards 4efbbd5876 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 7d542fb453 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards 759a8c3b05 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 2e5cd970d9 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards 0d3c7d8bd3 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards d3f75cbbb0 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards f911e85d4c 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] discards 4c6cc836e3 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 9bff6b6e89 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 9eb6dc529e 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards b354ee3667 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards ecfe764190 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards d538d57fcb 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards 8e7eb7746a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards 7fc8e9ba5d 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards 275bc34d18 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards 856f2ce46a 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards 894c740f72 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards 2a0a63b828 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new 314597b9dc 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new c8a86c2987 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new 60c516af1e 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new b79527f11d 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new d7f483a516 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new 40a4eeaef3 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new cd83946ed0 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 2ed2830cf1 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new efc5d6a30d 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new 3124530e81 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new 4d4bde8a4b 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 94de40bc34 194: onsuccess: #1995: 1: Success after linux: 517 commits new c85812df9f 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new da9e233dbe 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new 766b08dd7a 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new 12760da982 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new 3297af2383 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 9674ea4e70 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new d846bbd924 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 0747a22a91 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new f575455786 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new 58a7767506 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new 2545e55847 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 9e432a2e17 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 588387b8b4 207: onsuccess: #2010: 1: Success after gcc: 4 commits new a759ea4202 208: onsuccess: #2012: 1: Success after linux: 12 commits new e233bd72d0 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 217383894d 210: onsuccess: #2017: 1: Success after binutils: 6 commits new b1605d4223 211: onsuccess: #2020: 1: Success after binutils: 10 commits new a1e0410cf6 212: onsuccess: #2022: 1: Success after linux: 3 commits new 30cd462a1c 213: onsuccess: #2024: 1: Success after binutils: 3 commits new be6fbf98a2 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new e9ab052cd6 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 1e6ac94904 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 943ea929c4 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 418da06a6e 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 6ccdd0b694 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 161cb27617 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 252b333fca 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 01f31c6586 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new ef3f224471 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 998beaba08 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 7767f14e07 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new a104e8bae2 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new ee7d790ba8 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new ad05d098dc 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 81f958cf20 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new c33c9ea20d 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 03794d7c9e 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 88b8d815a5 232: onsuccess: #2048: 1: Success after glibc: 2 commits new cf2517fad4 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new ccf448c383 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 2868b7d8f1 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new acc4646d09 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 24086bfcc9 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 6b24c4dbe5 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 2313721b8b 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new b95d16396e 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 0ece8b2457 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 41161d7788 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 1a92c8bb03 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new fda3c5ff05 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 38c0da9c81 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 9fc99ab2d0 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 3ec00c6d2b 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new e92b17d349 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 758befbebc 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new ec9bfa91fc 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 481471cd30 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new e17c35a3e3 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new c589c34af8 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new fdaef89a98 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 5d23787d5c 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 05d6a3aa7d 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 9bb209db3a 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 8f7c84cd9c 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 48be718c4c 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 0a5ca6eea5 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 29f860f3c9 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 2d16bbd2b9 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new fd260c0f19 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 3b01a0bd26 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 550b1c5dc9 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 6613a12742 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 1168cc8469 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new cd1a73ce12 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 49ec9a05de 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new d4b24f46af 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 69123cb836 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new aabeac0840 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 0d12e2481c 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new d395b5c7d3 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 8a26f46bde 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new d1540712b5 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 06e777059d 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 3e763dc2ff 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new fe654b4cca 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 3f45f8bce4 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 4c6b97b790 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new f2ef485c93 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 1122b2f6ee 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 736332735e 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...]

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 (565c1665b5) \ 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 1740 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 32008 -> 31976 bytes 04-build_abe-stage1/console.log.xz | Bin 92376 -> 91956 bytes 06-build_abe-linux/console.log.xz | Bin 8368 -> 8372 bytes 07-build_abe-glibc/console.log.xz | Bin 237128 -> 237096 bytes 08-build_abe-stage2/console.log.xz | Bin 228488 -> 228948 bytes 09-build_abe-gdb/console.log.xz | Bin 39440 -> 39504 bytes 10-build_abe-qemu/console.log.xz | Bin 31732 -> 31052 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2764 -> 2780 bytes 13-check_regression/console.log.xz | Bin 5360 -> 7160 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 7 + 13-check_regression/mail-body.txt | 53 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 416 +++- .../results.regressions | 60 +- 14-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 55 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +- results | 27 + sumfiles/g++.log.xz | Bin 2661404 -> 2694612 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2243132 -> 2242872 bytes sumfiles/gcc.sum | 2602 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 893956 -> 896196 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214012 -> 214128 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439764 -> 436452 bytes sumfiles/libstdc++.sum | 10 +- 40 files changed, 1857 insertions(+), 1487 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy mail/mail-body.txt => 13-check_regression/results.regressions (73%)