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 2fc86245f 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards dcb91ee42 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/gl [...] discards aecab5874 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 242866308 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 769e025a7 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 commits discards 8e802ccda 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 commits discards 07e3c9ff1 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/gd [...] discards 690b92335 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 7bdae1edb 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-283 [...] discards a80f72647 128: onsuccess: #1723: 1: Success after linux: 12 commits discards a2e67cdf8 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 5259f6703 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards a0d6b549d 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 59c129142 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 9b5070122 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...] discards 763afd022 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] discards 26bbca19f 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] discards 3f1626050 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] discards bd63470d8 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] discards ad17121eb 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards dfad93068 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] discards 9b988798a 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] discards b860735de 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits discards c2076bdc7 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] discards 6df3dc41a 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] discards 59f1fd226 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] discards 14b051252 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards f75b2a29a 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 7c125fe08 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards d56fbc449 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards c0328d83f 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards 9ab19af6c 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards d65063e83 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards a4aff5274 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards d4c09f3fb 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards c7ffc52f5 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards f9f14c5f9 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 0f1303c00 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 45e035804 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards 9a2c3ad74 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards d71f2b2c8 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 75d981e90 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 081c84d5b 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 989e043e1 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 58bc4fb84 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 6a400205e 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 24a5796e2 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 61bc1ca54 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 4c5465d13 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards b24e73f31 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 76ff6cfb3 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 9b31756e4 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 37bcbfa5e 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 038f6848d 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 0f555fbfd 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 4de4d4da7 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 5ca28e895 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 73c2102a3 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards 1e04125a0 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 1b9c43985 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 59182d747 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 6e4e18222 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 221d37216 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 3cde71ff7 74: onsuccess: 1: Successful build after linux: 44 commits discards 355b50136 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 9485861b3 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards abf007901 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 3fe749241 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards 74534abf0 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 04f93eefd 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ef076abb8 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2eb9f662f 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 3b97bda6f 65: onsuccess: 1: Successful build after gcc: 4 commits discards 4efc8687c 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b1ce93a96 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 3e4633941 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards 6232c88ca 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 7fce5e496 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 05ac9b334 59: onsuccess: 1: Successful build after glibc: 2 commits discards eac73ba3f 58: onsuccess: 1: Successful build after binutils: 2 commits discards cc9c15c7d 57: onsuccess: 1: Successful build after gcc: 7 commits discards 806ded2d2 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 742d95730 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 43916f4ab 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards b2c1265ce 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 2391e05d3 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 48d1027bc 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ebd8c79e4 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 3a4b748ea 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards b1113b62b 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 4c44b07bf 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9bc3407eb 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards fa121271d 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f03c0c666 44: onsuccess: 1: Successful build after linux: 34 commits discards 8f2e9acbf 43: onsuccess: 1: Successful build after gcc: 2 commits discards 755c7f5c7 42: onsuccess: 1: Successful build after baseline build: no n [...] discards d3b45913f 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards cf7db9fb5 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f31a13e4e 39: onsuccess: 1: Successful build after gcc: 2 commits discards 70407a727 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards eb2ea868f 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 76d52bb29 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 99a1e615c 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9d6a27ac6 39: onsuccess: 1: Successful build after gcc: 2 commits new 5b1de2d0f 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new abebb6d9b 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3ce9ae241 42: onsuccess: 1: Successful build after baseline build: no n [...] new 168e5a68f 43: onsuccess: 1: Successful build after gcc: 2 commits new 65927593d 44: onsuccess: 1: Successful build after linux: 34 commits new 70e89371b 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8501f1e25 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new d0452093d 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d0bb452ef 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 044244907 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b1e0a0219 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fbe5771b8 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 13ada7dc8 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 8e8dc7870 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 577fb92ab 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 1f39d4b9b 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5b5501646 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2d5cac2c1 57: onsuccess: 1: Successful build after gcc: 7 commits new 80d8097cf 58: onsuccess: 1: Successful build after binutils: 2 commits new 111cd4b3e 59: onsuccess: 1: Successful build after glibc: 2 commits new 422b03c34 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 1114777e0 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 941db5f33 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 6adef7b11 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ed7f9df0b 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e4e9594e4 65: onsuccess: 1: Successful build after gcc: 4 commits new 452298937 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new bff83260c 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c78cfec73 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 42d01a2a1 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new a0d5ac626 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new e1e257906 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new b739d7cf1 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cafa78799 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 3fa513ed4 74: onsuccess: 1: Successful build after linux: 44 commits new 9abc42b66 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 032c01742 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 4f1517cdc 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3f7df73ca 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 63526d5e6 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new edfdfe813 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new f14dbc5ce 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 9b379bdd9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 18af5fd07 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new d42f46a81 84: onsuccess: 1: Success after gcc/glibc: 9 commits new b8e46e00c 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new e5e3fdfe5 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new d16d2608f 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 6023e9bcb 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 165f61d35 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 666ec359d 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new cad6b3cd7 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 22eea5420 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 534e1813d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 1c80e341a 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new dc0f9dc54 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new 1e162a93b 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new b6fa5c0bf 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new f8ef13a54 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 928327f1c 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new 3a7565930 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new ba114e188 101: onsuccess: #1693: 1: Success after glibc: 14 commits new abbac48c3 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new e173ca6e1 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new f1f9cf396 104: onsuccess: #1697: 1: Success after gcc: 4 commits new afb44ee52 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new d5af97c47 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new 7df3d9b8f 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 0fed3f0fb 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 93c899aea 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new c83cac278 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 50944e1bd 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new 527ffffd2 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] new 0fa8e2d1d 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] new 6574bbeab 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] new 5e39eeded 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits new fbabb89b6 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] new ef220d618 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] new 6905c13af 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 2e1874e44 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] new e3429b2f2 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] new 1be46a29d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] new 89b3a60c5 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] new ed534a3e8 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...] new ce1e672d3 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new d770085d1 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new b64a40bfb 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 1a568c5b7 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new ba5142408 128: onsuccess: #1723: 1: Success after linux: 12 commits new 394ad9a0d 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-283 [...] new f6b747417 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 345d1df94 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/gd [...] new 3a6483405 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 commits new 1a9f4bcc4 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 commits new 7a735e6a9 134: onsuccess: #1730: 1: Success after binutils: 2 commits new ee6246029 135: onsuccess: #1733: 1: Success after binutils: 5 commits new d82fb9765 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/gl [...] new c2ce308a5 137: onsuccess: #1736: 1: Success after gcc: 5 commits new a8f840716 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/gd [...]

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 (2fc86245f) \ 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 1692 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30360 -> 30672 bytes 04-build_abe-stage1/console.log.xz | Bin 91760 -> 91800 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8748 -> 8636 bytes 07-build_abe-glibc/console.log.xz | Bin 234240 -> 233968 bytes 08-build_abe-stage2/console.log.xz | Bin 226272 -> 225092 bytes 09-build_abe-gdb/console.log.xz | Bin 37804 -> 37368 bytes 10-build_abe-qemu/console.log.xz | Bin 32112 -> 31036 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3928 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2712 -> 2884 bytes 13-check_regression/console.log.xz | Bin 5748 -> 7280 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 8 +- 13-check_regression/mail-body.txt | 58 +- 13-check_regression/results.compare | 32 +- 13-check_regression/results.compare2 | 59 +- 13-check_regression/results.regressions | 32 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 60 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 32 +- sumfiles/g++.log.xz | Bin 2688404 -> 2661340 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2209604 -> 2233748 bytes sumfiles/gcc.sum | 2430 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 887124 -> 886740 bytes sumfiles/gfortran.sum | 51 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201316 -> 201260 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 423648 -> 430752 bytes sumfiles/libstdc++.sum | 13 +- 45 files changed, 1610 insertions(+), 1441 deletions(-)