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 39ae576271 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 843a1ad82d 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 828f6a84ce 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 9145a910a9 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 16aa5d44d3 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 98f8e6a607 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 812cb9345d 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 822f0f6a6d 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards b49e3cba54 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards f61891d895 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 1e2604b3dc 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 7b0a34eb65 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 06eb56510b 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards b010d6db8b 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards ff8829a5be 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 61bbad0c45 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards fc1df81de2 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 92f917cd59 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 20e5fe609a 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards c97c5f89a3 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards e429601d01 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 1cab78b28b 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 0a2cd4c7c8 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 8f99f71a4a 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards ae796fd33a 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards b338a29329 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 7fb470cd06 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 14e8d47ae9 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 6bbef5da4a 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 06d5dec9ba 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards a5768db162 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards c3ac701d4a 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 013797a525 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards d5d5d03efb 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 9c4801f3a7 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 64efeaf613 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 62686ebcd8 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards f87d26145f 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 5214f3ef36 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 3ab485ac84 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 8df8bdd5ff 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 106e1af2de 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 88df6ecfbd 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards ec37cf594e 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards a8e4d80816 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 5c27bb9ae8 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 41a5573a19 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 1c635fcdc7 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards ff11a40295 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 63c1e85496 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 5ea7d59660 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 1e29f1f5b5 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 306366f1b1 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 93169f3f3f 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 9cb7903b74 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards c5aaa16123 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 029b885bfd 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 67a9749310 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards e94290bcb5 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards be5777fc05 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 3278122f42 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 4ca9e4db3c 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 428e494f5b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 5ba264b0c6 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 9d76ccf81d 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards c15e4c9849 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 9b70971188 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 994a189e92 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 0958df7c1d 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 12753b873f 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 6736271f3c 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 25ee0b8c9e 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 26bdd4bfa8 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards a082d0c187 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8a896b29ac 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 5bd14431ed 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 5d426f0026 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 1a13699f78 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 27a1bd3b3c 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards c681eaa58c 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards cf997d8e75 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards cc77380e39 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 37ce9b6437 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards c933282afa 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards e8839af958 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 36e83809ae 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ac3d16dc95 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 8ce6b4fa72 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 9f9cc1f969 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 52aece1394 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 59ba3fb447 75: onsuccess: 1: Successful build after linux: 44 commits discards 0b50dc6e4a 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards c7aa266035 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 61992465d9 72: onsuccess: 1: Successful build after linux: 12 commits discards 36e5e79bc3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 4373249a8e 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 9286ee5bb3 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 57d1b978f1 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0e5defba6b 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 8ee2778b9e 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 11df3841eb 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 15c1997ef1 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a5fdfb9c76 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new c60041cf16 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new d52a4f3571 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1fbf0bbeb3 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new a75219c749 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new e166e742b2 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 81a348c453 72: onsuccess: 1: Successful build after linux: 12 commits new 28346e894e 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 24f85211f8 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 82d02b3ae7 75: onsuccess: 1: Successful build after linux: 44 commits new 26d95a3a1d 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5f697d2dd6 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 619f93ec4a 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 21f55295a5 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 31b0bbe335 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3e900bc249 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 9cbcc82d49 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 5430e9d5ad 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new c54ca29e9d 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 6581053911 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 4013db3e64 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 441d7e84be 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 3ef02f13e9 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 236d53777d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new c738b18588 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 71b504f554 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new c258111ca5 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 96ab48bed9 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new f5ddc5c61f 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new c0494e8318 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 0b1a912582 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new fd1d20b361 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 66fba19183 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 628b558e56 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 612c658d70 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 8cd0d7f6b3 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 5877f39d0e 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new b117e0c13b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new db8b02351b 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 63d93b3e4a 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 7a69368ea5 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 66c2dc2f62 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new b902f9a0a5 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new a22d6e3672 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 675c646658 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 8c717686f5 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 503389a262 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new f003418ed9 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 49ef4e90c9 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new e8681e56e3 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new ce79d78553 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 5b63cb81c1 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new a8dd98b17e 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new b1b8269c9a 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 47cefdfefa 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 4530b0c5d0 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 94fbf88c81 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 52bb06dcdb 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new cbf7908fe6 124: onsuccess: #2159: 1: Success after linux: 23 commits new aa65db0897 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new eb2cb96dae 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 51f266fdec 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 8f7a1ece91 128: onsuccess: #2163: 1: Success after linux: 23 commits new 23f7ad4058 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new a375e26cbb 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 7e2e3a900a 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 0d0ce470d2 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 0ee6b98e96 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new d068bbc7cb 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new aa01b9e285 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new fae89091b8 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 8a612db198 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new a9001a102c 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 42c5038c00 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new a2e12a9556 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new a0c299b8bf 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 39144ff7d2 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 3d8e127a06 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 2b8b0be5c2 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 4960191b7b 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new a53f17ff7b 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new ebd25c7ad8 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new eda935ea1a 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 368fbaf77c 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 3ffdf74d37 150: onsuccess: #2185: 1: Success after gcc: 3 commits new bee5ccf97f 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 67a1377939 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 7725315500 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 2c904e58da 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 7a11c3af36 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 7122e13db4 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new cbebd27861 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 376aee789f 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new d465154297 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new e145fd6c44 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new dbbc8fdf66 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 8b61ac3666 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new fdc89ce190 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 3337da84bf 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 63575cd147 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 0cbef42b73 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits
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 (39ae576271) \ 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 2736 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30492 -> 31104 bytes 04-build_abe-stage1/console.log.xz | Bin 72812 -> 73140 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 9196 -> 9220 bytes 07-build_abe-glibc/console.log.xz | Bin 240188 -> 239960 bytes 08-build_abe-stage2/console.log.xz | Bin 203824 -> 205060 bytes 09-build_abe-gdb/console.log.xz | Bin 37620 -> 37748 bytes 10-build_abe-qemu/console.log.xz | Bin 32124 -> 32188 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2692 -> 2944 bytes 13-check_regression/console.log.xz | Bin 5340 -> 6704 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 17 + 13-check_regression/mail-body.txt | 51 + 13-check_regression/results.compare | 58 +- 13-check_regression/results.compare2 | 55 +- 13-check_regression/results.regressions | 51 + 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 53 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 51 + sumfiles/g++.log.xz | Bin 3438168 -> 3438928 bytes sumfiles/g++.sum | 215 +- sumfiles/gcc.log.xz | Bin 3005968 -> 3002280 bytes sumfiles/gcc.sum | 5182 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1035044 -> 1030516 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2284 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202216 -> 202248 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 424428 -> 427484 bytes sumfiles/libstdc++.sum | 16 +- 43 files changed, 3088 insertions(+), 2840 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions