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 d8c3fe1d26 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 17fe5be600 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards b090ef2ba0 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 18433d903f 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards f04888c058 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 03652fcecc 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards cf5937fd21 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 6f49237c28 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards f34e05c534 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards c308c9f499 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 8a94dc384a 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 9b31385d80 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards cca0bca499 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards a7758c4970 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 7e00e1b7ba 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 8ab35bf65e 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 3b23288adb 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards dcc22bcec8 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 4051a5662e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 6778a7124c 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 489d03abe6 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 597e496d36 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards e78b22551a 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards fe3ae2a3e5 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 636b0befc1 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 5965b9088a 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 39e417160d 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards da42910593 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 8eb77bbd6e 124: onsuccess: #2159: 1: Success after linux: 23 commits discards cd7448bc58 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 17d9b587a1 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards be4e97d9da 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 1ccdd20e86 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards b1b08ea7ed 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 466b9fb17c 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 7fac25b697 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 2a1cfdaeef 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 17514b4380 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 32fb46244e 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards aa99a97982 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 1b8fbaccce 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 48e68689d2 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 165fce0b7e 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 5d755e1c8e 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 0b0d7447c4 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards cb838bce82 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 8dfd72cfe3 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards b5100f8b66 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 1f8acc9750 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 03c591b401 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 9bbf7a0cb8 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 934a139ae3 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards ac8f36cab4 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 0067b93e69 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 983956e668 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 177f987fc3 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards ae02da8b4c 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards c11ef400d6 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 5872eccd35 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards ba2c8b932b 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 6ec4826787 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards d9211b8db1 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards a900ed8698 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 3de00f745d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 1761460875 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 519861e50a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards b0d88fb795 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 5613d12e4c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 98eca2b187 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards a2834d31ec 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 40f13e8a2b 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards d523cedda7 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 1363080bbd 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c6e1e974d4 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c73ada8051 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 89e374cb9c 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 8656b64b8e 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1afdbc4eae 75: onsuccess: 1: Successful build after linux: 44 commits discards ad2f7f09db 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 52d4b1de96 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cfcf575760 72: onsuccess: 1: Successful build after linux: 12 commits discards aef1f635d3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 0761aa3ce4 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 4c04f277f9 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 220e18170c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dfdeb3c4da 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards ae503a0953 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards dc34eed820 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2ee14d9715 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5becb79a90 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 6a0d49642d 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards f9de5fa520 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 092ade8c85 60: onsuccess: 1: Successful build after glibc: 2 commits discards 7b18926549 59: onsuccess: 1: Successful build after binutils: 2 commits discards 0417ff5cca 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards e4e68beeaa 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 00c5bbc850 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 18614bd02a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 3ac44e44b8 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards acee7af3c1 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards b8d26046d6 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 459de2eab1 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 1f1ca48756 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2d9302893b 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new ee3f07c7df 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new ad390a4e72 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7350e54aa3 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 93bf971ed4 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 73715f6186 59: onsuccess: 1: Successful build after binutils: 2 commits new f3aaef0df4 60: onsuccess: 1: Successful build after glibc: 2 commits new 7da0537923 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new ceed1fdcff 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 44ba1ba40d 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new aefa48c3c6 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 035093f380 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4745c3dcb1 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new f44f50819e 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new a4d4532fd4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fa3cb83ba5 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 7c74861e72 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 9924ecf8d3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new ea23afa0e7 72: onsuccess: 1: Successful build after linux: 12 commits new 1c77c8c483 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 190b13b4ba 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new fb0cd6d0c5 75: onsuccess: 1: Successful build after linux: 44 commits new ad5e9d3917 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 09e92d6465 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new d21361a0ce 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 3fbb8d9cf6 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 81b44c860c 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 35387dc2e7 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new a9e2080c11 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 7da9e9f1f8 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 25b45f26e7 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new bb23acee08 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 3e7e4e7c33 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new c922711f71 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 65b97bca9c 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 889d0699cc 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 355fa83df9 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 245c27491c 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 39c355949b 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new a504260c24 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 10d78a0fab 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 5ee2928305 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new e500a09daf 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 1e2d6e079d 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new c837e522c2 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 50068afd4c 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 8369a8e0a3 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 2130e3b186 101: onsuccess: #2130: 1: Success after binutils: 81 commits new cb931c623f 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 795d96a765 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 17a724f0a0 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new e851ef1544 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 8069f52b3b 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 1361dbb1f8 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 1b252bc42f 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new d84776fa4d 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 53c3ccb96b 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 3280b6a0b9 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 8169b717df 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 7c44c50b57 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 7f8b2b5ed4 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new af63e90745 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new c61b3e5c94 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new ce68806775 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 5fb91f1dd7 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new b1c2e1657a 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 9c434c2b37 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 9abdb76c14 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new f1b2e9923b 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new c28effc580 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new feb7775395 124: onsuccess: #2159: 1: Success after linux: 23 commits new ca431d4021 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 388f8e822f 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 44a311f1af 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 211e72c40f 128: onsuccess: #2163: 1: Success after linux: 23 commits new 0a89644c38 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 259714adf3 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 7f766c23ac 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 45793d8734 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 2e4ea7bf31 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new f4ef12ff19 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new c375c087fb 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 2e8c41fad0 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new e640b68e9a 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 72a938d90a 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new c294c6389d 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 4d72c7ac9d 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 2b19bb66b6 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new eb30d469e4 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 66950a863c 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 2698a1617f 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new ded5e9f481 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new f6f45ca686 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 47b3157434 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 5037f3e509 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 67748ddce0 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 5e9ce2c692 150: onsuccess: #2185: 1: Success after gcc: 3 commits new eb0d2c2eb5 151: onsuccess: #2186: 1: Success after gcc: 2 commits new aaae8b9a98 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new c974eec8c9 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 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 (d8c3fe1d26) \ 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 1684 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30156 -> 30232 bytes 04-build_abe-stage1/console.log.xz | Bin 72668 -> 72116 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8920 -> 8944 bytes 07-build_abe-glibc/console.log.xz | Bin 240060 -> 239304 bytes 08-build_abe-stage2/console.log.xz | Bin 203076 -> 202832 bytes 09-build_abe-gdb/console.log.xz | Bin 37404 -> 37484 bytes 10-build_abe-qemu/console.log.xz | Bin 31844 -> 31944 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3956 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2752 -> 2448 bytes 13-check_regression/console.log.xz | Bin 19812 -> 31100 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 515 +- 13-check_regression/mail-body.txt | 244 +- 13-check_regression/results.compare | 388 +- 13-check_regression/results.compare2 | 8040 ++++++++++++++++++--------- 13-check_regression/results.regressions | 160 +- 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 | 246 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 160 +- sumfiles/g++.log.xz | Bin 3414820 -> 3433428 bytes sumfiles/g++.sum | 2750 ++++++---- sumfiles/gcc.log.xz | Bin 3030236 -> 2999004 bytes sumfiles/gcc.sum | 9004 ++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1033340 -> 1029608 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202640 -> 202576 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427340 -> 423868 bytes sumfiles/libstdc++.sum | 16 +- 43 files changed, 12390 insertions(+), 9318 deletions(-)