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 13c1c1f7b9 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 7c8f98333a 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 32d2e1f1de 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 44851faeab 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 417b1bc9f3 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 3a69ee4c22 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 509845db3c 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards a7aa5d9bb5 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards aac120d405 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 902b7e4b15 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards aa0f4e7174 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 4daec7bed9 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 76461ef814 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 4c97fe176a 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 702d6d42a5 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 1ef66303ef 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 37f2911991 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 10af6eea4f 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards b523553c90 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 585db4d589 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 491cab4ee4 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 0276aefe3b 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards db97e25cb0 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards a4fd3915b9 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 66212a6088 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 5e0d6f6679 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 7f20c13ec9 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards d55a0a6ff5 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 07b99e482d 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 9290b4abbe 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 6af5ac97f4 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 8ac00b69a4 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 32c4367c2d 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 7cea956e61 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 4c4c8d2dd5 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards ce9e9c52ff 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 473950ccb1 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 77dc245715 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 6f81a6eebe 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards b4b0d15d47 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 950e67d434 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards fd4f21fc0a 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 319ca2de33 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 35cf817ba2 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards b968632727 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards b8548eb734 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards e713e65776 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 8db9aeee4d 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards d6edde32f7 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 77a2b5f611 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards c1a357c909 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 458719e7e9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards cde2ddd682 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards d110a81ee0 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 8485818fb4 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 8a91809c87 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards d10e56dce8 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 47c5d68fa6 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 03e1dfd5f2 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 89428385dd 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 92b7f9389d 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards e774deda17 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 61a7a2352c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 8814dcd848 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards c41cae3cee 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards b3903f5630 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards e3b48ffa8a 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards c8576eb0e3 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0c0ea98c57 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 53f7a8f759 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 4d880fb0d6 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 5fccc6273e 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 837039dd4b 75: onsuccess: 1: Successful build after linux: 44 commits discards 8a6c5af2c4 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 2ba2318087 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 196748fd59 72: onsuccess: 1: Successful build after linux: 12 commits discards a633428eef 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 8e73372571 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 59b4c34b68 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards d66b3527ee 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ad47832abc 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards d60357b5bc 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 2b5c6ae328 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 79f0bbb01c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 24e6b575a1 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 1928758873 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards b397735a56 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards ae60a3b388 60: onsuccess: 1: Successful build after glibc: 2 commits discards 4dacd0e9ed 59: onsuccess: 1: Successful build after binutils: 2 commits discards 092675cd0c 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 9674e3be45 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 82b372510d 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3a13b8af64 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards f38c61597d 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 64dc3e6604 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 38b4fc658d 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 29936f5577 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fb46dd8c5b 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 396fc25fe0 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 4f46e7c92a 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1e41ad3a7c 47: onsuccess: 1: Successful build after linux: 10 commits new d9718f0cad 47: onsuccess: 1: Successful build after linux: 10 commits new de70a92094 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 49725838f8 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 389dc05e40 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new cd0ae7b02b 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c461f8c798 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new b3bbfa9880 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new d7c77f090b 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 93f68926ec 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new bed1f15b02 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d344c1bbd0 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 19f947f453 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 9eec14cb3a 59: onsuccess: 1: Successful build after binutils: 2 commits new 11a568fcdc 60: onsuccess: 1: Successful build after glibc: 2 commits new c0991fcfba 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 179b58ed36 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 535f2172be 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 650eb66a56 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2e9657342d 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c77dfc0562 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new c053ad5a45 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 1489e35af4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5fdb48379d 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 00ec16b4ec 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new f33f755936 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 2a709bde5a 72: onsuccess: 1: Successful build after linux: 12 commits new 693f3ee443 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 42e3875761 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 159fb0ed1a 75: onsuccess: 1: Successful build after linux: 44 commits new 20ae0d0866 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e6bd2f265f 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new e3891899f0 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new b40e997cc7 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 95aac3f2f9 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d3293e855f 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 9771065088 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 29fee573aa 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new a08724c72e 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 0bc5842ac4 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 8ce25d9885 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 58b2cc8a13 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 7048f29b05 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 42f3de4f4e 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 30975777f7 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 5939ffc277 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new fa99c540ae 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 6a9c7f4ffc 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 7af715a089 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 6ed94ceed4 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 6b5bc0cea5 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 41442abfa2 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 359fe894c6 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new d0bed38f44 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 35c1ecbbf0 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 6758cb5594 101: onsuccess: #2130: 1: Success after binutils: 81 commits new decfeec8e3 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 3f903735e5 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 4e2ffc9cd2 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new e4cde253d1 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 5696baa323 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 44f42f35c6 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new d1f15b047b 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 982a17acd7 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new f1a9466180 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 47427e431c 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 6b6b095b92 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new b964d9f3e0 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new f07c6d9d58 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new f20bb816e3 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 5653796366 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new f56796bac7 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 372c387758 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 2b90114150 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 94c04a5f57 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new f7ad2f6316 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new ffe4431def 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 6cc05e5624 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 3325d02be9 124: onsuccess: #2159: 1: Success after linux: 23 commits new e4bfdd4abb 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new b6c0643121 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new d5db18d0f7 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 10d81acc24 128: onsuccess: #2163: 1: Success after linux: 23 commits new cf0652603b 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new b9709ef95b 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 082fa047d3 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 625d116bbe 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 9d6b7b0e80 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 29a70d0b54 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new c6e2c33d0a 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 6db0e6c0a1 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new f26b4cdbca 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 94b8ea0f4a 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new c54a9c5f7b 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new e8a8c7502d 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 7153447b6e 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 0c50b22ae4 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 6a96402747 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new f33a886239 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 15de3c6809 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 51be600a40 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 95c6507025 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 8d7c7c469c 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 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 (13c1c1f7b9) \ 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 1712 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30532 -> 30500 bytes 04-build_abe-stage1/console.log.xz | Bin 72336 -> 72280 bytes 06-build_abe-linux/console.log.xz | Bin 8496 -> 8652 bytes 07-build_abe-glibc/console.log.xz | Bin 240032 -> 240452 bytes 08-build_abe-stage2/console.log.xz | Bin 203140 -> 202832 bytes 09-build_abe-gdb/console.log.xz | Bin 37644 -> 37736 bytes 10-build_abe-qemu/console.log.xz | Bin 31980 -> 31808 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3928 -> 3928 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2712 -> 2640 bytes 13-check_regression/console.log.xz | Bin 6644 -> 6852 bytes 13-check_regression/mail-body.txt | 87 - 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 264 +- 14-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 89 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.xz | Bin 3434876 -> 3413528 bytes sumfiles/g++.sum | 197 +- sumfiles/gcc.log.xz | Bin 3002148 -> 3029764 bytes sumfiles/gcc.sum | 4479 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1026064 -> 1035540 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202196 -> 202108 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 425152 -> 420408 bytes sumfiles/libstdc++.sum | 8 +- 38 files changed, 2670 insertions(+), 2598 deletions(-)