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 56a994cf26 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards ae4bfd7383 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards adc313fc93 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 6ed77c9892 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 8e81da2a1d 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards cb06c41c83 128: onsuccess: #1723: 1: Success after linux: 12 commits discards a02908b59f 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 76695809f6 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards f8d196f40f 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 9b7bdd62aa 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards bff5c9c269 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards cca36a37bd 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards f1f269d320 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 4512d42f8e 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards a640f2740c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards af980d7369 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards cf4e69deda 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards b52aa747ee 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards eb82908b84 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 085777e18b 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 02a86f5218 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards e343e3138c 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards ac14020fe5 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 24772e1c12 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 8e091edea4 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 0f4884d74f 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards d46e544ac1 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 6681106d52 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 4cb90d010b 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 8ae3385969 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards ad682a74d5 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 096e6f170c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 927e923353 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards c802c980d5 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 3a2f8103ca 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 16446b4ba1 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 1445de16d3 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 8347a2e989 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 42e90973d5 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 2053d71bb4 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards f6ffef7bbb 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards c60525cac9 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 906d436a3f 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 6dc890e903 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards abd7ff912b 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1e1c254687 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 9d433a72f5 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 3b89838161 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 6fe3e132d3 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards b173caf08f 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards ddccf1570f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 7e69595ec8 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 7e1d87e13a 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards dc08a2901b 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 24e07e9d0a 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards f379a5f9a6 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9a8b0cfd4f 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 89c1e6e0e2 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards bf1e9d44f6 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a64fe3ea40 74: onsuccess: 1: Successful build after linux: 44 commits discards 2687edcc92 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 85a222c352 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3c67c8fef5 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 142ae5b8af 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 7939baffd8 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards c9256ea93f 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b088863092 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4779212292 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 8c17756cc5 65: onsuccess: 1: Successful build after gcc: 4 commits discards b69d806b50 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e6cf4b821d 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2c3b781f65 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 0ee58f8a08 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 27eb044a2d 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards d3727e8022 59: onsuccess: 1: Successful build after glibc: 2 commits discards 1d1fe1df27 58: onsuccess: 1: Successful build after binutils: 2 commits discards d74baeaff2 57: onsuccess: 1: Successful build after gcc: 7 commits discards 9fe33e42a4 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 56ab5cc245 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0b6215bab0 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards ecbc18fe77 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards ad78684ee2 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards f63454fa51 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e68091f71a 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2b1b3d0e74 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 450861638c 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 949d79fa47 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 90d13d50b6 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 74e5ddb1d5 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 101c24b380 44: onsuccess: 1: Successful build after linux: 34 commits discards 7066c7ba26 43: onsuccess: 1: Successful build after gcc: 2 commits discards 65433570c3 42: onsuccess: 1: Successful build after baseline build: no [...] discards 49a24c29cb 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 912fd951b3 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bc4f2f45a7 39: onsuccess: 1: Successful build after gcc: 2 commits discards 0a385da82f 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ea3e975556 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a2bfde5405 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d9131e5bcd 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 27fd444176 34: onsuccess: 1: Successful build after gcc: 3 commits discards 0083204486 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5d86c2ab3f 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5d6aec311c 34: onsuccess: 1: Successful build after gcc: 3 commits new 72255ec45f 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ef421f508c 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9a5d715a59 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 002253ad48 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 949b7e32e9 39: onsuccess: 1: Successful build after gcc: 2 commits new a164305c89 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1eeb8144ed 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4085049c1d 42: onsuccess: 1: Successful build after baseline build: no [...] new 978f1d3b7f 43: onsuccess: 1: Successful build after gcc: 2 commits new 79531a3c67 44: onsuccess: 1: Successful build after linux: 34 commits new 2a91e6ceb7 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 99bf79b195 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new dff39ffc29 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new be9523ad0a 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new df1b0b6114 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 594837cd36 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1264519376 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8fbee3dc1a 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 0b157a3efd 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 6a2433cfac 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 209cdcc44c 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cc91d861be 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d1ca9b677c 57: onsuccess: 1: Successful build after gcc: 7 commits new 39a2fcb086 58: onsuccess: 1: Successful build after binutils: 2 commits new fa36dcc511 59: onsuccess: 1: Successful build after glibc: 2 commits new 954955dd53 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 0746980260 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 69ec88c9f0 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 0e6cacb9f5 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4b98a34e6c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fc0fe2f208 65: onsuccess: 1: Successful build after gcc: 4 commits new c4a99d4c13 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1a40502db1 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new da8e7e6aea 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3cda765e69 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new e9fe32e55c 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 88626be65a 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new faabcbadde 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 820d563825 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new a5b493e873 74: onsuccess: 1: Successful build after linux: 44 commits new 4c07d01554 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e9166b494a 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 7134254f05 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a672e3a023 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 15abad27df 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 8a88352cfe 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 8459d4e509 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 0781366441 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new a3eb9db509 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new e419e29d2c 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 11ff7a576b 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 1b34f5a7a6 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new acbc10b443 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new fb1884c133 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 2591d7c3fa 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 96fa460a3d 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c12391cd13 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new ee0c2a34cc 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new f33687115a 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new f6c9c7f4ec 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 97f0cd5db6 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new b4254341a1 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 3a9a36b606 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new bed7d2824f 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 52d0e98d2c 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new e5c2e8e508 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 4d6d24a803 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 79afc9e694 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new d701a4c99c 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 0290228229 104: onsuccess: #1697: 1: Success after gcc: 4 commits new e9cab64c93 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 682ab0cda3 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 5132abcd1c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 5274176c1e 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new e3c8825b23 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 7a8a38de58 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 3ac885162d 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 248c317a99 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 1fd9c310bd 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new f4b4cda71f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new cfb8cbb429 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 13de86ef61 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 286e312972 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 0cac63eba7 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new bd3986a177 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 41a5f082c7 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 7b4cbd59d6 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 3cbb4cc595 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new bcf3bc1609 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 3b4855312d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 93f848d9bf 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new a5ae2c6647 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 7c47a13703 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new a1b9f4b930 128: onsuccess: #1723: 1: Success after linux: 12 commits new c9bd75fe2a 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 08d565d25c 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 3938bfe61a 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new c34ac46621 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new b5f0c3e833 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new dac2338596 134: onsuccess: #1730: 1: Success after binutils: 2 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 (56a994cf26) \ 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 1736 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30520 -> 30176 bytes 04-build_abe-stage1/console.log.xz | Bin 90528 -> 91032 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8296 -> 8416 bytes 07-build_abe-glibc/console.log.xz | Bin 234412 -> 233816 bytes 08-build_abe-stage2/console.log.xz | Bin 224376 -> 223592 bytes 09-build_abe-gdb/console.log.xz | Bin 37524 -> 37420 bytes 10-build_abe-qemu/console.log.xz | Bin 31252 -> 31276 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2660 -> 2680 bytes 13-check_regression/console.log.xz | Bin 6120 -> 5260 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 52 +- 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 50 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 54 +- mail/mail-subject.txt | 2 +- manifest.sh | 27 +- results | 26 - sumfiles/g++.log.xz | Bin 2664548 -> 2657872 bytes sumfiles/g++.sum | 114 +- sumfiles/gcc.log.xz | Bin 2229432 -> 2240832 bytes sumfiles/gcc.sum | 2734 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 882812 -> 887508 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201100 -> 201104 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 420620 -> 428700 bytes sumfiles/libstdc++.sum | 16 +- 41 files changed, 1572 insertions(+), 1705 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions