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 b15ddc8013 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards ebe9ce02d7 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 57457afb31 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 797b369356 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 958c5773ea 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards c3b0a39992 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 3ab9d126e9 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 8f56bbbf1a 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 8f626d671a 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 86082833c2 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards a7162c8ec0 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 46d9964337 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards fe83fba76e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 4051e83abf 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 964e9c8171 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards c983184d78 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 4bca6f5afb 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 13af915050 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 7f6a67db3b 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 9af996124c 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 5be1758157 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 1859cf8ba5 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards d3bd0e3a4d 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 0c43b8dba4 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 9bd195a54c 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 730f0cca20 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 684e810169 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards df7aff3880 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards b4e15c21ba 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards c5950835da 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 527e6c40f7 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 3649664b80 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 69997dcb4e 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 33746d849f 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 5b8d354101 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards bed1f92803 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards bc93c13682 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 94dc3fbfb0 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards e6557f20cf 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 088fe0d62e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 6096385cf5 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards f1ab8d1c20 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards fbcc8d4d12 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 968705e2f7 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards f776165aa0 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards f4dee28b19 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 125111f775 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards d4ee789dd0 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 148cbe3c52 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 9872996cab 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 3af36e3607 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards fd4518b8ef 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 4a910b9c74 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 50542760f0 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards bf0e61a8a2 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 4f2db75131 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards b7d263e262 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards bbfc892d31 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 1a74f92c4b 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 330d97e752 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fa42e4c207 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 77355e5a52 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2de4e25d3b 74: onsuccess: 1: Successful build after linux: 44 commits discards a09d7745d1 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 0886163cd3 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fdf38ff121 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards e0b1fcdfad 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards a7c86ca794 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards e2123ad1ff 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c0b3bce8e4 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cb9e0a37e5 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a36adaa6c5 65: onsuccess: 1: Successful build after gcc: 4 commits discards 662db299f3 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f25f3e40f6 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 67b2dacfd2 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards f78266f670 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 22abb2bd66 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards f223e005cf 59: onsuccess: 1: Successful build after glibc: 2 commits discards 5abeb7f8b7 58: onsuccess: 1: Successful build after binutils: 2 commits discards a9fb4df8e7 57: onsuccess: 1: Successful build after gcc: 7 commits discards 539babac4d 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 10cc050718 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 82cbbdd406 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 6974365bae 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards f796f6c54e 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 23b966eb67 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0c51eedc44 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c9cae5e440 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3846049a5d 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 9d4a99f32c 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0a78622aae 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 50ca3134c2 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5d9217b605 44: onsuccess: 1: Successful build after linux: 34 commits discards 2695624ff4 43: onsuccess: 1: Successful build after gcc: 2 commits discards a863fc9b7b 42: onsuccess: 1: Successful build after baseline build: no [...] discards 73de885dc7 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c0028bb053 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0678105b29 39: onsuccess: 1: Successful build after gcc: 2 commits discards f000cc928b 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e07a7d6fbf 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 8ed5ecd93d 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 21719e64fa 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new eb2ea868f1 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 70407a727b 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f31a13e4ed 39: onsuccess: 1: Successful build after gcc: 2 commits new cf7db9fb52 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d3b45913ff 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 755c7f5c74 42: onsuccess: 1: Successful build after baseline build: no [...] new 8f2e9acbfc 43: onsuccess: 1: Successful build after gcc: 2 commits new f03c0c6664 44: onsuccess: 1: Successful build after linux: 34 commits new fa121271d5 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9bc3407eb4 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 4c44b07bf7 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b1113b62b8 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 3a4b748ea8 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ebd8c79e42 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 48d1027bc8 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2391e05d3f 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new b2c1265cec 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 43916f4ab5 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 742d957309 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 806ded2d2a 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cc9c15c7d3 57: onsuccess: 1: Successful build after gcc: 7 commits new eac73ba3f6 58: onsuccess: 1: Successful build after binutils: 2 commits new 05ac9b3346 59: onsuccess: 1: Successful build after glibc: 2 commits new 7fce5e496c 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 6232c88cad 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 3e46339418 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new b1ce93a966 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4efc8687c0 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3b97bda6f0 65: onsuccess: 1: Successful build after gcc: 4 commits new 2eb9f662f4 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ef076abb89 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 04f93eefd6 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 74534abf07 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 3fe7492419 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new abf0079013 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 9485861b30 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 355b501367 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 3cde71ff74 74: onsuccess: 1: Successful build after linux: 44 commits new 221d372161 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6e4e182229 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 59182d7474 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1b9c43985e 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1e04125a0a 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 73c2102a32 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 5ca28e8952 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 4de4d4da78 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 0f555fbfdf 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 038f6848d3 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 37bcbfa5ea 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 9b31756e4c 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 76ff6cfb35 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new b24e73f311 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 4c5465d135 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 61bc1ca54d 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 24a5796e23 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 6a400205e0 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 58bc4fb84d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 989e043e1f 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 081c84d5b5 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 75d981e90c 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new d71f2b2c8b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 9a2c3ad74a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 45e035804e 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 0f1303c006 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new f9f14c5f91 101: onsuccess: #1693: 1: Success after glibc: 14 commits new c7ffc52f50 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new d4c09f3fb4 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new a4aff5274a 104: onsuccess: #1697: 1: Success after gcc: 4 commits new d65063e831 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 9ab19af6cd 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new c0328d83f7 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new d56fbc4496 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 7c125fe08f 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new f75b2a29a1 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 14b0512522 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 59f1fd2260 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 6df3dc41ad 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new c2076bdc72 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new b860735de7 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 9b988798a5 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new dfad93068a 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new ad17121ebe 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new bd63470d80 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 3f16260501 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 26bbca19fe 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 763afd0226 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 9b50701222 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 59c1291426 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new a0d6b549d1 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 5259f67033 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new a2e67cdf84 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new a80f726473 128: onsuccess: #1723: 1: Success after linux: 12 commits new 7bdae1edb6 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 690b923357 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 07e3c9ff14 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 8e802ccdac 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 769e025a7f 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 242866308f 134: onsuccess: #1730: 1: Success after binutils: 2 commits new aecab58744 135: onsuccess: #1733: 1: Success after binutils: 5 commits new dcb91ee423 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 2fc86245f1 137: onsuccess: #1736: 1: Success after gcc: 5 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 (b15ddc8013) \ 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 1732 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30780 -> 30360 bytes 04-build_abe-stage1/console.log.xz | Bin 93196 -> 91760 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8820 -> 8748 bytes 07-build_abe-glibc/console.log.xz | Bin 235624 -> 234240 bytes 08-build_abe-stage2/console.log.xz | Bin 227680 -> 226272 bytes 09-build_abe-gdb/console.log.xz | Bin 38280 -> 37804 bytes 10-build_abe-qemu/console.log.xz | Bin 31952 -> 32112 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3580 -> 2712 bytes 13-check_regression/console.log.xz | Bin 9844 -> 5748 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 | 33 +- 13-check_regression/results.compare2 | 716 +------- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 26 + sumfiles/g++.log.xz | Bin 2672076 -> 2688404 bytes sumfiles/g++.sum | 136 +- sumfiles/gcc.log.xz | Bin 2240788 -> 2209604 bytes sumfiles/gcc.sum | 2714 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 886508 -> 887124 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201232 -> 201316 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 423860 -> 423648 bytes sumfiles/libstdc++.sum | 14 +- 41 files changed, 1673 insertions(+), 2219 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