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 507a9af787 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 7082680620 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards aa7ea2ef6b 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 4969a3b18b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 0100c7ea1a 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards d4ed062b0f 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 9fcd5760e9 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards cfa756f457 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 7faad2e8d1 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 4192335d49 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards d65d229590 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 5813329cbe 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 478dcb250b 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards f09b0250a4 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 18b1aa9b85 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 7418fb42c3 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards b3e47c59fe 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards d25e8ed4e6 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 2c7f731bf8 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 5bcbdeaddb 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards d29c449dbf 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 5971d1b09d 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards d241bd81dd 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards cb52efe01d 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 54617e79f1 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards ae4c6fda92 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 0a3ddf86f6 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 34bf9c03aa 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards c247acb258 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 25acafcaf0 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 1674b8f731 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 8cefcf81a9 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 755fb4bb37 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 5bec9bc7a2 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 19364d7a16 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 6de6ddcd6f 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 934d46bd60 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 6e50e8536e 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards d7ca04d7cb 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 5cd5e1c60a 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4de9189fdb 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 6bb3aca4fa 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards cd46961670 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 4d93967eeb 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0b1a3d7f98 75: onsuccess: 1: Successful build after linux: 44 commits discards 45dad00f5b 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 44ab85f061 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 82551d058c 72: onsuccess: 1: Successful build after linux: 12 commits discards dfc4e06172 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 4f8f0e9582 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 5fa9d1863e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 626354d238 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 00a6ccbc55 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards f5e7ca6e46 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 30c8635400 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d2b75c66a7 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 25e53e73ee 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 354c42bd95 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 87be1416ca 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 27803d2958 60: onsuccess: 1: Successful build after glibc: 2 commits discards 5aa36f7f4e 59: onsuccess: 1: Successful build after binutils: 2 commits discards b922da239d 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 3ab83ce955 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards db6edd10a3 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 678064aea6 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards c5a77c55e2 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 929c5b1d46 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 05717ba37b 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 626a2bb671 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e2084a1288 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 09fe7d60aa 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 4f185c9de6 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1604171840 47: onsuccess: 1: Successful build after linux: 10 commits discards 39f434fcfc 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards a2fa55efce 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards baf0cb44fb 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 9575cd9ca0 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 75a1e2161e 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards 20b4a46c39 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3e29ff5434 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 36271c4301 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b73ef9c341 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards e84aee63ee 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2e1b52d2b3 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 003fd04488 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3ac3ffda15 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ab51581bfa 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8e2f7bd71c 32: onsuccess: 1: Successful build after gcc: 7 commits discards 80338cb5ed 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards aea409b8b9 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 003e7ab879 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3c3d99b324 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4144341433 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards bb83ffb00d 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9658fd9def 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3be5ebbcab 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a428a6ae92 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 57decb7a7d 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 998da7a9c4 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8394a4d11b 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 60e125b121 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 82f3e54a9c 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5cfbdce866 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ffb0d444a3 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 81922fe9cb 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e875be745c 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ac915af2cc 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d39fda76ed 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b3ab3d1331 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 91bd00f09c 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 3f31c1a6b3 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 646b5b344a 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d462e3be09 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 5030c525bd 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 318e15c786 32: onsuccess: 1: Successful build after gcc: 7 commits new c41c4d473a 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 84ba73008d 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0349f9ca51 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 52ec6e1dc4 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ea6b0ce0c2 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 5194930c06 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 6e42420c2e 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 26684ffe47 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new bf69953e20 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new beff842774 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 63d1d164ae 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new e29824ee60 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 52f2a967fa 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new af0e5c115b 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new f619b9b428 47: onsuccess: 1: Successful build after linux: 10 commits new c829b75bdd 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aa59c533f2 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 7282c2b588 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b451d50dc9 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 61a4f600a8 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 1b8f6edf48 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 38c718b58f 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 573238b8ac 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new a9ddc365a6 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 90d3a6e6ae 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6ab2eb878e 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 2bfa9085a6 59: onsuccess: 1: Successful build after binutils: 2 commits new a6ecdfba80 60: onsuccess: 1: Successful build after glibc: 2 commits new a21f4fcb62 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 57a04b6bac 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 832d4872a6 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 33c337886a 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a030e77a7d 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0d72223742 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new d1ba3f4040 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 627d82f67e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 283934a863 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 1a5d323f86 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 5926895b58 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 95b3348325 72: onsuccess: 1: Successful build after linux: 12 commits new 516bd77bf5 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d6e0c41c52 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 9fa6815414 75: onsuccess: 1: Successful build after linux: 44 commits new c91389cbef 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8ff18d5eaa 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new feca64825c 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 88e0ed563a 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4320745748 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 568025c007 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new be086fce4c 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 19f9a0bc9e 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 048350a43f 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 59970c53eb 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 8b9d8da0e0 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new c98804d85c 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 74b2359003 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 1432e8b2b8 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 2ce35d23cc 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 1f746638c5 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new f7c191b0a7 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 54ae7c2933 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 59dac4f2a5 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new e9de269354 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new e46f77fa3b 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new a218b75d6c 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 6655e32fc5 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 9e0f1c5de2 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 6615d9c4a3 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new ddfea07944 101: onsuccess: #2130: 1: Success after binutils: 81 commits new cce6125909 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new effc186604 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 4f74390e6d 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 9c97f9ec86 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new bfd2858969 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 945f5c1a1c 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 0c44aa1ca5 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 5187eac846 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 580d1ae5cc 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 0a99a8d4c2 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 81669825d0 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 6e72467552 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new c6f33b6869 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 1366607266 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 9368e41ea0 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 13906b15c3 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 521c1e7e01 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 163229b723 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 38f10b3a68 120: onsuccess: #2155: 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 (507a9af787) \ 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 1904 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 32388 -> 30320 bytes 04-build_abe-stage1/console.log.xz | Bin 72472 -> 72224 bytes 06-build_abe-linux/console.log.xz | Bin 8516 -> 8908 bytes 07-build_abe-glibc/console.log.xz | Bin 239924 -> 239788 bytes 08-build_abe-stage2/console.log.xz | Bin 203276 -> 203228 bytes 09-build_abe-gdb/console.log.xz | Bin 39660 -> 37512 bytes 10-build_abe-qemu/console.log.xz | Bin 31500 -> 32012 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2600 -> 2776 bytes 13-check_regression/console.log.xz | Bin 7404 -> 6292 bytes 13-check_regression/mail-body.txt | 43 - 13-check_regression/results.compare | 34 - 13-check_regression/results.compare2 | 94 +- 14-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 45 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- sumfiles/g++.log.xz | Bin 3404860 -> 3410492 bytes sumfiles/g++.sum | 87 +- sumfiles/gcc.log.xz | Bin 3008464 -> 3016028 bytes sumfiles/gcc.sum | 4325 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1028924 -> 1027592 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202048 -> 201928 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 420488 -> 427916 bytes sumfiles/libstdc++.sum | 2 +- 40 files changed, 2303 insertions(+), 2441 deletions(-)