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 c35cc15b20 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards c7538d910b 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards e8311a3ec0 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 8ab71a261b 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 78703d9740 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 7759dcb0c9 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 031839291b 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 4530614ec2 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards a5b14d371d 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards aff16be23b 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 7f900610b0 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 9726f9a014 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 2adccd1078 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards b78cf4a738 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards a2c40ac4d9 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 152c212981 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards ec414bfc39 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 1a3ebc79e6 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 78e91f8967 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 73d7fb7f9a 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 93e775593f 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 5a8a3325c9 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards dd381f1625 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 597d64a8eb 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 24cbfe85f0 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 120522f05d 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards e5772d0ed5 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 2bf9043a39 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 5a1c9f8811 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 33167e90e2 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards b340d7a5dc 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 2d6d4dca7b 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards d052c5097b 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 8028a4ec73 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 2fad372832 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 5c73c5412b 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 2a7b457b66 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 88939709f2 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 33421cca3a 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards af580faf98 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 3369064c9e 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards e2379cea2d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards cdb41c6d3b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 56cede9be1 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards b1e17dd95b 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 697476793a 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 570baeab4d 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 056c4fe799 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 23f84bd53a 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 3d4672b077 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards d56c8679ad 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 0b5a6156e1 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards d667f7eda2 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 9f40db46d9 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 82893b4990 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards b22c0a1748 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 22040e0ad3 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 0bb5dcfff0 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 45b4b65d96 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 8655a1d182 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards d89fc07ff5 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards da40980d29 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards b71b1f9b31 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 190ad4c543 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards bed7a44ad1 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 8570f008c7 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards f417380eda 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards da5150d578 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 43a9b3abaa 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 8bfe1b8ac1 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 91c2a1a308 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 583a4a8ba9 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 2bdb65dffd 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards acd34a2ae1 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards d591cdb604 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards b846efe34b 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 0de6207565 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards dd19879f03 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 7b472821be 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cddb4f5876 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 35cb604304 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards fbbb8771b2 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 81eb8ac777 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0f18d76ba2 75: onsuccess: 1: Successful build after linux: 44 commits discards b6e87396eb 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 3b1528e8c3 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cfca240c9b 72: onsuccess: 1: Successful build after linux: 12 commits discards 82a178929b 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 37c611caf0 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 72908ea2aa 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 704cd78419 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6c6e21565b 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 59a70e06c7 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards d1c7888800 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 545557c993 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8137990564 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 6f8f9aef33 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards f806dddc6e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 922dbe485d 60: onsuccess: 1: Successful build after glibc: 2 commits discards 43be9af63a 59: onsuccess: 1: Successful build after binutils: 2 commits discards dc8c273257 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 90ae6acad8 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 7b8f669eaa 59: onsuccess: 1: Successful build after binutils: 2 commits new 675f97e534 60: onsuccess: 1: Successful build after glibc: 2 commits new 3142a40d54 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new bf2925370d 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 5899bab328 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2e99462a63 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b64b30f4d1 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fbea46aa8c 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new f95524e6ba 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 3d448d927b 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bc90c52b35 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 62a4e10738 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 96bb138431 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 675efe72f0 72: onsuccess: 1: Successful build after linux: 12 commits new ee940f8622 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 60feca2c93 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 6b72fc1cc0 75: onsuccess: 1: Successful build after linux: 44 commits new 164af65360 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 01da9aef73 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 9c88c99695 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 727136c1a7 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f98ec8fccf 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e7164407d9 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 78b0a8f5bf 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new df8c1dc455 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 86da1ddb82 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 5e4dc41c33 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new b22e17d052 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new e74ebfd8ff 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 10da006e17 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new fb76125b2a 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new bb2447ebee 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 3ca5d9d2a4 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 61366ff4ba 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 970f6b86a2 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 3e634fa7b6 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 92e31a2b23 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new d29ca06609 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 4779e1f92e 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 7da93f894b 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new aedabb6962 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new efd2e83613 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 89ada51989 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 3481e74437 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 288cb5afff 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new ff6f237cb5 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new b4e73db701 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 76ed6b2745 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 6960278239 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 4fe74b905d 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 49a6ff53c3 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 96c5d93e5e 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new b2f72a2feb 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new de60a76b55 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new ac14ecfb69 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 889d89b913 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new eb2e0f0179 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new b379d8b2a4 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 6c1ea28f9a 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 28f8c45e6e 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 1ae8adf3bf 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 7501fbdbc2 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 4fbe51f9fe 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 8925abdd27 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 61d5346415 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 49aa61d42a 124: onsuccess: #2159: 1: Success after linux: 23 commits new af2276f202 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 66fd71c7cd 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 7120ba08e3 127: onsuccess: #2162: 1: Success after gcc: 9 commits new effae8b933 128: onsuccess: #2163: 1: Success after linux: 23 commits new 030dd8a2c1 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 73e49ab27d 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 7a8a975792 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new ae2171249d 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new a5f90d45de 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new a3f8679c85 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 4215d03b75 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new d691aab4b6 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 74fd027e19 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 5f4ca8f840 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new a609d1e5ea 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 30a4c23095 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new ea876c33ef 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 7f85a7f810 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 20a6826f40 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 3169f2d122 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 1165ab4ccb 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new cdadf66d1c 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 743dff53fb 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 4ce861809b 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 57d3c57e1a 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new e1992da2cb 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 20b610b3d6 151: onsuccess: #2186: 1: Success after gcc: 2 commits new ccda88a674 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new fb919fb611 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 85309f090b 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 2cd73a75a2 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 681d017576 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 7d314c6d0a 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 7822c964a3 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new bdf612ab1e 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...]

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 (c35cc15b20) \ 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 1704 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30812 -> 30728 bytes 04-build_abe-stage1/console.log.xz | Bin 74324 -> 72256 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8304 -> 9172 bytes 07-build_abe-glibc/console.log.xz | Bin 239864 -> 239064 bytes 08-build_abe-stage2/console.log.xz | Bin 204752 -> 201828 bytes 09-build_abe-gdb/console.log.xz | Bin 37812 -> 37732 bytes 10-build_abe-qemu/console.log.xz | Bin 32016 -> 32356 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3948 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 4808 -> 2552 bytes 13-check_regression/console.log.xz | Bin 9908 -> 17812 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 69 +- 13-check_regression/mail-body.txt | 143 +- 13-check_regression/results.compare | 88 +- 13-check_regression/results.compare2 | 2855 ++++++++++++++-- 13-check_regression/results.regressions | 108 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 145 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 108 +- sumfiles/g++.log.xz | Bin 3410948 -> 3406988 bytes sumfiles/g++.sum | 2640 ++++++++------- sumfiles/gcc.log.xz | Bin 3030496 -> 3032252 bytes sumfiles/gcc.sum | 5518 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1032208 -> 1033776 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202264 -> 202360 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 421400 -> 424540 bytes sumfiles/libstdc++.sum | 16 +- 43 files changed, 7340 insertions(+), 4533 deletions(-)