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 f947627d8b 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 0047edec0e 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards e44776f0a5 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards e08ba75132 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 9ac8c69ac1 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 5ccdd6eb68 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 293d1371a2 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 6ff1e817d3 128: onsuccess: #1723: 1: Success after linux: 12 commits discards d1f83bb36b 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards d794dccbe6 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 551885b74a 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards b5c9f60340 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards eadc6cb6d9 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards f8be085c91 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 53350f24dd 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards a3bbe97e23 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards ef38c224f9 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 9abe4ae97d 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards b884cfb6d4 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards a64d166a8e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 196e27a63d 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 389911a757 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 37bb4910e4 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards fd7d9cfd4e 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 2bcf469c33 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards daeee1dbbc 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards d6bed0104e 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards fb69b1bdbf 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards a18e14dbc0 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards c84f2ada02 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards d674b8091b 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 21ac4fe3c7 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards da28730984 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 06340d167d 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 17dc78508d 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 4848fa48dd 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 0af822ea43 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards a499219603 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 72566a8f26 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards c6e120d124 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 30dd009067 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 2ae48553b7 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards d1460e1dbc 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 8b868706e3 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards c0a2c28999 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards b4df54d214 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f6c9d4d319 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f0095f83b3 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 184d7ba509 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 0f601a17a7 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 09c5259ebf 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards a1895ebaf8 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards db34ef783b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 47ce4f7005 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards e89f46b1ac 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 6a02d0e2e0 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards c129a33b5c 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 4e5e25c28d 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cd01fe06e4 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a8b1177e90 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 7ae55a3179 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6d7d2b13c7 74: onsuccess: 1: Successful build after linux: 44 commits discards 12446be631 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 17c32382ed 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4438c295f0 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 5d4472896e 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards e29568e62f 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards ce0b5a658e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5fcdc3240d 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 700a05ccc1 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards afc5e3bd5a 65: onsuccess: 1: Successful build after gcc: 4 commits discards c771881e1e 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e517c1f8e0 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1f979a4932 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 29f36b22fd 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards dc86bf6554 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards f6a99105b9 59: onsuccess: 1: Successful build after glibc: 2 commits discards 4965195cc9 58: onsuccess: 1: Successful build after binutils: 2 commits discards 4aabd29bd5 57: onsuccess: 1: Successful build after gcc: 7 commits discards 2e86bc5d1b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cb9b48b4bd 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 778bf1040a 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 9e3c3fa207 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 2882bb9425 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards fd205bf7a7 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 37c8a1e2e7 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8ded437fee 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 62a1771201 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 1575bc6609 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0d36aebb5d 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 285b5419c8 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7a5243c049 44: onsuccess: 1: Successful build after linux: 34 commits discards 7f27eb6696 43: onsuccess: 1: Successful build after gcc: 2 commits discards 7b64acd497 42: onsuccess: 1: Successful build after baseline build: no [...] discards 6ca587de6b 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6fd60a76db 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards abee7caf2a 39: onsuccess: 1: Successful build after gcc: 2 commits discards 0a85dce391 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 642740a9e6 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0315a87d50 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e6dbd0a1c7 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f2f173a9bf 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8ed5ecd93d 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e07a7d6fbf 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f000cc928b 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0678105b29 39: onsuccess: 1: Successful build after gcc: 2 commits new c0028bb053 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 73de885dc7 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a863fc9b7b 42: onsuccess: 1: Successful build after baseline build: no [...] new 2695624ff4 43: onsuccess: 1: Successful build after gcc: 2 commits new 5d9217b605 44: onsuccess: 1: Successful build after linux: 34 commits new 50ca3134c2 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0a78622aae 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 9d4a99f32c 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3846049a5d 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new c9cae5e440 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0c51eedc44 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 23b966eb67 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f796f6c54e 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 6974365bae 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 82cbbdd406 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 10cc050718 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 539babac4d 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a9fb4df8e7 57: onsuccess: 1: Successful build after gcc: 7 commits new 5abeb7f8b7 58: onsuccess: 1: Successful build after binutils: 2 commits new f223e005cf 59: onsuccess: 1: Successful build after glibc: 2 commits new 22abb2bd66 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new f78266f670 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 67b2dacfd2 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new f25f3e40f6 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 662db299f3 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a36adaa6c5 65: onsuccess: 1: Successful build after gcc: 4 commits new cb9e0a37e5 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c0b3bce8e4 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e2123ad1ff 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a7c86ca794 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new e0b1fcdfad 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new fdf38ff121 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 0886163cd3 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a09d7745d1 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 2de4e25d3b 74: onsuccess: 1: Successful build after linux: 44 commits new 77355e5a52 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fa42e4c207 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 330d97e752 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1a74f92c4b 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new bbfc892d31 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new b7d263e262 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 4f2db75131 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new bf0e61a8a2 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 50542760f0 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 4a910b9c74 84: onsuccess: 1: Success after gcc/glibc: 9 commits new fd4518b8ef 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 3af36e3607 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 9872996cab 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 148cbe3c52 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new d4ee789dd0 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 125111f775 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new f4dee28b19 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new f776165aa0 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 968705e2f7 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new fbcc8d4d12 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new f1ab8d1c20 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 6096385cf5 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 088fe0d62e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new e6557f20cf 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 94dc3fbfb0 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new bc93c13682 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new bed1f92803 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 5b8d354101 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 33746d849f 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 69997dcb4e 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 3649664b80 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 527e6c40f7 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new c5950835da 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new b4e15c21ba 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new df7aff3880 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 684e810169 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 730f0cca20 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 9bd195a54c 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 0c43b8dba4 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new d3bd0e3a4d 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 1859cf8ba5 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 5be1758157 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 9af996124c 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 7f6a67db3b 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 13af915050 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 4bca6f5afb 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new c983184d78 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 964e9c8171 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 4051e83abf 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new fe83fba76e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 46d9964337 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new a7162c8ec0 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 86082833c2 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 8f626d671a 128: onsuccess: #1723: 1: Success after linux: 12 commits new 8f56bbbf1a 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 3ab9d126e9 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new c3b0a39992 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 958c5773ea 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 797b369356 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 57457afb31 134: onsuccess: #1730: 1: Success after binutils: 2 commits new ebe9ce02d7 135: onsuccess: #1733: 1: Success after binutils: 5 commits new b15ddc8013 136: onsuccess: #1735: 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 (f947627d8b) \ 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 1728 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30060 -> 30780 bytes 04-build_abe-stage1/console.log.xz | Bin 90836 -> 93196 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8468 -> 8820 bytes 07-build_abe-glibc/console.log.xz | Bin 234164 -> 235624 bytes 08-build_abe-stage2/console.log.xz | Bin 225676 -> 227680 bytes 09-build_abe-gdb/console.log.xz | Bin 37700 -> 38280 bytes 10-build_abe-qemu/console.log.xz | Bin 31384 -> 31952 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2676 -> 3580 bytes 13-check_regression/console.log.xz | Bin 5156 -> 9844 bytes 13-check_regression/results.compare | 24 +- 13-check_regression/results.compare2 | 710 ++++++++- 14-update_baseline/console.log | 70 +- 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 43 +- sumfiles/g++.log.xz | Bin 2662172 -> 2672076 bytes sumfiles/g++.sum | 675 ++++++++- sumfiles/gcc.log.xz | Bin 2225460 -> 2240788 bytes sumfiles/gcc.sum | 2575 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 886288 -> 886508 bytes sumfiles/gfortran.sum | 48 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201216 -> 201232 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 432056 -> 423860 bytes sumfiles/libstdc++.sum | 17 +- 41 files changed, 2745 insertions(+), 1463 deletions(-)