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 ce9b73e98c 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 3771a18e08 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards ffebaee388 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards b4daae58f9 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 07e7aba994 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 6a6aa2c031 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 9998ad0509 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 30311bb512 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 4f0bef0d83 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 609ba57d87 124: onsuccess: #2159: 1: Success after linux: 23 commits discards d009d8031a 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 6b8403c53a 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards b584d7c053 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 0e0643a22f 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards fa4ae317c5 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards c716b734a3 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 8cfa5cf598 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 8ea386a8b3 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 3121157775 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 3c075114e2 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 7a4e195e7b 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards f78fdd8705 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 6eb45c43d5 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 812c73254f 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards d9e5c78f28 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 1b12028218 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 59ab2bf2d3 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards b648a4feeb 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 816014f239 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards bdd2fc6b69 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 6c59fe2d9a 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 3ae42609ca 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards b44ed66182 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards f548717b14 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 7a4c4b96f8 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 08eab8fea5 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 017f7fc98e 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 12dcce9a9e 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 8d99ceeb48 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 8bc5374335 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 998240cfec 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards db77d7532e 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 13ede4ae7b 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 4ae5542639 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 4be74f59f7 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards ecd931ac05 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards a56ab637a1 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards f07220f727 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 2159099173 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 8ba5c35487 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 13eb157509 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 03bdf6026a 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 90a10c1b83 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 2fa4877662 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e6e49e9bda 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7ca0251a7f 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 7f78ed4513 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 42a5610454 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3d919e0c15 75: onsuccess: 1: Successful build after linux: 44 commits discards cbd4d3ea82 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 1e9dcbec2a 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ac73a29917 72: onsuccess: 1: Successful build after linux: 12 commits discards 2042d64d2d 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 691f579b32 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards affdb1fc66 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 25aa81d421 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4e01b5d18d 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 5a696017a4 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards a4998a8e89 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9ee4c14333 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5c89bd6b01 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 4e972cc7b2 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 2c93cfd1e2 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 9e9e1b5a89 60: onsuccess: 1: Successful build after glibc: 2 commits discards 0275a67de8 59: onsuccess: 1: Successful build after binutils: 2 commits discards e1c23f0660 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 13fab07880 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7616c66a04 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards af99d60026 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards a0466e14fa 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards d9a42a9b0c 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 2d4eaf4a58 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards d41e778c4f 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2fa39a4e3c 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards bf50fc526b 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 6c378e1bfe 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2097b51b38 47: onsuccess: 1: Successful build after linux: 10 commits discards 77cf7c91b4 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 0d4a76da22 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 86a221063b 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 4bc8ad629d 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 9b97c1c982 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards 60ac70bc2f 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dc19d5e7dd 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 2e7521241a 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 6ebcd83a3e 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 01f375448e 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a6c77e15a2 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2a55f305b1 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ec2d5f9983 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f5facb71af 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a3a2275d0d 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 331f9d98fb 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c8d839f856 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 955c72c24f 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 008a14bf3d 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 5f054b0677 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new e080a425b2 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new f4eee7398d 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 870970feb8 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 659bb839bd 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 4278737ffe 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new aa490c7e66 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 0f8abda8d8 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b5763085fd 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new a9637a3355 47: onsuccess: 1: Successful build after linux: 10 commits new 29f0320d82 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fbbcabfc07 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 27717ef7a5 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 00e1a2b1b6 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 93bbc470ed 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 05cec26b25 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 43cc36fffe 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 7fbc2b1d6a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 134a43d14b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b271b4949d 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6cbda4b08c 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 767186a22c 59: onsuccess: 1: Successful build after binutils: 2 commits new 27f5278a0c 60: onsuccess: 1: Successful build after glibc: 2 commits new 04a3aa54c5 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 15563a043a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 78443c280e 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 249ac207ca 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0b3de7eaaf 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f33a1983c8 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 2400f04a7a 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 677225498f 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c27916147e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 1c85ca56ff 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new d62b893fee 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 4be6fb3c3e 72: onsuccess: 1: Successful build after linux: 12 commits new b3d2031113 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new da2a9275e3 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new c418f082e6 75: onsuccess: 1: Successful build after linux: 44 commits new 8e9c7f198c 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c7fe8b58bd 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new fe0b921d91 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new b177199811 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 5b7e25504b 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0c5be61cba 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 39f9768473 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new a47c5f900b 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 3df00a3067 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 53ee23727c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 7e9b76103c 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 67c8658c2a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 6e82955d0e 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new e4889a7ed9 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 518c69e1ff 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 2b10facb9e 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 05fd6b79e7 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 40659591fa 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 2e18269fde 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 52d93b6b63 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 92cd5e0383 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 96276ac2dd 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 1c24652da8 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new f0f622032b 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new fa5ef5d5c7 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 49b50c244a 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 4c63188ec7 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 91b11bc85a 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 597e95cf33 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 366639db6a 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 776fb4a356 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new b75c47bf41 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new eb0552d498 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 27800a0a32 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new daba6ed6cd 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new ae974a19a0 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 67a6660781 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 0da0e72176 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 592f3e1d42 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 7e7185c300 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 10c54e26b0 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 48e8883396 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 4a1e5d876f 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new e838430bf3 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 2a5074b672 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 916c1becf5 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new cb72e199c4 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 4415410e5e 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 3a8255b3bb 124: onsuccess: #2159: 1: Success after linux: 23 commits new f37f7721bd 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new c473861967 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 371c78a31f 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 11b6a4584c 128: onsuccess: #2163: 1: Success after linux: 23 commits new 812a4b96a4 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new ed2477e07a 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 04a6883dd0 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 198c48d635 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 5c831adb46 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 019da947cc 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...]
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 (ce9b73e98c) \ 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 1752 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30960 -> 30560 bytes 04-build_abe-stage1/console.log.xz | Bin 72892 -> 72556 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8756 -> 8768 bytes 07-build_abe-glibc/console.log.xz | Bin 239876 -> 239632 bytes 08-build_abe-stage2/console.log.xz | Bin 204656 -> 203016 bytes 09-build_abe-gdb/console.log.xz | Bin 38024 -> 37708 bytes 10-build_abe-qemu/console.log.xz | Bin 33136 -> 32420 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2464 -> 2712 bytes 13-check_regression/console.log.xz | Bin 184900 -> 19316 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 183 +- 13-check_regression/mail-body.txt | 224 +- 13-check_regression/results.compare | 380 +- 13-check_regression/results.compare2 | 46207 +++--------------------------- 13-check_regression/results.regressions | 139 +- 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 | 226 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 139 +- sumfiles/g++.log.xz | Bin 3412428 -> 3416060 bytes sumfiles/g++.sum | 3233 ++- sumfiles/gcc.log.xz | Bin 3032440 -> 3030340 bytes sumfiles/gcc.sum | 5300 ++-- sumfiles/gfortran.log.xz | Bin 1030084 -> 1031928 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2300 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202052 -> 201904 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422748 -> 423916 bytes sumfiles/libstdc++.sum | 133 +- 43 files changed, 8661 insertions(+), 47687 deletions(-)