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 bdf612ab1e 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 7822c964a3 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 7d314c6d0a 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 681d017576 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 2cd73a75a2 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 85309f090b 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards fb919fb611 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards ccda88a674 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 20b610b3d6 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards e1992da2cb 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 57d3c57e1a 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 4ce861809b 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 743dff53fb 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards cdadf66d1c 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 1165ab4ccb 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 3169f2d122 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 20a6826f40 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 7f85a7f810 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards ea876c33ef 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 30a4c23095 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards a609d1e5ea 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 5f4ca8f840 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 74fd027e19 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards d691aab4b6 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 4215d03b75 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards a3f8679c85 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards a5f90d45de 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards ae2171249d 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 7a8a975792 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 73e49ab27d 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 030dd8a2c1 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards effae8b933 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 7120ba08e3 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 66fd71c7cd 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards af2276f202 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 49aa61d42a 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 61d5346415 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 8925abdd27 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 4fbe51f9fe 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 7501fbdbc2 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 1ae8adf3bf 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 28f8c45e6e 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 6c1ea28f9a 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards b379d8b2a4 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards eb2e0f0179 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 889d89b913 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards ac14ecfb69 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards de60a76b55 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards b2f72a2feb 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 96c5d93e5e 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 49a6ff53c3 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 4fe74b905d 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 6960278239 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 76ed6b2745 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards b4e73db701 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards ff6f237cb5 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 288cb5afff 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 3481e74437 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 89ada51989 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards efd2e83613 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards aedabb6962 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 7da93f894b 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 4779e1f92e 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards d29ca06609 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 92e31a2b23 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 3e634fa7b6 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 970f6b86a2 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 61366ff4ba 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3ca5d9d2a4 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards bb2447ebee 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards fb76125b2a 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 10da006e17 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards e74ebfd8ff 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards b22e17d052 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 5e4dc41c33 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 86da1ddb82 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards df8c1dc455 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 78b0a8f5bf 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards e7164407d9 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards f98ec8fccf 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 727136c1a7 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9c88c99695 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 01da9aef73 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 164af65360 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6b72fc1cc0 75: onsuccess: 1: Successful build after linux: 44 commits discards 60feca2c93 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards ee940f8622 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 675efe72f0 72: onsuccess: 1: Successful build after linux: 12 commits discards 96bb138431 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 62a4e10738 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards bc90c52b35 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 3d448d927b 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f95524e6ba 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards fbea46aa8c 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards b64b30f4d1 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2e99462a63 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5899bab328 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards bf2925370d 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 3142a40d54 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 675f97e534 60: onsuccess: 1: Successful build after glibc: 2 commits discards 7b8f669eaa 59: onsuccess: 1: Successful build after binutils: 2 commits new 3d2b739e1a 59: onsuccess: 1: Successful build after binutils: 2 commits new 37a8f6d7cd 60: onsuccess: 1: Successful build after glibc: 2 commits new 27be399276 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new eed9ab1673 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new a819207dfc 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 97be036919 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f276fc61f0 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 398de58161 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 06a2f3db43 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new e508011355 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 348273cff9 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new de2707e5f1 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new be5513f361 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new cc37705cd3 72: onsuccess: 1: Successful build after linux: 12 commits new 8c13f87155 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4c90bcec29 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 816673056e 75: onsuccess: 1: Successful build after linux: 44 commits new 0e1651feaf 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a2859fa0f7 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new d2eae8b86f 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 8c1c2e1610 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9706a65791 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 622c670e5d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 4689f1ce5b 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 79fedd0efa 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 981cdfd2d0 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 89a6a009de 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new d442ea2c59 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new aa832e433f 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 4a7c87f2a2 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new a8365efa7d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 55e3a19a54 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 3962e00529 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new b57f3e2bd3 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 70cc0bb7fa 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new f487a792c8 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 6d998cba59 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new f20f278116 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 7600bff5cd 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 3a0bac66e2 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 2d50f7734d 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new da8db58a06 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new b6f80185fd 101: onsuccess: #2130: 1: Success after binutils: 81 commits new c0b47de672 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new f58f41871b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 65d5b4a91b 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 39e2cb6ccd 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 0279553308 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 238bd162e7 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 3fd9b52003 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new a779b9688e 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new afbee1974e 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new e2e2290d30 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 4e6a8f14bb 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 84c74ac3b3 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 956d858e4b 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new b75992bafa 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 7181622db5 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 978dd35d71 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new e7b6a23e40 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 96f7962da2 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 920326fa15 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 6f91294897 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new d3b0ce1ce6 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new fe1f5aa3a2 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 787a1e738e 124: onsuccess: #2159: 1: Success after linux: 23 commits new ab039daf81 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 7f3d8ded6f 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 68205b758a 127: onsuccess: #2162: 1: Success after gcc: 9 commits new f07b8dc491 128: onsuccess: #2163: 1: Success after linux: 23 commits new 4aef93afa1 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 090ee3e0d8 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new c0217f4cd7 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 862e388aff 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 39a26278ae 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 5a2f0bd63c 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 3f88e98f8d 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 9b28626055 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 322da15a62 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 3ce7c1eb3c 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 6a4f88fd58 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new d9df3583a8 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new c637b56341 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 1fa089f82d 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 6ed8075f06 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 45b31cc70e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new c722363c99 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 975b621ad5 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 573680e9b0 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new cc959c885c 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 2fc3dc0461 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 4fb38c0b23 150: onsuccess: #2185: 1: Success after gcc: 3 commits new add3ea7f3b 151: onsuccess: #2186: 1: Success after gcc: 2 commits new d230d59e0d 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 8a1754f096 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 4b0c758fe8 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 323826ccef 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 9b6fa3a6cf 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 682b782901 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 2fef1fc7a4 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 3fe671781a 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new c442def5bd 160: onsuccess: #2195: 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 (bdf612ab1e) \ 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 1712 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30728 -> 30148 bytes 04-build_abe-stage1/console.log.xz | Bin 72256 -> 72356 bytes 06-build_abe-linux/console.log.xz | Bin 9172 -> 9996 bytes 07-build_abe-glibc/console.log.xz | Bin 239064 -> 239960 bytes 08-build_abe-stage2/console.log.xz | Bin 201828 -> 203060 bytes 09-build_abe-gdb/console.log.xz | Bin 37732 -> 37480 bytes 10-build_abe-qemu/console.log.xz | Bin 32356 -> 32160 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2552 -> 2608 bytes 13-check_regression/console.log.xz | Bin 17812 -> 16404 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 40 - 13-check_regression/mail-body.txt | 127 +- 13-check_regression/results.compare | 79 +- 13-check_regression/results.compare2 | 2541 +++++++---------- 13-check_regression/results.regressions | 101 - 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 129 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 +- results | 101 - sumfiles/g++.log.xz | Bin 3406988 -> 3410472 bytes sumfiles/g++.sum | 2492 +++++++--------- sumfiles/gcc.log.xz | Bin 3032252 -> 3031732 bytes sumfiles/gcc.sum | 4717 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1033776 -> 1030564 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202360 -> 202232 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2660 -> 2652 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 424540 -> 419844 bytes sumfiles/libstdc++.sum | 8 +- 45 files changed, 4664 insertions(+), 5815 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