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 286763cb3f 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 40fcca45b8 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 3556fcd221 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards f4493dbf46 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards c468e24706 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards f951a8bde5 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 55da16576d 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 8fb969cc2d 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 61d23cddcf 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards cf09d9bd2a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 5b65a8f44f 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards e9eea594e9 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards ed0f65e2f8 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards df659b9c00 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 6246007d36 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards bd7a8f6ee5 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 09e7c53dce 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 5968df5418 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 9b8581b3d9 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 9765cdd7bd 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 49d3a10e83 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards ec5ffbfae0 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 2b8249a732 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 647966ffcf 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 9f49f4c6b1 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 021c4a029e 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 8eb01bd2c2 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 17e900ee6b 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards f24112118b 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 53c8da7675 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 5126ab4a47 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 21e9f9996d 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards a4f5b8db54 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 659e999505 128: onsuccess: #2163: 1: Success after linux: 23 commits discards da75d4e3cf 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 77fc9a899c 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 0163e05bed 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards c13a1f86b8 124: onsuccess: #2159: 1: Success after linux: 23 commits discards c5be307b4f 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards a9eb3cb786 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards ea094c39f6 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 3b3b1d1929 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 57c5baff4b 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 60bca1c67f 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 732e02c413 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards a50c535052 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards e6f94ad21f 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 5283b6b757 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 68baa6fc42 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards e6be03c3cc 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards cda02b0319 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 09c6da24d3 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 5a68dcbe73 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards c76ae132e5 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 5263df3c13 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards a8d7270a26 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 4380ca8291 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 5bc0bf5bbc 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 85233ae10a 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 6d93fb465f 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards aacf9ed127 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 7a3b54387b 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 41957ac0f8 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 3e70405cf5 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards dd7ebd4c26 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 4f78b4054e 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards e0d40bd5f8 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 9f5649adbe 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 007980e550 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 78d9d3d0e2 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards bf7f9673e4 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 8b10bca901 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 51cce2d23e 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards da54384812 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards dc3d36a4a8 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards aa2cb47570 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 3ab4dabe03 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 4175e92d4e 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 748c941fbd 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 2cbfce75ad 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 9fc572bb9d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards b84aace20c 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards beb3820d2e 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards fd1ee418a7 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 0a378427a3 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 3afb87c3d8 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f2bb02755c 75: onsuccess: 1: Successful build after linux: 44 commits discards b40fa33f81 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards b258056614 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5124322d32 72: onsuccess: 1: Successful build after linux: 12 commits discards 0e9460140c 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards aa005e2f7f 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 643aeb00bb 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards cba03fe747 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9377b2520e 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 4a7ff5ea78 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 798562e08d 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f758833964 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9b2793d8e8 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards ed5a03dbb1 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards d7cc25685f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 33974947e9 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new cc9207c2d8 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 6a7486e6f9 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 08fbe77942 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b2f384cabd 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 95e61a4363 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new dbfa27cb66 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 3634dd1762 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0b09980422 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 18e5b63c96 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 073664df36 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new fe35cf32ea 72: onsuccess: 1: Successful build after linux: 12 commits new 048481ad69 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e4981204d7 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new b2a1ed533d 75: onsuccess: 1: Successful build after linux: 44 commits new 7073310843 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3e8f4d62d6 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 26e1b456d1 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new afa5c5f0bf 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d2be4dd2d8 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e9a102ecd5 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 9bc184e674 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 91d9cd5c07 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 62a9966761 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 46175e8dc7 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new dcf486d920 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new efe9bf5859 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new ccdf9a4209 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 4ca6bef5e5 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 5843253e29 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 5a1cc01b10 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 844d57fb1f 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 04b98cde14 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new be809e6c30 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 4dccfb0f4b 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 3638d91da1 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 4ced6a8bab 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 8f4a7f8269 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new a0e6970b29 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new d81bcac289 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 5b0c70bcd8 101: onsuccess: #2130: 1: Success after binutils: 81 commits new ad89073ba2 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new f63431ce89 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 8e28af31b8 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new b3e981321c 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new c848972de4 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 1101692d58 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new e43322fc9e 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 5ad31d859b 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new d55267530a 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 9c0a521241 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new aea3ed83f3 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 418518d092 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new ad96eb2366 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 4bd8d63331 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new b4e129f0f6 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 7eb8a3f99c 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 02bd408d81 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 8f0c10d96e 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new dfc64be600 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new f8ea90f269 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 9ec7d537f4 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 4c798f71f0 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new b5b938b0cc 124: onsuccess: #2159: 1: Success after linux: 23 commits new 12d05888ac 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 29ae108f36 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 05461d31f3 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 1f01297726 128: onsuccess: #2163: 1: Success after linux: 23 commits new ea1b7f5432 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new d762e9595d 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 1c4850af1f 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 4801292882 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 0514bab253 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new f42268936e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 787012bc19 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 265d1c05e2 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 897008f1e6 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new faa8d994e1 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 9a784d11cc 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 77a0952fd7 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new ed7f3ff16c 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new f81b2d68aa 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 2dc81b6626 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 0273822d48 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 452ece8007 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new afdd380d0e 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 5a59f0914f 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 34b0cb1abd 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 3ed285fd18 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new a78b18ba76 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 0048261030 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 191cea079d 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 77d3a8c9ae 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new fcf10b984c 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new d016f47839 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new a0f5868d83 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 8963064629 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new d50bcfacee 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 71b860bdf2 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 7c5aca15f0 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 621a2452eb 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new a6c9296282 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/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 (286763cb3f) \ 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 1768 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30272 -> 30680 bytes 04-build_abe-stage1/console.log.xz | Bin 73696 -> 72208 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 9132 -> 9188 bytes 07-build_abe-glibc/console.log.xz | Bin 239780 -> 239956 bytes 08-build_abe-stage2/console.log.xz | Bin 204460 -> 203236 bytes 09-build_abe-gdb/console.log.xz | Bin 37440 -> 37760 bytes 10-build_abe-qemu/console.log.xz | Bin 31920 -> 31908 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3924 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3968 -> 2608 bytes 13-check_regression/console.log.xz | Bin 7180 -> 6140 bytes 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 191 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- sumfiles/g++.log.xz | Bin 3414740 -> 3411544 bytes sumfiles/g++.sum | 162 +- sumfiles/gcc.log.xz | Bin 3028540 -> 3031412 bytes sumfiles/gcc.sum | 4753 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1029576 -> 1031376 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202396 -> 202248 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422936 -> 430132 bytes sumfiles/libstdc++.sum | 20 +- 39 files changed, 2585 insertions(+), 2763 deletions(-)