Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (71f554bdb1 -> 94826eac49)

by git＠git.linaro.org

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 71f554bdb1 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 25cc411511 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards f6c92d1503 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 864296c798 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 2edc7eea38 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards a2a347de9f 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards bbbf11ee45 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 84dc5a2b68 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards b3db7cc387 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards a813b5b6a1 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 650dcc5464 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards a07bcdb306 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 68f3ff84c8 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 516568f786 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 3cb57b59bb 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 6b19e634cf 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 2bfe33c0af 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 30e5ede381 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards df2d235808 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 539572a8d3 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards fa84d0d547 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards fefeaae2cc 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 9a56e7436f 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards abf11365a2 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards a2cbf0188f 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards cc9b35b3b1 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 09b1c5ba75 128: onsuccess: #2163: 1: Success after linux: 23 commits discards a4a18fe655 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 13d18aac66 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 18e91df37e 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 6ce8802fd0 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 4cde71f5fe 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 796dd6cfbc 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 87870cea6c 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 87eb4bce48 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards b9e067cf8a 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 5dc4416720 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards b85803a92f 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 93e8cfecbd 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 213acea74c 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards fd488ab35c 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards fbc1b40a3d 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 08e4d4814f 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 0fc7da07e8 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 12fae94892 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 25fb2ace23 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 487fe1ff7a 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards fc1155c886 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards ab6208f50d 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 7e8e336a57 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards b7dc133863 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 6d89c82827 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 24e54cb662 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 628325fa6a 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 350d4713e0 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 4c69320477 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 6ebd5dadf6 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 3c0c6d495e 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards a82cf3602c 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards d1b2427d67 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 8a365cf2a5 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 728856177d 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 4778ac950e 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 702d6b42a3 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 7d8fd5fc42 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 7030de2c24 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 4d82e1c116 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards dbfc541e4b 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 27090cdfab 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards e5f153c843 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 79b23630d5 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards eca1677e17 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 5b62c17768 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 8d364e5b6d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 390e1e966e 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3239c67024 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5f9cb89224 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 8f5c8cd4ff 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 5c8ff8f4d5 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 74734d50ee 75: onsuccess: 1: Successful build after linux: 44 commits discards 8a32fc4488 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards cbc8a6ee89 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ce233d5e6b 72: onsuccess: 1: Successful build after linux: 12 commits discards fb88d81a54 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards feb063d296 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards c04746aba0 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards e064d825eb 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7e83936eb8 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 48b5bd8c40 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 8d217635b6 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fc01bf115c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 00c5a29a07 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 0791c14d58 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 556572c05d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 8890bfccff 60: onsuccess: 1: Successful build after glibc: 2 commits discards 8ad950b6f9 59: onsuccess: 1: Successful build after binutils: 2 commits discards 61447effca 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 48a6a6ebaa 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4d23312c09 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2b11c3cbe1 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 34ca317eef 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new e52a06d913 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 9eaeee48ff 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new c4f0e6dd5d 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3b408c19f9 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new bacb609864 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new e68efca98b 59: onsuccess: 1: Successful build after binutils: 2 commits new 00dd264d68 60: onsuccess: 1: Successful build after glibc: 2 commits new 09be2e9eac 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 22cbfb5caf 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 6d8e2b15bb 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new ea50043cbe 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 79647b2547 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aa822a57fa 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new a53f559573 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 4690a12c23 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f736cba4f8 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 5a294ee92c 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 460075457c 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 3b5ae4e322 72: onsuccess: 1: Successful build after linux: 12 commits new 5f678f5d26 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 664c4cd968 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 25d3a5649d 75: onsuccess: 1: Successful build after linux: 44 commits new 487a7f6b54 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5bb657995f 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 1f80d0fa7f 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 0b24af59dc 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 41156ccd7e 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a79cc899b5 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 5e70677787 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new c9aa8f0a90 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 5ef3e5fbae 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 3c4f0899d8 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 5c48491f6a 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new f363095c40 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 5089cbd7ee 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new a4a93b4afb 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 1291957ee0 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 7b0e265e72 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 924afcb9b9 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new e5d165a355 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new e2401bddc3 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new aed6ddb410 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 0414a21784 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new a2f03f66dc 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new de89e74e24 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 42ba2f78bc 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new db9ccc04d3 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new b76df77aa2 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 170c80e02c 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 443e408ba7 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 73339f110f 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new c1dc9ad219 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new ff6b10e572 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new edaf4db5b1 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new cfe50d1ad3 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 448ec07cc0 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 962e9dfcd8 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 7fac7042d2 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new d4088026f5 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new e91028af33 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new d2b25fff9d 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 3ed3ee32c6 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 9f5555d2ed 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 7ab72da4ab 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new ba59b8491d 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 4dfe7484bd 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 0f72394213 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 5cad7ce7e3 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 5be70e4c79 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 7328d5ac95 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 65a38d1193 124: onsuccess: #2159: 1: Success after linux: 23 commits new b0ee3aa118 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 92b89630bc 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 4e22b93178 127: onsuccess: #2162: 1: Success after gcc: 9 commits new e387e9eee9 128: onsuccess: #2163: 1: Success after linux: 23 commits new aa7cde98da 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 20cbc9c86e 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new d25e54e99e 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 7bc723f080 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 9d958f4607 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 24a6e24ed0 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new af68149978 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new d8d46cdbea 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 63bd572742 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 29d0d6f2bb 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new ceb0933f6e 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new de036dfc3a 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 09660b14e4 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 6d62db8971 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 18c95ca237 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new e9527f858b 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 0e7b02a0fd 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 47c2fd9eed 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 43bf08fb6b 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 37a536a95c 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 7ae279969a 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 2a81a2affa 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 8d8dd18c8e 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 7094769710 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 319001da96 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 330b64206e 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 94826eac49 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/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 (71f554bdb1) \ 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 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30832 -> 30368 bytes 04-build_abe-stage1/console.log.xz | Bin 72680 -> 72316 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8928 -> 8548 bytes 07-build_abe-glibc/console.log.xz | Bin 240008 -> 239844 bytes 08-build_abe-stage2/console.log.xz | Bin 203648 -> 203196 bytes 09-build_abe-gdb/console.log.xz | Bin 38152 -> 37712 bytes 10-build_abe-qemu/console.log.xz | Bin 31844 -> 31936 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2880 -> 2568 bytes 13-check_regression/console.log.xz | Bin 18844 -> 9528 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 11 - 13-check_regression/mail-body.txt | 143 +- 13-check_regression/results.compare | 345 +- 13-check_regression/results.compare2 | 3316 +++---------------- 13-check_regression/results.regressions | 101 - 14-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 145 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 101 - sumfiles/g++.log.xz | Bin 3415412 -> 3411884 bytes sumfiles/g++.sum | 148 +- sumfiles/gcc.log.xz | Bin 3030792 -> 3031720 bytes sumfiles/gcc.sum | 5311 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1029700 -> 1034672 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202448 -> 202288 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 423268 -> 427432 bytes sumfiles/libstdc++.sum | 16 +- 44 files changed, 3368 insertions(+), 6458 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-norov-allmodconfig updated (c4c393c0bd -> 4a3b341f11)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-norov-allmodconfig in repository toolchain/ci/base-artifacts. from c4c393c0bd 15: onsuccess: #60: 23023: Success after binutils/llvm/linux [...] new 4a3b341f11 16: onsuccess: #61: 23023: Success after binutils/llvm/linux [...] The 1 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 1696 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30188 -> 29912 bytes 04-build_kernel_llvm/console.log.xz | Bin 64392 -> 64656 bytes 05-build_abe-qemu/console.log.xz | Bin 32000 -> 31588 bytes 06-build_linux/console.log.xz | Bin 5292 -> 4824 bytes 08-check_regression/console.log.xz | Bin 4380 -> 4296 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (2a80c4e5bb -> 2012526d2a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-arm in repository toolchain/ci/base-artifacts. discards 2a80c4e5bb 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits discards 2202bd4a52 153: onsuccess: #1773: 1: Success after gcc: 4 commits discards 4c00da7161 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits discards 901712799d 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] discards 673a7c8231 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] discards 49d5491d2b 149: onsuccess: #1769: 1: Success after gcc: 3 commits discards 527eee9530 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits discards c7c9cf714c 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits discards bf25e292f9 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards 6e437d97b7 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards c2bd0f06b7 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards ed08ce8701 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards 9c64f65513 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards 5bc804a0a9 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards ce5a469ae4 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards 0f3dbe4a3e 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards 0072028b33 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards c998823cd4 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards 03cafda7cd 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards 00f5bc5baa 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards ebd259e8c0 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards 6871e1470e 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 9623b9aaa3 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards 978b65d196 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards 6407ed8abf 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards 13d9a61ecb 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards b50f1acfd6 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards d2a6f03533 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards b64cedcae0 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards d533c68c36 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards 281691771b 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards b36d7376df 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards 3435ad197a 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards 8c64df0545 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards b9f9d4c0e2 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards 4e75328ed8 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards 714d5cd41d 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards 3ffef7c51f 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 8fc8ee4410 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards c4f3fd5467 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards bf69f8352d 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards 9019b37cb5 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards 9851e30220 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards 106c87da0f 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards d7e16defe1 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards d445856f17 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards acb2516d38 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards 7cf87960b7 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards 1e47416acc 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards 7a9baa2656 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards bd290a77a9 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards 404a34910a 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards 6e68c478de 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards 604dd807ed 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards d5c61ca7ac 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards e6c9e133dc 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards 39399840ac 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards 30bcbcf97b 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards 14d44ddedf 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards 7a4c04c752 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards 60dc792795 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards ad2edc06dd 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards 8b47e62626 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards 154f8085d2 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards ecc737c4a8 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards e59abcddb3 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards 3cb2dce4f6 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards cafebc5383 87: onsuccess: 1: Success after gcc: 6 commits discards 9bb97a1bce 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards 282a8a74a4 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards 185d5f4a4d 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards 2e831e9391 83: onsuccess: 1: Success after gcc: 14 commits discards 932ac604d1 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 44bc1d5b19 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards 8a11de90da 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards 0debbc48e6 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards 65d8663718 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards 679f31b62d 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 2b30a8d8f1 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 3e8141265b 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards e875bb056a 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards 512060a184 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards d40b5914df 72: onsuccess: 1: Successful build after baseline build: no [...] discards 9555b38113 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 5e58a13050 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 4c305f91f9 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] discards 34685cdf33 68: onsuccess: 1: Successful build after gcc: 2 commits discards 51e9d94d89 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 9bf66e23a1 66: onsuccess: 1: Successful build after gcc: 4 commits discards 63eb33d289 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 3cfc5a3c01 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards fc789cd32d 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 7e1c01f82f 62: onsuccess: 1: Successful build after gcc: 4 commits discards 94a2df9a96 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 410ec1fb3a 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards a3615b43f6 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits discards 8133ace96d 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] discards a841c6252e 57: onsuccess: 1: Successful build after binutils: 2 commits discards fe2b38a410 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards bf4d1c134c 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 590188d492 54: onsuccess: 1: Successful build after gcc: 5 commits new c642c515c1 54: onsuccess: 1: Successful build after gcc: 5 commits new b4ada9e8dd 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 45cd4d5c76 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits new b091356c62 57: onsuccess: 1: Successful build after binutils: 2 commits new 80c96d0981 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] new fa17985a9c 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits new 10c461ea19 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits new e360852230 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 22ddb6cc0e 62: onsuccess: 1: Successful build after gcc: 4 commits new b82fd2fd3d 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 21a366f944 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 7516692dae 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits new e0b9f64df5 66: onsuccess: 1: Successful build after gcc: 4 commits new c23669ed12 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 46bf5f2538 68: onsuccess: 1: Successful build after gcc: 2 commits new c0728656d5 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] new b84461ea21 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 99b09c1407 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new abbb3dfb44 72: onsuccess: 1: Successful build after baseline build: no [...] new 4a9aeca7a0 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new f23bfd728b 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new 8f5d8f4446 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 6765cf15b2 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new d26da6b21c 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 1132794e93 78: onsuccess: 1: Success after binutils/gcc: 17 commits new d1654d8657 79: onsuccess: 1: Success after binutils/gcc: 23 commits new debd9ccf1d 80: onsuccess: 1: Success after binutils/gcc: 8 commits new 35995a4c75 81: onsuccess: 1: Success after binutils/gcc: 8 commits new 7e09f1ef89 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 9bd5d6892c 83: onsuccess: 1: Success after gcc: 14 commits new 5caa04c8c2 84: onsuccess: 1: Success after binutils/gcc: 2 commits new 163f1bf091 85: onsuccess: 1: Success after binutils/gcc: 19 commits new 54a167f029 86: onsuccess: 1: Success after binutils/gcc: 8 commits new 91fe1d2fd8 87: onsuccess: 1: Success after gcc: 6 commits new 64a0cd739e 88: onsuccess: 1: Success after binutils/gcc: 2 commits new 154d4446cd 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new 1dfc0628c3 90: onsuccess: #1645: 1: Success after gcc: 2 commits new e396a0dc63 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new 9e9f595366 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new 5a2587214e 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new 8518f86b56 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new 90f544a655 95: onsuccess: #1653: 1: Success after gcc: 13 commits new fc5c5aa192 96: onsuccess: #1654: 1: Success after gcc: 5 commits new b8216f14ed 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new cba9ce18dd 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new 13f4b172be 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new 79f19eab5b 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new 9c4c2e40f9 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new 598ddc897d 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new 014afaa6ee 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new 62170a81d7 104: onsuccess: #1700: 1: Success after gcc: 2 commits new 92ed2cb70b 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new 61cf300440 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 829e08189d 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new 580cae4c6e 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new c271bf7e32 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new 8d47869ab5 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new bbb20ec603 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new f537aa3284 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new 26c8608de3 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new f81d847fdf 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new 46d90f528f 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new de33a075c0 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new 6b5a8bea2b 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new a7dd5acd5d 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new 1e0cee5cb1 119: onsuccess: #1715: 1: Success after binutils: 4 commits new 45497ac3ea 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new b8fa92abe2 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new db3738ba3a 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new 3b1c9195e1 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new f6efcfeacb 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new b7c20f2fae 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new 2a67b0f0a2 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new 62e3c86fa6 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new ec3f419afb 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new b760f3cc0e 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new 10b8256b37 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 89cae07b91 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new 5f27eec0bc 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new 862285306f 133: onsuccess: #1733: 1: Success after binutils: 3 commits new 5d91465c83 134: onsuccess: #1736: 1: Success after binutils: 3 commits new f00b8987a2 135: onsuccess: #1739: 1: Success after binutils: 4 commits new a8a6a41e38 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new 39eebc453c 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new 3c95c3d606 138: onsuccess: #1749: 1: Success after binutils: 5 commits new cc3ad7b68c 139: onsuccess: #1753: 1: Success after binutils: 5 commits new 9fba389f79 140: onsuccess: #1756: 1: Success after binutils: 3 commits new c86f13a060 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new cde482198d 142: onsuccess: #1761: 1: Success after gcc: 83 commits new 565d79502a 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new 3882a85d87 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new fa01cd827c 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new 0e60710996 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new c8e15985cf 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits new 48bae509d9 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits new e686951e50 149: onsuccess: #1769: 1: Success after gcc: 3 commits new d644a3529a 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] new 8c0142e778 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] new 65a7c271da 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits new 296e88e76a 153: onsuccess: #1773: 1: Success after gcc: 4 commits new f91b9c2354 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits new 2012526d2a 155: onsuccess: #1775: 1: Success after binutils: 2 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 (2a80c4e5bb) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (20 [...] 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 1664 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2716 bytes 03-build_abe-binutils/console.log.xz | Bin 53448 -> 50792 bytes 04-build_abe-gcc/console.log.xz | Bin 233364 -> 232616 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3824 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2528 -> 2460 bytes 07-check_regression/console.log.xz | Bin 5252 -> 4856 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 7 - 07-check_regression/mail-body.txt | 22 +- 07-check_regression/results.compare | 25 +- 07-check_regression/results.compare2 | 52 +- 07-check_regression/results.regressions | 27 - 08-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 24 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 27 - sumfiles/g++.log.xz | Bin 2762656 -> 2807940 bytes sumfiles/g++.sum | 148 +- sumfiles/gcc.log.xz | Bin 2357212 -> 2358904 bytes sumfiles/gcc.sum | 3752 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 910320 -> 908880 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2176 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204648 -> 204536 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2536 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 465100 -> 466040 bytes sumfiles/libstdc++.sum | 12 +- 35 files changed, 2097 insertions(+), 2154 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-next-allnoconfig updated (da940ef45d -> 1bf47fdc81)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-next-allnoconfig in repository toolchain/ci/base-artifacts. from da940ef45d 11: onsuccess: #323: boot: Success after binutils/llvm/linux [...] new 1bf47fdc81 12: onsuccess: #324: boot: Success after binutils/llvm/linux [...] The 1 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 1884 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30416 -> 30148 bytes 04-build_kernel_llvm/console.log.xz | Bin 63668 -> 63636 bytes 05-build_abe-qemu/console.log.xz | Bin 32012 -> 31636 bytes 06-build_linux/console.log.xz | Bin 3092 -> 3072 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4556 -> 4332 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (e01db3839c -> a2fd0d5a31)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm in repository toolchain/ci/base-artifacts. from e01db3839c 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new a2fd0d5a31 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] The 1 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 1872 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 52220 -> 50752 bytes 04-build_abe-gcc/console.log.xz | Bin 234696 -> 232356 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8900 -> 8376 bytes 07-build_abe-glibc/console.log.xz | Bin 232288 -> 232240 bytes 08-build_abe-gdb/console.log.xz | Bin 49700 -> 49668 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3852 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2688 -> 2508 bytes 11-check_regression/console.log.xz | Bin 6528 -> 6280 bytes 11-check_regression/results.compare | 37 +- 11-check_regression/results.compare2 | 59 +- 12-update_baseline/console.log | 9 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.xz | Bin 2843824 -> 2856852 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 2496020 -> 2475128 bytes sumfiles/gcc.sum | 4660 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 946996 -> 952176 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2252 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 217312 -> 218044 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 464360 -> 466524 bytes sumfiles/libstdc++.sum | 10 +- 37 files changed, 2477 insertions(+), 2534 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_O3 updated (802b4e95d5 -> 01747d0d3b)

