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 2215e7f30b 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 2d06ee2311 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 00b5a297ae 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 83b8444a9b 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards d0f0ea2279 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 0fd7c8e4cd 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 4640c42d5b 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards a1873116c7 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 488c7164e9 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 34f6d3ceed 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards f53f625404 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 28f296f525 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards c9566ff76e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 0318f655ee 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 56da5b2424 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 057b30ba76 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards cb5b05b93b 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards dfa85ca827 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 41db5ca3ba 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 92beeec99c 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards afd72f6849 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 989a64da38 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards c7a803fbde 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 0fb72c13f7 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards e0211ec63b 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards e49f69bd77 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 804460c7a7 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 695f1e5ca3 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 76f7a2420a 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 5e5edfa25d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards ae140e38bd 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 9734bad17a 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards cf969cf480 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards dc7a58411c 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 7dff448db6 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 8b7a16c9f8 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 19aa25fadb 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards f6c395c20c 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 4a2a8017aa 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 76a9633b1c 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards e28b50f915 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 021b28098f 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 1f8a394fcd 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards ba3540a46f 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards cd91565b42 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards bad8bc65ca 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards a0933cf32e 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 193b53cea9 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards b4dec405d7 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards bd672fd8eb 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 07b72a3121 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 2aab5aa631 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 670abe78f7 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards eb10c166e8 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 3cb40ffd40 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 787fa0bb2f 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 5e023ffd5f 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 0ab04b094f 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 05c29611ad 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 44cbb6f96a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards e4d501029d 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards f9deeebfde 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 6505f81338 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 499e525f55 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 735409b1c0 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 393f1385a3 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards bbb617d110 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b8548e5629 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a325b28438 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 1091bd92c2 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 0f218c61ae 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 088c8d79eb 75: onsuccess: 1: Successful build after linux: 44 commits discards f6031352a9 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards b070241808 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 195c2dc6bf 72: onsuccess: 1: Successful build after linux: 12 commits discards 26559f8df7 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards a6ce167a72 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards ae485b8a65 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards aa8b0bcf5c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6b8d5f5fcb 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 65b9da04d6 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 65f4bb13b3 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4e30d63fcc 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0481103e1f 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 3adcfae811 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 856e9bd614 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards a7f482a89a 60: onsuccess: 1: Successful build after glibc: 2 commits discards a4bb5182b1 59: onsuccess: 1: Successful build after binutils: 2 commits discards 465b185a13 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 85ecac66dd 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2bb14a88c9 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ca110a7e51 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 2624f828fa 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 038acc2abe 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards c477254496 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards b6edb5a4c3 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 83c3e83347 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e14194f051 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards cb99b1e51b 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5960da2622 47: onsuccess: 1: Successful build after linux: 10 commits discards a695757ec4 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new d936a1519f 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 1e41ad3a7c 47: onsuccess: 1: Successful build after linux: 10 commits new 4f46e7c92a 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 396fc25fe0 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new fb46dd8c5b 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 29936f5577 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 38b4fc658d 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 64dc3e6604 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new f38c61597d 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 3a13b8af64 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 82b372510d 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9674e3be45 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 092675cd0c 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 4dacd0e9ed 59: onsuccess: 1: Successful build after binutils: 2 commits new ae60a3b388 60: onsuccess: 1: Successful build after glibc: 2 commits new b397735a56 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 1928758873 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 24e6b575a1 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 79f0bbb01c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2b5c6ae328 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d60357b5bc 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new ad47832abc 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new d66b3527ee 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 59b4c34b68 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 8e73372571 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new a633428eef 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 196748fd59 72: onsuccess: 1: Successful build after linux: 12 commits new 2ba2318087 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8a6c5af2c4 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 837039dd4b 75: onsuccess: 1: Successful build after linux: 44 commits new 5fccc6273e 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4d880fb0d6 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 53f7a8f759 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 0c0ea98c57 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c8576eb0e3 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e3b48ffa8a 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new b3903f5630 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new c41cae3cee 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 8814dcd848 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 61a7a2352c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new e774deda17 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 92b7f9389d 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 89428385dd 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 03e1dfd5f2 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 47c5d68fa6 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new d10e56dce8 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 8a91809c87 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 8485818fb4 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new d110a81ee0 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new cde2ddd682 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 458719e7e9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new c1a357c909 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 77a2b5f611 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new d6edde32f7 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 8db9aeee4d 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new e713e65776 101: onsuccess: #2130: 1: Success after binutils: 81 commits new b8548eb734 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new b968632727 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 35cf817ba2 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 319ca2de33 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new fd4f21fc0a 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 950e67d434 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new b4b0d15d47 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 6f81a6eebe 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 77dc245715 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 473950ccb1 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new ce9e9c52ff 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 4c4c8d2dd5 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 7cea956e61 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 32c4367c2d 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 8ac00b69a4 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 6af5ac97f4 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 9290b4abbe 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 07b99e482d 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new d55a0a6ff5 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 7f20c13ec9 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 5e0d6f6679 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 66212a6088 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new a4fd3915b9 124: onsuccess: #2159: 1: Success after linux: 23 commits new db97e25cb0 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 0276aefe3b 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 491cab4ee4 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 585db4d589 128: onsuccess: #2163: 1: Success after linux: 23 commits new b523553c90 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 10af6eea4f 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 37f2911991 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 1ef66303ef 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 702d6d42a5 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 4c97fe176a 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 76461ef814 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 4daec7bed9 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new aa0f4e7174 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 902b7e4b15 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new aac120d405 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new a7aa5d9bb5 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 509845db3c 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 3a69ee4c22 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 417b1bc9f3 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 44851faeab 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 32d2e1f1de 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 7c8f98333a 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 13c1c1f7b9 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...]

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 (2215e7f30b) \ 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 1700 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30304 -> 30532 bytes 04-build_abe-stage1/console.log.xz | Bin 72600 -> 72336 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8484 -> 8496 bytes 07-build_abe-glibc/console.log.xz | Bin 239776 -> 240032 bytes 08-build_abe-stage2/console.log.xz | Bin 203040 -> 203140 bytes 09-build_abe-gdb/console.log.xz | Bin 37412 -> 37644 bytes 10-build_abe-qemu/console.log.xz | Bin 31900 -> 31980 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3928 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2808 -> 2712 bytes 13-check_regression/console.log.xz | Bin 8132 -> 6644 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 134 +- 13-check_regression/results.compare | 84 +- 13-check_regression/results.compare2 | 435 +-- 13-check_regression/results.regressions | 87 - 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 136 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 87 - sumfiles/g++.log.xz | Bin 3408532 -> 3434876 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 3029088 -> 3002148 bytes sumfiles/gcc.sum | 4494 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1028292 -> 1026064 bytes sumfiles/gfortran.sum | 50 +- sumfiles/libatomic.log.xz | Bin 2300 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202120 -> 202196 bytes sumfiles/libgomp.sum | 59 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 428316 -> 425152 bytes sumfiles/libstdc++.sum | 14 +- 43 files changed, 2579 insertions(+), 3268 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions