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 90ff28182c 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 2078a43226 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 2caaab12a5 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 5d9ea963aa 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 606c83301c 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 882bc23060 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 5803a1f853 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards ad93c4ad88 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards ab430c1f9f 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards c1f20cc8eb 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 44d50f2139 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 983ca60edf 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 58d8db1c39 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 276e0420f9 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 09c43b0bd2 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 8f4e4eb41b 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards a3459fb57c 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 4ea84b2061 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 7e21a0f4d6 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 0ce799a743 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards c402964017 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 1b0cfa2e10 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards ba73217d1f 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards e87f0c31ed 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards adfc360083 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 68771b79b2 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 0c43773f53 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards aac8cd95c4 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 96df226891 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 2d4705111c 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards b01a867064 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 99a3ffe21e 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards fe95e9fd29 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 653e4aa71b 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards d41f45ef03 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 7461a8884b 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 0900dfd3fb 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 71782058c0 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards bb33f82c94 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 34bed7f669 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 73eef4066a 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 4b65b9c787 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 91860e4c31 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 19c99490ea 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 9f436cfd20 128: onsuccess: #2163: 1: Success after linux: 23 commits discards d11f48cede 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 1df0b2fb6f 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards eb357676a9 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 5103a3e987 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 82c45aa40f 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards e69a2e0da4 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards d43919a076 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 2d3e0c97fc 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards d7ca793d10 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 820a3d9e08 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards aa81e4dad1 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 38e8f46fc6 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards c77c641641 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 9cb434d79e 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 1c7291f439 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 73fe7ab3fa 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 5a0bd61c84 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards a15e81b6e4 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 5fcda510bb 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 9ae80015ed 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards d499270000 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 0aa25e9127 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 59f7b4bd79 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 69bafb7891 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards c65dc656f9 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 17a593a1fd 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards ec312fdcf2 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 65d809ef33 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 7d99696c4b 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards ac25e9d8fd 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards cfa17dbe98 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 35387944bf 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards b9e2e7bef9 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards f81726939b 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards a9227657d0 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 103f6f737c 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards c589f779fc 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 60196e991a 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards f01f9df4a9 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards c650e47634 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 8ef6ed65e5 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards f41a959a0d 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 5ef426bbdb 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 98801c9dff 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 28243755f9 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 272a8f3207 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 525adb350f 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 10750cc932 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 59c423e429 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0101894773 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 9e036e2089 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards d6006ad73f 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 825a053775 75: onsuccess: 1: Successful build after linux: 44 commits discards 3f3f728471 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 2fbd69b2a6 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c335784d66 72: onsuccess: 1: Successful build after linux: 12 commits new bbaf4e72f8 72: onsuccess: 1: Successful build after linux: 12 commits new 30ca9227b0 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 04e39af6e4 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 7e747326cd 75: onsuccess: 1: Successful build after linux: 44 commits new 15cf081b7a 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 914264eb72 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 44ab18af47 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new b9f55dad9b 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f4514d3ba3 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 83c8caad2b 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 65ccf2849f 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new d8ddc0d807 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new a3d1490844 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 313ddc93a2 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new a886ae7253 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 5560cb9040 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new a4bbe2e067 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 4210319c66 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 5bf82d213b 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 92d525fcc6 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 35c1e1a8bd 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c8c20ace81 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 63c2749af8 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 617c6065db 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 5bee44af9c 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new de9a00061a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new a2730484f2 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 4f0a27063a 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 8eef5232dd 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new c45143afa6 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 98a7303248 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 1346b87b72 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 7b396e8e46 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 70cd4ec787 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new c2980c5e49 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new a08c416795 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 6256c99e07 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 1515391aee 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new a4d92b094d 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new ba62061c45 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new c3b7af0d56 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new bde8b46aec 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 7516e02375 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new ce31e7f1a1 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new e1f1cb4b77 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new de7bdbd2fa 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 123927428a 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 192ef765b9 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new cfc00d30ea 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 3f9fceac23 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 29e316ef66 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 4cebc00e1b 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new e4836737bc 124: onsuccess: #2159: 1: Success after linux: 23 commits new 1a99f7a490 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 9a55638a84 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new b99f1f0707 127: onsuccess: #2162: 1: Success after gcc: 9 commits new e0383d4e87 128: onsuccess: #2163: 1: Success after linux: 23 commits new d41d5f758d 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 4bf9f76a3c 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new d6142ec651 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 524388caad 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new d7479bb62d 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new caf164a142 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new fa28546006 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 42d1c26025 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 3af7b0d4cb 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new ff08ff1b33 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 69dc2b1058 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new ccf5ac62f5 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 8e1ae83e10 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new f879a83e33 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 5787e649da 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 244ff35392 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 7f15d026d0 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new d3cf3e1656 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 62b551268c 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 8f72b79cdc 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 02a5e1089a 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new a32d78c5c2 150: onsuccess: #2185: 1: Success after gcc: 3 commits new a74b02ece5 151: onsuccess: #2186: 1: Success after gcc: 2 commits new f3c485e08a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 529243955d 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new e68b3f5e00 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new d06332cc14 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 47d141f31f 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 34ae868845 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new b80640d74d 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 1242600672 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new f59e8abb6e 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 11cff3ec6a 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 9a34728241 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new a0175ec57c 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 96ec80b707 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 421a73cec5 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new e6a044dcae 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 5adaddb04b 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 587352b11e 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new e0ba0b8d36 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new f567a86abc 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 6101f71f11 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 91b9b5d755 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new cc24250702 173: onsuccess: #2208: 1: Success after gcc: 10 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 (90ff28182c) \ 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 1756 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30740 -> 30776 bytes 04-build_abe-stage1/console.log.xz | Bin 72672 -> 72536 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8544 -> 8584 bytes 07-build_abe-glibc/console.log.xz | Bin 238996 -> 240412 bytes 08-build_abe-stage2/console.log.xz | Bin 202920 -> 203620 bytes 09-build_abe-gdb/console.log.xz | Bin 37920 -> 37936 bytes 10-build_abe-qemu/console.log.xz | Bin 31968 -> 31760 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3920 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2808 -> 2712 bytes 13-check_regression/console.log.xz | Bin 16704 -> 8840 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 97 +- 13-check_regression/mail-body.txt | 224 +- 13-check_regression/results.compare | 175 +- 13-check_regression/results.compare2 | 3469 ++++------------------ 13-check_regression/results.regressions | 133 +- 14-update_baseline/console.log | 76 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 226 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 133 +- sumfiles/g++.log.xz | Bin 3411232 -> 3427456 bytes sumfiles/g++.sum | 235 +- sumfiles/gcc.log.xz | Bin 3037936 -> 3026824 bytes sumfiles/gcc.sum | 4762 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1029596 -> 1033216 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202428 -> 202244 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 428700 -> 430360 bytes sumfiles/libstdc++.sum | 14 +- 41 files changed, 3852 insertions(+), 5799 deletions(-)