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-aarch64 in repository toolchain/ci/base-artifacts.

discards 0c1215e0f 124: onsuccess: #2159: 1: Success after linux: 23 commits discards d8f254ac9 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-283 [...] discards da677ec66 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 72757b2d9 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/gd [...] discards 177ad65a9 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/gl [...] discards 5cf1cfe97 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/gl [...] discards 8ae910c26 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/gl [...] discards 87bb79695 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/gd [...] discards f1ff3038e 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 89d08d985 115: onsuccess: #2147: 1: Success after binutils/linux/glibc/ [...] discards 77b5261ce 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] discards b928d77d3 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] discards ba903996b 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] discards cf13b9283 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] discards 96166ce21 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] discards bb058e26c 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 3838aa8cb 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 3aba82c26 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 0fa75ee2a 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] discards 67209d9c9 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] discards 634cc047e 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 3d2c714f2 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] discards d51a1351c 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] discards 07f64af26 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 4b14774de 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards 1d9598773 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards 75f8bae4d 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 0612b6d22 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards afbc3c61d 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 79e165bdc 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards ebb099345 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards 9d60f41ce 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 80bae3d08 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 645a84d9e 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards aec36b943 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 21c36ae94 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards ed5faae3a 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 20e0f4cc4 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards dc79cf066 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards c67cf23b0 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards ae8d1bf78 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 76702d26d 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 5674c1e55 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 24cc46038 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards 29c8c9c49 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 6f8447146 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 16eb850ff 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards dcefbbee4 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards b8604be9d 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5d6494328 75: onsuccess: 1: Successful build after linux: 44 commits discards 8adfe20fc 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards ed484e724 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ec19161b1 72: onsuccess: 1: Successful build after linux: 12 commits discards 442c4905c 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards eebd049f6 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards c8a06c1f0 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 844e00506 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1d9f68206 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards ad11fc55c 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 9bdea3693 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards da44e1b5f 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e72dd2e6a 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 7e5ba51ab 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards 8ac1e2269 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 0212b8b2f 60: onsuccess: 1: Successful build after glibc: 2 commits discards 4d2cec1b9 59: onsuccess: 1: Successful build after binutils: 2 commits discards 8f7f70567 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards 07ff7f137 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 4b8359d46 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2bffd99cd 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] discards 8912f3015 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 34c677ad4 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 2eabc7b6a 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits discards 21509d309 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ca4641821 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 8199cd556 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards a4e97b03e 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d0581367b 47: onsuccess: 1: Successful build after linux: 10 commits discards ac7e6dea0 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 211541b3e 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9dd2ec038 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards f3c679d33 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards c1c3c4abd 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] discards 4c72d8311 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7dd858925 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 287e5748e 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 4d7b024a5 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards d0ae9cf60 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 33cb99a8a 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 69da4d3ff 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 97cfbb65c 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 93d0fa331 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 30d9fac59 32: onsuccess: 1: Successful build after gcc: 7 commits discards b83149e80 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 3cdc9af63 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards b86f564f5 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f49a14f25 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 6ed11cbef 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] discards 3ea8cbbbd 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 09317bb49 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 83a020280 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 370ed753e 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b268ed675 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 17033be1f 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 069c10806 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] new ee8fd854c 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 053222461 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 4fe2f2f4d 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new bc4124512 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new abed66615 32: onsuccess: 1: Successful build after gcc: 7 commits new d1e01f391 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 6031d0993 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 7957fae7a 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 42d27cc6d 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 639e335cc 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 9345cc3d1 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new e2247072c 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 4d61bc61c 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new cbe282539 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 53ac2935c 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] new 689c3e572 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new d13644725 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 7916d41dd 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 447aebf2f 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new a41a39c40 47: onsuccess: 1: Successful build after linux: 10 commits new 2c170665b 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 95970ced2 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new dd3e26440 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 422945859 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 1c69824fc 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits new 38bc67f4b 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 035ac8cdc 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new b4b946179 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new d3d0985a9 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 4b7138bb9 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new a8feedc7f 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new d408a8f0d 59: onsuccess: 1: Successful build after binutils: 2 commits new 552670697 60: onsuccess: 1: Successful build after glibc: 2 commits new 1b72a80e8 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 2c0bd44ba 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new 6047bf6f1 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 7040effe9 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new dd25daa6a 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a4ab6d6b3 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 8d673d8c4 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new 88595acd3 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new eaedf2248 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new f885c6c37 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 5cb0e9ec5 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new a22617283 72: onsuccess: 1: Successful build after linux: 12 commits new b9a8e4360 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ce4fcadf3 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new dbf21dff7 75: onsuccess: 1: Successful build after linux: 44 commits new f017ad3e3 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b0703aaae 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new 1372019d4 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new ce117ef13 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 663576ef2 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 242bbac42 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new 5720c3145 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new a1c8cbb47 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new d2ccb1c0e 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 71a7614d4 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new aac0539fc 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new c7b2a455b 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new c4baadd7b 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new fc97cd764 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new d0e64cf2e 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 50d9b7f46 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new e41f6081f 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 10dbc8027 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new bdcbf6066 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new eec0268d2 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new 4ec56644d 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new e0ed65dec 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 5ed5f20bc 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new e16e99fd8 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new e3039a618 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new 74811c323 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 113ea1e2c 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] new 819df42ca 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] new a33321d67 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 5e2b7e822 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] new dad85823b 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] new 230a7cae0 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new acb121d70 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new eb9a7317e 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 42c546951 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] new 589628633 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] new dfe7732a8 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] new da9fd314b 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] new ffb4412d3 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] new 8a659a872 115: onsuccess: #2147: 1: Success after binutils/linux/glibc/ [...] new 76ff89c8d 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 39842d531 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/gd [...] new 0c8bc4a05 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/gl [...] new 2b4281f17 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/gl [...] new 4b05c9322 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/gl [...] new c8ec99db8 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/gd [...] new b2a81e80b 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new cebf7285b 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-283 [...] new fff0f9787 124: onsuccess: #2159: 1: Success after linux: 23 commits new a3a1e4eef 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/gd [...]

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 (0c1215e0f) \ 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 1760 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30548 -> 30208 bytes 04-build_abe-stage1/console.log.xz | Bin 72764 -> 72188 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8728 -> 8696 bytes 07-build_abe-glibc/console.log.xz | Bin 240044 -> 240300 bytes 08-build_abe-stage2/console.log.xz | Bin 203300 -> 202972 bytes 09-build_abe-gdb/console.log.xz | Bin 37920 -> 37340 bytes 10-build_abe-qemu/console.log.xz | Bin 31612 -> 31412 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3932 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2916 -> 2452 bytes 13-check_regression/console.log.xz | Bin 5508 -> 6172 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 36 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 26 + sumfiles/g++.log.xz | Bin 3405196 -> 3435088 bytes sumfiles/g++.sum | 198 +- sumfiles/gcc.log.xz | Bin 3032656 -> 3013276 bytes sumfiles/gcc.sum | 4558 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1034192 -> 1024616 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202076 -> 202012 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 420428 -> 421072 bytes sumfiles/libstdc++.sum | 20 +- 44 files changed, 2643 insertions(+), 2475 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