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-arm in repository toolchain/ci/base-artifacts.
discards e6d3640795 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards e15d57c6a5 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 5485f06e00 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards fdbb2dff2f 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 709a0f26bd 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards ed5012b5b9 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards a9147d9e7b 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 14039e2a11 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards fe3ad7e747 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 9251a2792c 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards a2831576b7 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 19cd4de165 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 8ee473f5c7 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards e0c5e59d6f 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 5824033dfb 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards a2fdd841a8 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 88f5238127 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 786645428b 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards e71943e0e7 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 3093f364d7 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards c46f23b881 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 8207c1bc71 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 084da64930 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards a1de7ff7ee 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards b1cbe0fc5c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards e4168c6c21 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 5c7496fb4d 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards a8160844ae 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 9c81e0e52b 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 7c08dfe9d7 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards a8e8ccf591 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 551c7be5b9 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 914decab46 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 120c0ebd1a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 095278b8f4 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards d37039416c 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards a84c53ed42 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 73d8d46d15 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 082d4b49b3 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards f4cde1b291 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 2060606aa2 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards c733a579a1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1e2812df5f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3d1d629559 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 4b73727b8b 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards cdab33c5db 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 61368d3e0c 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards c9c950bd47 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 8f82d97a2c 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 73ec75fb88 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards b96c1f8c90 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards baa6f69a7b 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards c04aa6dbfc 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 30ff581014 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 1108230c82 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 69109d7030 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 57ef8a38a6 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 08405f57e6 74: onsuccess: 1: Successful build after linux: 44 commits discards 0ef3024c2c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 13314d2091 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 87f3729cd0 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 87dfec1baa 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 97d4af1919 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 2056e97bcb 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8d4e989dba 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b8ed6c4ef2 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 982074f803 65: onsuccess: 1: Successful build after gcc: 4 commits discards 6dd04b81d7 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 75db1be36e 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d541c6af21 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 3a51591400 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards f94a6fc299 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 6e35ac5c8f 59: onsuccess: 1: Successful build after glibc: 2 commits discards 3ca387a528 58: onsuccess: 1: Successful build after binutils: 2 commits discards 7824adbcdd 57: onsuccess: 1: Successful build after gcc: 7 commits discards b54afb5f9b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 05f320dfe7 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eeac610967 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards a0d5057754 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards da8a525772 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 50aa5b1746 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c110fa40ab 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 69cb5a8a30 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 799671cf6a 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 706ee75753 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 93361ddc1f 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 651c11857e 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ed5d51cdaf 44: onsuccess: 1: Successful build after linux: 34 commits discards eb6b17a89a 43: onsuccess: 1: Successful build after gcc: 2 commits discards ab692564ed 42: onsuccess: 1: Successful build after baseline build: no [...] discards 909ff62bba 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a608605ab6 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6864e6f436 39: onsuccess: 1: Successful build after gcc: 2 commits discards d457a7aa23 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b4a40cbf0a 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 03811c5634 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 48ac4c6980 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e232137c1e 34: onsuccess: 1: Successful build after gcc: 3 commits discards b4404b15bd 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0727adf3cc 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 07996cf9d3 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 01ec2060bf 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 11e92cb114 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new af4055714f 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d23772b4de 34: onsuccess: 1: Successful build after gcc: 3 commits new 623c0e53af 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 16fdfe7c91 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f1b953aa59 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fc3e18227f 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 12fd294422 39: onsuccess: 1: Successful build after gcc: 2 commits new c4f9595de7 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3b3cb363e6 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 70a5d34c39 42: onsuccess: 1: Successful build after baseline build: no [...] new ed9f49ce24 43: onsuccess: 1: Successful build after gcc: 2 commits new 4b6088981e 44: onsuccess: 1: Successful build after linux: 34 commits new b50bf176cc 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 80e5c5134e 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new b196af905b 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f82a3c782c 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 37744d659a 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fef6a86332 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7bf360a542 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3ad6c32c18 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 329f3ad1f0 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 7896c6ad83 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new d560ce74c7 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 18878b7c1c 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 319e0ffe09 57: onsuccess: 1: Successful build after gcc: 7 commits new f58f7f37c1 58: onsuccess: 1: Successful build after binutils: 2 commits new 63c2676913 59: onsuccess: 1: Successful build after glibc: 2 commits new 7f17a61e9d 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e9061da353 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 9e30816b87 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 0b58e4a58d 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 55dbdcc585 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0823239dd6 65: onsuccess: 1: Successful build after gcc: 4 commits new 4a1617da05 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 67c4a540a2 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 321f404665 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7b5606202a 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 404a90c18a 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 89a1264122 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new afa62a4f0e 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bfe5e36f01 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new c49fc3ccd1 74: onsuccess: 1: Successful build after linux: 44 commits new dcf75902bb 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aa26514184 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 1651600d51 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 83e5459cd5 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 30aaf8cfa8 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new ddce83a39d 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 1bb20f6f3b 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new db1ce0e63d 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 58ddf02179 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 5a7a37a4dc 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 4c5ff0d456 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 5490980d00 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 59584f3101 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new c5fdec5b54 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 666a6bda1f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new e5ee22d0ba 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 1af058877e 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new c2092b172e 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new a37220ebb6 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new ba7b3e2c93 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 579e25874c 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new be5844939f 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 7effab9237 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 0dde784f68 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new f5bc5cf1c5 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new b6917ec175 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 86fb4b6257 101: onsuccess: #1693: 1: Success after glibc: 14 commits new bba7b5b216 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new cd65d0d1d9 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 96c180a71e 104: onsuccess: #1697: 1: Success after gcc: 4 commits new d9bd7c85e7 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 6c7564e93c 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 5cb9278f0c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 6bab157a21 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new bd8c037d80 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new d1a16e537a 110: onsuccess: #1703: 1: Success after gcc: 6 commits new c9f0b437c3 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 9fb0bc5ed1 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 93ee57d464 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 35af6bcad8 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new c8a6731333 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 4b9e98e0a0 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 6c80fcb6bd 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 2c6d21b815 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 9505aec82c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 1dbfea50ce 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 88734aa100 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new e459f1cacb 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new fcd3fe2172 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 059ffd608f 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new fdd7e46a3f 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 8952b22171 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 5ba2f24360 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 8c2945be83 128: onsuccess: #1723: 1: Success after linux: 12 commits new 84030b4d11 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 4cb3126a8a 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 013113cbee 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 0a22431dae 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...]
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 (e6d3640795) \ 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 1760 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29992 -> 30256 bytes 04-build_abe-stage1/console.log.xz | Bin 90388 -> 91028 bytes 06-build_abe-linux/console.log.xz | Bin 8312 -> 8304 bytes 07-build_abe-glibc/console.log.xz | Bin 233636 -> 234500 bytes 08-build_abe-stage2/console.log.xz | Bin 222660 -> 224160 bytes 09-build_abe-gdb/console.log.xz | Bin 37224 -> 37428 bytes 10-build_abe-qemu/console.log.xz | Bin 30944 -> 31256 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2424 -> 2776 bytes 13-check_regression/console.log.xz | Bin 5336 -> 6028 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 9 +- 13-check_regression/results.compare2 | 24 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 26 + sumfiles/g++.log.xz | Bin 2659608 -> 2680968 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 2197864 -> 2202728 bytes sumfiles/gcc.sum | 2144 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 881268 -> 884228 bytes sumfiles/gfortran.sum | 10 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201268 -> 201232 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 426076 -> 422612 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 1286 insertions(+), 1158 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions