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 d2af2300b9 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards d9689b4df0 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards ad37874270 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards ea5655170d 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 4759287cb6 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 0ac2d47757 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards e58c949086 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 885e5b583c 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 61d38317e6 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 61503dd564 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 17af442099 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 63f4afe067 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 49032695de 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards a2e14b45ad 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 011c44806c 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 7e702dde8f 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 4bdadc3599 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards c4cbe8a834 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 2c65045d5a 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 8086e241eb 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards a5f3d713c6 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards d7cf7f88ab 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards a9c522ac24 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 515344e8d6 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards b4f7628a1c 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 4e64c16b6f 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 459f6bcd37 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 926d8da3c7 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 8043676df1 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 0e05f26b88 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 29988e4709 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards f6d139a856 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 87d4a58a7e 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 99acdd4aa1 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 0cc8f54383 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 12750ce55d 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 01cc6b251a 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards dc463b52bb 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards fb743198df 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 813d8dddb0 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 6c420f06e5 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards d99fcad603 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards f12fb4e739 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 663672e62d 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards b228c582ee 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 4d0bc7817c 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards a5dfd13d94 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 016c3a47b4 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 6c6088d3bd 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 1d8ce0a3ff 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards b92501dc1b 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 95c49c99ed 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 32c99d5549 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 8d61c4194d 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 9c7d5bf4f8 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 4ff81a5e23 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 5c6b6cf638 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards fc2d246ae1 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards b47d8624be 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards f167ddae4d 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards c29d7771ec 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards d9d8ef67b2 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 244b4372c5 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 8fc422a50f 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards fc0fa394f0 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards dc1c006308 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards d1b2698921 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards f4c2d492a5 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 126ccd6c8e 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 6f33725853 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 563bc18200 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards fa438f6558 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards b9dde6f783 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 6ca22821f1 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards d86d5cb746 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 421f5e8601 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 009d3ff63d 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards f442986044 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 7f1053ce7c 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards f9118fedf4 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 055c1c5230 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards de9aff29a9 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards d8f269cf71 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 872760a893 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards db29e75af5 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards e60620911b 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 786e6311d1 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards c02fa49ff1 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards c922ab6342 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards ed7f6b873d 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 8bb496f9d4 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards 0fad523480 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards fff2f535a7 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 241e17c68e 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards e7377aa828 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 2a9be61acf 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 4330b35357 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards cf7aec8fa2 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 48e4cf0a4d 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 115b979f32 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 0ed5a003e8 210: onsuccess: #2017: 1: Success after binutils: 6 commits new bdd5489faf 210: onsuccess: #2017: 1: Success after binutils: 6 commits new f4cd5c9478 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 16806b08dd 212: onsuccess: #2022: 1: Success after linux: 3 commits new b312323b4d 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 80a822e187 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 2f98910994 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 9c03f53970 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 4981e62201 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 075ea9436b 218: onsuccess: #2030: 1: Success after gcc: 5 commits new bfa8b252ca 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 5b93da4d90 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 60cf1e5a20 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 5a848e289e 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new c13910d7d1 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new af57efb88a 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 031389108b 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 7b4748412d 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new f9d714dadd 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new 92bd72a377 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 88bc01b6bb 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 5ef1973493 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 2d3c1e6095 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 23c374cda7 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 66b245a546 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new fe854bcc5b 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 2c5bb2731c 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 901509e930 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 0b13ef00cb 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 10b2e790fa 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 09c9a7c65a 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 0e81ed30b1 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new c3f7b6c312 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new f5e4017f17 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new f18fa2faa5 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new cec66a5fa9 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new e427943c84 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 3050aa2e9b 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new cdc149eabd 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new d25872a817 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new f537a67ae1 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 56a97af1c3 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 8e4e5af85b 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 91028aedd0 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new b4898f7dcf 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new c283456d69 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new a18f79a50c 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 7f2e3c2487 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 6abffeee71 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 98c3caff98 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 12ccaaf379 259: onsuccess: #2075: 1: Success after glibc: 2 commits new c925ae44cc 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new d06779e1d5 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 2bc9a492e6 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new dae507ad8a 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 9af06a1d3a 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 18593b8707 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 9ba92af981 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 7dabc7d088 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 5fa8217914 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 94b4f27b0b 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 301cb8e764 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new fc2bf04ab7 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new a285568bc5 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 0faffef850 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 4d5bfdd80b 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new b92b8bc82b 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 11ed1ecf2c 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 335a991f4d 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 37157bd55d 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new a918310324 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 5d84a2e446 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new b3009fba0a 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new e794e95764 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new bc84eb3009 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new a6728705f3 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 4c287705a0 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new dd1358d8dc 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 3faf7475e3 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 6e97a0dc83 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new faa89f69df 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new aa515aa65f 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 4a8f400dd9 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new c2aaf7e4e4 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 76ad8e3000 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 97ed43fb8a 294: onsuccess: #2110: 1: Success after gcc: 17 commits new d7c9a28aee 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new d5d782bc33 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 9ac33afa0a 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 019b93c050 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new b1a6d4de4d 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 9d8a32bee9 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new fd70c97f04 301: onsuccess: #2118: 1: Success after linux: 16 commits new 96a8308c61 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 7799e1c34f 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new d4714a82a9 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new bf70268323 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 610d3aa043 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 8695b061c3 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 509865764c 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 17e089e0c5 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 3fb0f542a3 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 78e2ddb4cd 311: onsuccess: #2130: 1: Success after gcc: 4 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 (d2af2300b9) \ 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 1732 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 31900 -> 31836 bytes 04-build_abe-stage1/console.log.xz | Bin 92212 -> 92092 bytes 06-build_abe-linux/console.log.xz | Bin 8512 -> 8532 bytes 07-build_abe-glibc/console.log.xz | Bin 236500 -> 236396 bytes 08-build_abe-stage2/console.log.xz | Bin 227940 -> 228328 bytes 09-build_abe-gdb/console.log.xz | Bin 39680 -> 39732 bytes 10-build_abe-qemu/console.log.xz | Bin 31276 -> 31664 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3044 -> 3220 bytes 13-check_regression/console.log.xz | Bin 5216 -> 5260 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 7 + 13-check_regression/mail-body.txt | 27 + 13-check_regression/results.compare | 10 +- 13-check_regression/results.compare2 | 35 +- 13-check_regression/results.regressions | 27 + 14-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- results | 27 + sumfiles/g++.log.xz | Bin 2672752 -> 2659548 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 2229088 -> 2261008 bytes sumfiles/gcc.sum | 2168 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 888380 -> 895148 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214020 -> 214156 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2672 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 433344 -> 434392 bytes sumfiles/libstdc++.sum | 10 +- 40 files changed, 1277 insertions(+), 1166 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions