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 8ff40ba64a 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 2c4f1487de 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 00624ca3e6 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 7986d5dd90 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 1774cbeae9 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 644cd9aa26 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 039b185014 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards d549e9c8c9 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards fc6cca1432 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 83f8c313ab 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 357670f30a 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 826f233d45 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 37699e4228 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 4c83958d53 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 882769073a 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 2456e2afea 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 091bd275d9 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards a33963d82c 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 096cda756b 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 96ef4cf616 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 46d261d873 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards b4e2c9fccc 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 68f62c9d0d 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards a6d83c9449 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards f42aa6da04 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards f9fc3915c1 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards c8284bfd54 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 3abfac9417 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 7b549d9764 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 70055c0375 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards ecbfe15318 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 96870baee5 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards c8b40b1cc4 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 7ba9e29f5b 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards fac64fa4bb 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 0595042132 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 3f749e9ec1 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 056d501920 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 9675e7b380 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards c7455ca1eb 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 8841ac7a3b 124: onsuccess: #2159: 1: Success after linux: 23 commits discards bd07feccdd 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 86387013fe 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 9428ffa46d 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 7ef4f6b804 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 5bb235361a 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 9f3c92454a 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards ffc9678bb1 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 08056b0c50 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 6559d80ca0 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards ba2b4a7f80 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards c59b03d9da 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards d455b3bec9 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards d55c06c09d 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards b2a9360367 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 9ec165fe32 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 2b37eead75 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 597629fb53 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards d6ea255208 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards f9901675ca 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards f8546a04ee 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards ee27d8eb9a 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 5bbe54ecce 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 23817fdef9 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards c84de812c8 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards c16c7dd88e 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards c7a37f68b3 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 7c23c3dd76 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 7f1bd67a42 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 832f27950d 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards d369f65a0e 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards c35fbb5b56 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 3c8e73182a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards b09682750d 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards d25a341a41 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 49bde99d1d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 360f0642c7 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards c0185c3f70 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 6f5358a5e0 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards cf7df3c9f6 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards b18e1be356 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 7fe2b458cf 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 3cd18efb5b 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 99df3ee39d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 05f2e880b2 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards aa481eaa04 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f26eb47442 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards ad02bc3486 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 56b0580ff5 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 40aaf9e0ed 75: onsuccess: 1: Successful build after linux: 44 commits discards a7965fcc09 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 36b0d03b75 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 483f042980 72: onsuccess: 1: Successful build after linux: 12 commits discards 6d90e8a392 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards aedc2d0d05 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 73c75318f8 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 1aa8ca5bad 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e1a2413eb4 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards ff574dfc42 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 182c773f90 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 40966768ed 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c7e4c21111 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 11df3841eb 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8ee2778b9e 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 0e5defba6b 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 57d1b978f1 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9286ee5bb3 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 4373249a8e 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 36e5e79bc3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 61992465d9 72: onsuccess: 1: Successful build after linux: 12 commits new c7aa266035 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0b50dc6e4a 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 59ba3fb447 75: onsuccess: 1: Successful build after linux: 44 commits new 52aece1394 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9f9cc1f969 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 8ce6b4fa72 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new ac3d16dc95 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 36e83809ae 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e8839af958 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new c933282afa 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 37ce9b6437 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new cc77380e39 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new cf997d8e75 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new c681eaa58c 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 27a1bd3b3c 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 1a13699f78 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 5d426f0026 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 5bd14431ed 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 8a896b29ac 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new a082d0c187 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 26bdd4bfa8 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 25ee0b8c9e 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 6736271f3c 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 12753b873f 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 0958df7c1d 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 994a189e92 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 9b70971188 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new c15e4c9849 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 9d76ccf81d 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 5ba264b0c6 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 428e494f5b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 4ca9e4db3c 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 3278122f42 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new be5777fc05 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new e94290bcb5 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 67a9749310 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 029b885bfd 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new c5aaa16123 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 9cb7903b74 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 93169f3f3f 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 306366f1b1 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 1e29f1f5b5 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 5ea7d59660 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 63c1e85496 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new ff11a40295 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 1c635fcdc7 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 41a5573a19 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 5c27bb9ae8 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new a8e4d80816 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new ec37cf594e 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 88df6ecfbd 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 106e1af2de 124: onsuccess: #2159: 1: Success after linux: 23 commits new 8df8bdd5ff 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 3ab485ac84 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 5214f3ef36 127: onsuccess: #2162: 1: Success after gcc: 9 commits new f87d26145f 128: onsuccess: #2163: 1: Success after linux: 23 commits new 62686ebcd8 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 64efeaf613 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 9c4801f3a7 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new d5d5d03efb 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 013797a525 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new c3ac701d4a 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new a5768db162 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 06d5dec9ba 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 6bbef5da4a 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 14e8d47ae9 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 7fb470cd06 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new b338a29329 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new ae796fd33a 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 8f99f71a4a 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 0a2cd4c7c8 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 1cab78b28b 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new e429601d01 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new c97c5f89a3 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 20e5fe609a 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 92f917cd59 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new fc1df81de2 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 61bbad0c45 150: onsuccess: #2185: 1: Success after gcc: 3 commits new ff8829a5be 151: onsuccess: #2186: 1: Success after gcc: 2 commits new b010d6db8b 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 06eb56510b 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 7b0a34eb65 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 1e2604b3dc 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new f61891d895 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new b49e3cba54 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 822f0f6a6d 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 812cb9345d 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 98f8e6a607 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 16aa5d44d3 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 9145a910a9 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 828f6a84ce 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 843a1ad82d 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 39ae576271 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 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 (8ff40ba64a) \ 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 1716 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30300 -> 30492 bytes 04-build_abe-stage1/console.log.xz | Bin 72964 -> 72812 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 9208 -> 9196 bytes 07-build_abe-glibc/console.log.xz | Bin 240076 -> 240188 bytes 08-build_abe-stage2/console.log.xz | Bin 202984 -> 203824 bytes 09-build_abe-gdb/console.log.xz | Bin 37552 -> 37620 bytes 10-build_abe-qemu/console.log.xz | Bin 31996 -> 32124 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2688 -> 2692 bytes 13-check_regression/console.log.xz | Bin 7032 -> 5340 bytes 13-check_regression/results.compare | 24 +- 13-check_regression/results.compare2 | 204 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- sumfiles/g++.log.xz | Bin 3409012 -> 3438168 bytes sumfiles/g++.sum | 189 +- sumfiles/gcc.log.xz | Bin 3027248 -> 3005968 bytes sumfiles/gcc.sum | 5033 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1030620 -> 1035044 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2284 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202492 -> 202216 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2652 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 424468 -> 424428 bytes sumfiles/libstdc++.sum | 16 +- 37 files changed, 2741 insertions(+), 2901 deletions(-)