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 ca61c02b45 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 716e75cfe3 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 4a5f7126a3 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 098c778525 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards c1c9e285a3 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 6ff51d2f77 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 3d3d6ad826 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards dd2518f5f9 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 776c75ef77 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards ce45154710 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 863e5c781a 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards d8bae3f689 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards af8166c7d5 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 072bb16431 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 5dcfcdc07e 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 57a86c5120 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 34c525236c 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 139b987915 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 104d0201e7 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards db63b028b7 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 19fde11b1a 124: onsuccess: #2159: 1: Success after linux: 23 commits discards dacf19a3c3 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 4f791791b7 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 889a2782ef 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 3a36c6c046 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards de494da3aa 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 9353fd2f1c 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 1d05e93568 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 6698a29ca8 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 0aab5795a1 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 40ce0eb38a 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards b29cab3f3b 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards cc71706965 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 333549c8e3 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 732109ff19 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 0572a129ac 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 1147a614ed 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards df0a126fbd 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards e8dbe7945c 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 329ac8f71e 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards e7101e1f17 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 7c8abf8148 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 0ed4e327ce 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 56200baf9a 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 7429d6df35 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards ed58ee5769 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 82c202a2f2 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards b8ece9096a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 8b0d4129a9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 4924a09012 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards bc7fb63495 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards c97fbaadcd 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards d35d9af008 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 23e74b3960 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards c44754c976 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 720824ce7b 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards dfb04e6904 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 3699c9ad8b 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards b99ae2b216 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards d6e8ec44b0 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 4dcb0ee794 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 7324229d23 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 49a8ec890d 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 4e7908b3dd 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards a65a0159e7 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cce1c8d871 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 013ac56063 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards d22e298b04 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards e73bd2505d 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ae4a06046b 75: onsuccess: 1: Successful build after linux: 44 commits discards 37c4d2042d 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 011ba2bf59 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 81f8ea66b9 72: onsuccess: 1: Successful build after linux: 12 commits discards 834dc23130 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 42c40d7b79 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 28d74518b4 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 8811920845 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 75337e0acc 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 0a60a8b8c4 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 17ff15c2e2 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 92b2d448a6 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c8e9e63db1 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 802563cbad 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 823a585d85 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 82b15dd902 60: onsuccess: 1: Successful build after glibc: 2 commits discards ef01651b3e 59: onsuccess: 1: Successful build after binutils: 2 commits discards 075b818817 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 7db3f0324b 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2447fe8794 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 633b3506cd 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards ec9b5c2ef3 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 0dd6c6a1e4 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 84c7016f0c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 9cff3a5581 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a578111d8c 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards df07fe6b22 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 5f56201ca0 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e4c56ea6b4 47: onsuccess: 1: Successful build after linux: 10 commits discards b794509600 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 7d1aa79ddb 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4c8e64bfeb 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 6a3aecdc0b 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new b3b34b6601 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8cd2a5c101 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 9a46de5cb9 47: onsuccess: 1: Successful build after linux: 10 commits new a7954c698e 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 866a8a9e4b 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new a96bbf4538 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 540dd0d969 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 74d6dfc93b 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new c1c2961d04 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 3b72d5e8f2 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new a02e4b37cc 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 9e629da782 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 750b7d20db 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 408a03c40b 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new e08e809406 59: onsuccess: 1: Successful build after binutils: 2 commits new ee141547be 60: onsuccess: 1: Successful build after glibc: 2 commits new 17775cfbad 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 88bc304076 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new b9def31c05 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new d62e56a854 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 08155e106c 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d439142b2e 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 1b68c19ffa 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new cfa25305ab 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 75d33ee957 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new a2de583ccf 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 84494f2f72 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new bb29e2732e 72: onsuccess: 1: Successful build after linux: 12 commits new 5148cc9cfc 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8ed00318f2 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 7dc0771d39 75: onsuccess: 1: Successful build after linux: 44 commits new 0c08bef861 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0e87defb6d 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 3f5ea8ccf3 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 70e87cb461 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d1cc036524 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 137da7954d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 2e19f43b5e 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 2077b478bd 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 785deca647 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 1f5ee70afe 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 593d153e9b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 89cea660f7 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 5d39123d1d 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 8665cdc360 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new da3f10b913 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new cba44c13f4 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 04cb8b2b6a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 6e41d0dbc8 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 43bfd02c40 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 89d38dcad3 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new e6c47c7bf6 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new f9a032c510 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 1654b1d68b 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 51e592e2f1 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new dc320e504a 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new cf6413bf20 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 878127e2d0 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new ddd8788c48 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new ba073081f2 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new c4d2350b3c 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 39acccc973 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 0d19cdf1f2 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new cd45df225a 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new e595e5ffd4 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new b05dfc05d3 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new e3e912cf3f 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 4a2e9decc2 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 5181a21259 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 53f41d8e41 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 0156404bc9 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new f9dbedf1c8 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 986702590c 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new a905f9eb34 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 0f9cbcfe65 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 69935ab006 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 0e44afa5ae 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 4348a3c025 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 901d3006af 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 7484b3c9c7 124: onsuccess: #2159: 1: Success after linux: 23 commits new 9059c2b63b 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new b36a3219e6 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 5f9a3b9946 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 1cedef2da6 128: onsuccess: #2163: 1: Success after linux: 23 commits new 3cc39e45d8 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new dc2d559315 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 1f106314c6 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new c60979b242 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 8fbb5b9f96 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 64a71d5d96 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 8beaa9ac8c 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 3d99b06d8a 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 505b00255f 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 16b9b0c344 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 99f1bb7fec 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 5431a7d60f 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new e7d681620f 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new dc2283d773 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 5dfe1e8c9d 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 787481397c 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 3943ef17c3 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...]

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 (ca61c02b45) \ 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 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30200 -> 30300 bytes 04-build_abe-stage1/console.log.xz | Bin 72464 -> 72300 bytes 06-build_abe-linux/console.log.xz | Bin 9288 -> 8472 bytes 07-build_abe-glibc/console.log.xz | Bin 240172 -> 239608 bytes 08-build_abe-stage2/console.log.xz | Bin 202948 -> 202884 bytes 09-build_abe-gdb/console.log.xz | Bin 37528 -> 37496 bytes 10-build_abe-qemu/console.log.xz | Bin 31820 -> 31904 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2660 -> 2784 bytes 13-check_regression/console.log.xz | Bin 7032 -> 8936 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 52 +- 13-check_regression/mail-body.txt | 175 +- 13-check_regression/results.compare | 77 +- 13-check_regression/results.compare2 | 488 +++- 13-check_regression/results.regressions | 77 +- 14-update_baseline/console.log | 54 +- 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 | 177 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 77 +- sumfiles/g++.log.xz | Bin 3413944 -> 3439504 bytes sumfiles/g++.sum | 94 +- sumfiles/gcc.log.xz | Bin 3024756 -> 3011328 bytes sumfiles/gcc.sum | 4797 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1028436 -> 1035292 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202196 -> 202308 bytes sumfiles/libgomp.sum | 12 +- sumfiles/libitm.log.xz | Bin 2660 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 424008 -> 425728 bytes sumfiles/libstdc++.sum | 2 +- 43 files changed, 3399 insertions(+), 2745 deletions(-)