by git＠git.linaro.org

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled updated (89acc71288 -> 936596c154)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled in repository toolchain/ci/base-artifacts. from 89acc71288 49: force: #445: 1: Failure after basepoints/gcc-13-2887-gb0 [...] new 936596c154 50: onsuccess: #446: 1: Success after gcc: 16 commits The 1 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 1620 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 37952 -> 37732 bytes 05-build_abe-bootstrap_profiled/console.log.xz | Bin 83504 -> 79832 bytes 06-check_regression/console.log.xz | Bin 3440 -> 2660 bytes 06-check_regression/jira-body.txt | 2 +- 06-check_regression/mail-body.txt | 20 +- 06-check_regression/mail-subject.txt | 2 +- 06-check_regression/results.regressions | 11 - 06-check_regression/trigger-bisect | 2 - 06-check_regression/trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 1061 ------------------------ jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 20 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 11 - 23 files changed, 33 insertions(+), 1127 deletions(-) delete mode 100644 06-check_regression/results.regressions delete mode 100644 06-check_regression/trigger-bisect delete mode 100644 06-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-allyesconfig updated (4d958db092 -> d42ddce88b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 4d958db092 26: onsuccess: #490: 37: Success after llvm: 145 commits new d42ddce88b 27: onsuccess: #491: 37: Success after binutils/llvm/linux/q [...] The 1 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 1740 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30172 -> 30116 bytes 04-build_kernel_llvm/console.log.xz | Bin 62620 -> 62664 bytes 05-build_abe-qemu/console.log.xz | Bin 32160 -> 31484 bytes 06-build_linux/console.log.xz | Bin 3844 -> 3904 bytes 08-check_regression/console.log.xz | Bin 3124 -> 4420 bytes 08-check_regression/mail-body.txt | 5 ----- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 7 +------ mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- 17 files changed, 25 insertions(+), 32 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled updated (8947b17967 -> 89acc71288)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled in repository toolchain/ci/base-artifacts. from 8947b17967 48: force: #444: 2: Success after gcc: 7 commits new 89acc71288 49: force: #445: 1: Failure after basepoints/gcc-13-2887-gb0 [...] The 1 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 -> 1620 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 38200 -> 37952 bytes 05-build_abe-bootstrap_profiled/console.log.xz | Bin 512024 -> 83504 bytes 06-check_regression/console.log.xz | Bin 2688 -> 3440 bytes 06-check_regression/jira-body.txt | 2 +- 06-check_regression/mail-body.txt | 15 +- 06-check_regression/mail-subject.txt | 2 +- 06-check_regression/results.regressions | 11 + 06-check_regression/trigger-bisect | 2 + .../trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 1061 ++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 15 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 13 +- 23 files changed, 1134 insertions(+), 18 deletions(-) create mode 100644 06-check_regression/results.regressions create mode 100644 06-check_regression/trigger-bisect copy 07-update_baseline/console.log => 06-check_regression/trigger-notify (100%) create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/interesting-commits] branch master updated (72efba6 -> a52c50f)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 72efba6 Add entry 1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4 from https [...] new a52c50f Add entry b04208895fed34171eac6bafb60c90048eb1cb0c from https [...] The 1 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: .../tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled}/build_url | 2 +- .../last_good | 0 .../summary.txt | 0 .../tcwg_gcc_bootstrap/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy gcc/sha1/{953e08fde44a596e4ec2491efd15cd645e1ddc48/tcwg_gcc_bootstrap/master- [...] copy gcc/sha1/b04208895fed34171eac6bafb60c90048eb1cb0c/tcwg_gcc_bootstrap/{master- [...] copy gcc/sha1/b04208895fed34171eac6bafb60c90048eb1cb0c/tcwg_gcc_bootstrap/{master- [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022