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 66ffcccc4c 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards c91e06f7a5 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 443a83b1b9 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards d22bc52044 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 59f87618a5 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards d594bee45d 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 5e7d695ab5 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 7ac9be8010 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 06122c28c8 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 37ade73655 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 0fe87f8333 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards f23372e04a 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards e8dbed1ec6 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 4192f5f9f5 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards a654c32e94 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 285a83be0e 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 78da4d6b06 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 517b2d781d 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards ed4b5fccfa 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards b4f39559a7 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 7f4de63070 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 78125c3d18 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards dbdd26f3e2 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 37e1d28b3b 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 4020df5132 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards a04fef81f3 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards b0cb2e278a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 9559b1cf09 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards d6f2117cab 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 648eb915da 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards d1dcb0740a 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards e77964fae6 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 86119f79b6 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 1c487eb4f7 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 6713a59d81 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 50f8cf8405 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards c4bbf48744 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards a312a09876 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 72f41bdeed 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b0fe20925d 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 40f129f5b8 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards b8f48848d5 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 781f7269e7 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fc90201da2 75: onsuccess: 1: Successful build after linux: 44 commits discards bf48ba7471 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 82361a49b6 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c045b7a8e0 72: onsuccess: 1: Successful build after linux: 12 commits discards 6aa41048b7 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards d701d4a185 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards c728e7c5e5 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 6d1e99615f 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2fbb998581 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 551263e720 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 53175e86cb 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4652e35ea6 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5179d39af4 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards bae3323f67 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 596dd2a7e2 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards e1d286867d 60: onsuccess: 1: Successful build after glibc: 2 commits discards 8e2f2585e1 59: onsuccess: 1: Successful build after binutils: 2 commits discards 42f6ce637b 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 347b194c8d 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 959c43c898 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9a62bab26f 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards ce9b4718aa 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 0e83ab15ac 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 83a613a51a 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 0b0d70f558 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c8821244a2 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f4d2e8656f 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 86d9e51684 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards da2c680212 47: onsuccess: 1: Successful build after linux: 10 commits discards 25764e9ebd 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 7f5592dfb7 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e723460e4b 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 7a8b29df71 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 2de6029477 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards 06f8cc0dd4 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bf984861e1 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 179d184b53 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 99af086a8e 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards b371b7f9ec 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 87b3d1f316 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 809c47594f 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d0ac952c18 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 19cc381576 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6f97baf9e3 32: onsuccess: 1: Successful build after gcc: 7 commits discards ab53287eb0 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2f004874a1 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards dfcfaf8321 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b88dd5f016 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 8fa81d7502 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards eae3239f2a 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b41d971351 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0c17acd413 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards acefed9041 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 31450e8bcc 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 632b0dc56e 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 38070dcbfa 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c23709e3a8 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e2d34d677b 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4ecf09e190 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 60e125b121 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8394a4d11b 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 998da7a9c4 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 57decb7a7d 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a428a6ae92 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3be5ebbcab 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9658fd9def 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bb83ffb00d 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4144341433 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 3c3d99b324 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 003e7ab879 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aea409b8b9 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 80338cb5ed 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8e2f7bd71c 32: onsuccess: 1: Successful build after gcc: 7 commits new ab51581bfa 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3ac3ffda15 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 003fd04488 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2e1b52d2b3 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e84aee63ee 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b73ef9c341 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 36271c4301 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 3e29ff5434 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 20b4a46c39 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 75a1e2161e 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 9575cd9ca0 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new baf0cb44fb 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new a2fa55efce 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 39f434fcfc 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 1604171840 47: onsuccess: 1: Successful build after linux: 10 commits new 4f185c9de6 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 09fe7d60aa 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new e2084a1288 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 626a2bb671 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 05717ba37b 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 929c5b1d46 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c5a77c55e2 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 678064aea6 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new db6edd10a3 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3ab83ce955 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b922da239d 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 5aa36f7f4e 59: onsuccess: 1: Successful build after binutils: 2 commits new 27803d2958 60: onsuccess: 1: Successful build after glibc: 2 commits new 87be1416ca 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 354c42bd95 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 25e53e73ee 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new d2b75c66a7 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 30c8635400 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f5e7ca6e46 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 00a6ccbc55 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 626354d238 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5fa9d1863e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 4f8f0e9582 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new dfc4e06172 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 82551d058c 72: onsuccess: 1: Successful build after linux: 12 commits new 44ab85f061 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 45dad00f5b 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 0b1a3d7f98 75: onsuccess: 1: Successful build after linux: 44 commits new 4d93967eeb 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cd46961670 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 6bb3aca4fa 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 4de9189fdb 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 5cd5e1c60a 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d7ca04d7cb 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 6e50e8536e 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 934d46bd60 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 6de6ddcd6f 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 19364d7a16 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 5bec9bc7a2 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 755fb4bb37 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 8cefcf81a9 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 1674b8f731 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 25acafcaf0 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new c247acb258 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 34bf9c03aa 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0a3ddf86f6 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new ae4c6fda92 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 54617e79f1 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new cb52efe01d 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new d241bd81dd 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 5971d1b09d 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new d29c449dbf 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 5bcbdeaddb 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 2c7f731bf8 101: onsuccess: #2130: 1: Success after binutils: 81 commits new d25e8ed4e6 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new b3e47c59fe 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 7418fb42c3 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 18b1aa9b85 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new f09b0250a4 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 478dcb250b 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 5813329cbe 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new d65d229590 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 4192335d49 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 7faad2e8d1 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new cfa756f457 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 9fcd5760e9 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new d4ed062b0f 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 0100c7ea1a 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 4969a3b18b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new aa7ea2ef6b 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 7082680620 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 507a9af787 119: onsuccess: #2154: 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 (66ffcccc4c) \ 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 -> 1904 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 31080 -> 32388 bytes 04-build_abe-stage1/console.log.xz | Bin 72600 -> 72472 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 9260 -> 8516 bytes 07-build_abe-glibc/console.log.xz | Bin 239916 -> 239924 bytes 08-build_abe-stage2/console.log.xz | Bin 202904 -> 203276 bytes 09-build_abe-gdb/console.log.xz | Bin 38292 -> 39660 bytes 10-build_abe-qemu/console.log.xz | Bin 31408 -> 31500 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2704 -> 2600 bytes 13-check_regression/console.log.xz | Bin 6520 -> 7404 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 23 - 13-check_regression/mail-body.txt | 143 +- 13-check_regression/results.compare | 36 +- 13-check_regression/results.compare2 | 108 +- 13-check_regression/results.regressions | 43 - 14-update_baseline/console.log | 42 +- 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 | 145 +- mail/mail-subject.txt | 2 +- manifest.sh | 43 +- results | 43 - sumfiles/g++.log.xz | Bin 3421900 -> 3404860 bytes sumfiles/g++.sum | 363 +-- sumfiles/gcc.log.xz | Bin 3012288 -> 3008464 bytes sumfiles/gcc.sum | 4957 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1030344 -> 1028924 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201992 -> 202048 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2652 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422228 -> 420488 bytes sumfiles/libstdc++.sum | 16 +- 45 files changed, 2802 insertions(+), 3243 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