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 dac2338596 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards b5f0c3e833 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards c34ac46621 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 3938bfe61a 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 08d565d25c 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards c9bd75fe2a 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards a1b9f4b930 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 7c47a13703 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards a5ae2c6647 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 93f848d9bf 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 3b4855312d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards bcf3bc1609 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 3cbb4cc595 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 7b4cbd59d6 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 41a5f082c7 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards bd3986a177 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 0cac63eba7 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 286e312972 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 13de86ef61 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards cfb8cbb429 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards f4b4cda71f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 1fd9c310bd 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 248c317a99 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 3ac885162d 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 7a8a38de58 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards e3c8825b23 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 5274176c1e 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 5132abcd1c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 682ab0cda3 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards e9cab64c93 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 0290228229 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards d701a4c99c 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 79afc9e694 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 4d6d24a803 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards e5c2e8e508 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 52d0e98d2c 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards bed7d2824f 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 3a9a36b606 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards b4254341a1 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 97f0cd5db6 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards f6c9c7f4ec 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards f33687115a 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards ee0c2a34cc 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards c12391cd13 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 96fa460a3d 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2591d7c3fa 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards fb1884c133 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards acbc10b443 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 1b34f5a7a6 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 11ff7a576b 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards e419e29d2c 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards a3eb9db509 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 0781366441 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 8459d4e509 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 8a88352cfe 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 15abad27df 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards a672e3a023 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7134254f05 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e9166b494a 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 4c07d01554 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a5b493e873 74: onsuccess: 1: Successful build after linux: 44 commits discards 820d563825 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards faabcbadde 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 88626be65a 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards e9fe32e55c 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 3cda765e69 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards da8e7e6aea 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1a40502db1 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c4a99d4c13 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards fc0fe2f208 65: onsuccess: 1: Successful build after gcc: 4 commits discards 4b98a34e6c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0e6cacb9f5 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 69ec88c9f0 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 0746980260 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 954955dd53 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards fa36dcc511 59: onsuccess: 1: Successful build after glibc: 2 commits discards 39a2fcb086 58: onsuccess: 1: Successful build after binutils: 2 commits discards d1ca9b677c 57: onsuccess: 1: Successful build after gcc: 7 commits discards cc91d861be 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 209cdcc44c 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6a2433cfac 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 0b157a3efd 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 8fbee3dc1a 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 1264519376 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 594837cd36 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards df1b0b6114 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards be9523ad0a 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards dff39ffc29 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 99bf79b195 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 2a91e6ceb7 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 79531a3c67 44: onsuccess: 1: Successful build after linux: 34 commits discards 978f1d3b7f 43: onsuccess: 1: Successful build after gcc: 2 commits discards 4085049c1d 42: onsuccess: 1: Successful build after baseline build: no [...] discards 1eeb8144ed 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a164305c89 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 949b7e32e9 39: onsuccess: 1: Successful build after gcc: 2 commits discards 002253ad48 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9a5d715a59 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ef421f508c 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 72255ec45f 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5d6aec311c 34: onsuccess: 1: Successful build after gcc: 3 commits new 9e4abd1d9c 34: onsuccess: 1: Successful build after gcc: 3 commits new e6dbd0a1c7 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0315a87d50 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 642740a9e6 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0a85dce391 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new abee7caf2a 39: onsuccess: 1: Successful build after gcc: 2 commits new 6fd60a76db 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6ca587de6b 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7b64acd497 42: onsuccess: 1: Successful build after baseline build: no [...] new 7f27eb6696 43: onsuccess: 1: Successful build after gcc: 2 commits new 7a5243c049 44: onsuccess: 1: Successful build after linux: 34 commits new 285b5419c8 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0d36aebb5d 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 1575bc6609 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 62a1771201 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 8ded437fee 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 37c8a1e2e7 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fd205bf7a7 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2882bb9425 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 9e3c3fa207 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 778bf1040a 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new cb9b48b4bd 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2e86bc5d1b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4aabd29bd5 57: onsuccess: 1: Successful build after gcc: 7 commits new 4965195cc9 58: onsuccess: 1: Successful build after binutils: 2 commits new f6a99105b9 59: onsuccess: 1: Successful build after glibc: 2 commits new dc86bf6554 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 29f36b22fd 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 1f979a4932 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new e517c1f8e0 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c771881e1e 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new afc5e3bd5a 65: onsuccess: 1: Successful build after gcc: 4 commits new 700a05ccc1 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 5fcdc3240d 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ce0b5a658e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e29568e62f 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 5d4472896e 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 4438c295f0 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 17c32382ed 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 12446be631 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 6d7d2b13c7 74: onsuccess: 1: Successful build after linux: 44 commits new 7ae55a3179 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a8b1177e90 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new cd01fe06e4 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4e5e25c28d 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c129a33b5c 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 6a02d0e2e0 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new e89f46b1ac 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 47ce4f7005 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new db34ef783b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new a1895ebaf8 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 09c5259ebf 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 0f601a17a7 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 184d7ba509 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new f0095f83b3 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new f6c9d4d319 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new b4df54d214 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c0a2c28999 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 8b868706e3 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new d1460e1dbc 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 2ae48553b7 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 30dd009067 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new c6e120d124 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 72566a8f26 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new a499219603 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 0af822ea43 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 4848fa48dd 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 17dc78508d 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 06340d167d 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new da28730984 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 21ac4fe3c7 104: onsuccess: #1697: 1: Success after gcc: 4 commits new d674b8091b 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new c84f2ada02 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new a18e14dbc0 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new fb69b1bdbf 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new d6bed0104e 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new daeee1dbbc 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 2bcf469c33 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new fd7d9cfd4e 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 37bb4910e4 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 389911a757 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 196e27a63d 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new a64d166a8e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new b884cfb6d4 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 9abe4ae97d 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new ef38c224f9 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new a3bbe97e23 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 53350f24dd 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new f8be085c91 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new eadc6cb6d9 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new b5c9f60340 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 551885b74a 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new d794dccbe6 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new d1f83bb36b 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 6ff1e817d3 128: onsuccess: #1723: 1: Success after linux: 12 commits new 293d1371a2 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 5ccdd6eb68 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 9ac8c69ac1 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new e08ba75132 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new e44776f0a5 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 0047edec0e 134: onsuccess: #1730: 1: Success after binutils: 2 commits new f947627d8b 135: onsuccess: #1733: 1: Success after binutils: 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 (dac2338596) \ 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 1688 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30176 -> 30060 bytes 04-build_abe-stage1/console.log.xz | Bin 91032 -> 90836 bytes 06-build_abe-linux/console.log.xz | Bin 8416 -> 8468 bytes 07-build_abe-glibc/console.log.xz | Bin 233816 -> 234164 bytes 08-build_abe-stage2/console.log.xz | Bin 223592 -> 225676 bytes 09-build_abe-gdb/console.log.xz | Bin 37420 -> 37700 bytes 10-build_abe-qemu/console.log.xz | Bin 31276 -> 31384 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2680 -> 2676 bytes 13-check_regression/console.log.xz | Bin 5260 -> 5156 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 31 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- sumfiles/g++.log.xz | Bin 2657872 -> 2662172 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2240832 -> 2225460 bytes sumfiles/gcc.sum | 2148 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 887508 -> 886288 bytes sumfiles/gfortran.sum | 10 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201104 -> 201216 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 428700 -> 432056 bytes sumfiles/libstdc++.sum | 8 +- 36 files changed, 1179 insertions(+), 1238 deletions(-)