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 0a22431dae 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 013113cbee 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 4cb3126a8a 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 84030b4d11 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 8c2945be83 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 5ba2f24360 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 8952b22171 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards fdd7e46a3f 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 059ffd608f 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards fcd3fe2172 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards e459f1cacb 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 88734aa100 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 1dbfea50ce 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 9505aec82c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 2c6d21b815 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 6c80fcb6bd 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 4b9e98e0a0 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards c8a6731333 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 35af6bcad8 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 93ee57d464 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 9fb0bc5ed1 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards c9f0b437c3 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards d1a16e537a 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards bd8c037d80 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 6bab157a21 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 5cb9278f0c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 6c7564e93c 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards d9bd7c85e7 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 96c180a71e 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards cd65d0d1d9 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards bba7b5b216 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 86fb4b6257 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards b6917ec175 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards f5bc5cf1c5 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 0dde784f68 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 7effab9237 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards be5844939f 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 579e25874c 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards ba7b3e2c93 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards a37220ebb6 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards c2092b172e 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 1af058877e 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards e5ee22d0ba 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 666a6bda1f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards c5fdec5b54 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 59584f3101 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 5490980d00 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 4c5ff0d456 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 5a7a37a4dc 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 58ddf02179 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards db1ce0e63d 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 1bb20f6f3b 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards ddce83a39d 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 30aaf8cfa8 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 83e5459cd5 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 1651600d51 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards aa26514184 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards dcf75902bb 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c49fc3ccd1 74: onsuccess: 1: Successful build after linux: 44 commits discards bfe5e36f01 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards afa62a4f0e 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 89a1264122 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 404a90c18a 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 7b5606202a 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 321f404665 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 67c4a540a2 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4a1617da05 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0823239dd6 65: onsuccess: 1: Successful build after gcc: 4 commits discards 55dbdcc585 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0b58e4a58d 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9e30816b87 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards e9061da353 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 7f17a61e9d 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 63c2676913 59: onsuccess: 1: Successful build after glibc: 2 commits discards f58f7f37c1 58: onsuccess: 1: Successful build after binutils: 2 commits discards 319e0ffe09 57: onsuccess: 1: Successful build after gcc: 7 commits discards 18878b7c1c 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d560ce74c7 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7896c6ad83 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 329f3ad1f0 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 3ad6c32c18 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 7bf360a542 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards fef6a86332 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 37744d659a 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f82a3c782c 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards b196af905b 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 80e5c5134e 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards b50bf176cc 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4b6088981e 44: onsuccess: 1: Successful build after linux: 34 commits discards ed9f49ce24 43: onsuccess: 1: Successful build after gcc: 2 commits discards 70a5d34c39 42: onsuccess: 1: Successful build after baseline build: no [...] discards 3b3cb363e6 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c4f9595de7 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 12fd294422 39: onsuccess: 1: Successful build after gcc: 2 commits discards fc3e18227f 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f1b953aa59 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 16fdfe7c91 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 623c0e53af 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d23772b4de 34: onsuccess: 1: Successful build after gcc: 3 commits discards af4055714f 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 11e92cb114 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new d85cd413ad 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 0083204486 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 27fd444176 34: onsuccess: 1: Successful build after gcc: 3 commits new d9131e5bcd 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a2bfde5405 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ea3e975556 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0a385da82f 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bc4f2f45a7 39: onsuccess: 1: Successful build after gcc: 2 commits new 912fd951b3 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 49a24c29cb 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 65433570c3 42: onsuccess: 1: Successful build after baseline build: no [...] new 7066c7ba26 43: onsuccess: 1: Successful build after gcc: 2 commits new 101c24b380 44: onsuccess: 1: Successful build after linux: 34 commits new 74e5ddb1d5 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 90d13d50b6 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 949d79fa47 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 450861638c 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 2b1b3d0e74 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e68091f71a 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f63454fa51 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ad78684ee2 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new ecbc18fe77 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 0b6215bab0 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 56ab5cc245 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9fe33e42a4 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d74baeaff2 57: onsuccess: 1: Successful build after gcc: 7 commits new 1d1fe1df27 58: onsuccess: 1: Successful build after binutils: 2 commits new d3727e8022 59: onsuccess: 1: Successful build after glibc: 2 commits new 27eb044a2d 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 0ee58f8a08 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 2c3b781f65 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new e6cf4b821d 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b69d806b50 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8c17756cc5 65: onsuccess: 1: Successful build after gcc: 4 commits new 4779212292 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b088863092 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c9256ea93f 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7939baffd8 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 142ae5b8af 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 3c67c8fef5 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 85a222c352 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2687edcc92 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new a64fe3ea40 74: onsuccess: 1: Successful build after linux: 44 commits new bf1e9d44f6 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 89c1e6e0e2 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 9a8b0cfd4f 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f379a5f9a6 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 24e07e9d0a 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new dc08a2901b 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 7e1d87e13a 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 7e69595ec8 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new ddccf1570f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new b173caf08f 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 6fe3e132d3 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 3b89838161 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 9d433a72f5 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 1e1c254687 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new abd7ff912b 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 6dc890e903 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 906d436a3f 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new c60525cac9 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new f6ffef7bbb 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 2053d71bb4 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 42e90973d5 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 8347a2e989 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 1445de16d3 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 16446b4ba1 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 3a2f8103ca 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new c802c980d5 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 927e923353 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 096e6f170c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new ad682a74d5 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 8ae3385969 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 4cb90d010b 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 6681106d52 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new d46e544ac1 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 0f4884d74f 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 8e091edea4 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 24772e1c12 110: onsuccess: #1703: 1: Success after gcc: 6 commits new ac14020fe5 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new e343e3138c 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 02a86f5218 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 085777e18b 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new eb82908b84 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new b52aa747ee 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new cf4e69deda 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new af980d7369 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new a640f2740c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 4512d42f8e 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new f1f269d320 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new cca36a37bd 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new bff5c9c269 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 9b7bdd62aa 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new f8d196f40f 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 76695809f6 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new a02908b59f 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new cb06c41c83 128: onsuccess: #1723: 1: Success after linux: 12 commits new 8e81da2a1d 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 6ed77c9892 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new adc313fc93 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new ae4bfd7383 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 56a994cf26 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...]
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 (0a22431dae) \ 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 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30256 -> 30520 bytes 04-build_abe-stage1/console.log.xz | Bin 91028 -> 90528 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8304 -> 8296 bytes 07-build_abe-glibc/console.log.xz | Bin 234500 -> 234412 bytes 08-build_abe-stage2/console.log.xz | Bin 224160 -> 224376 bytes 09-build_abe-gdb/console.log.xz | Bin 37428 -> 37524 bytes 10-build_abe-qemu/console.log.xz | Bin 31256 -> 31252 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2776 -> 2660 bytes 13-check_regression/console.log.xz | Bin 6028 -> 6120 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 52 +- 13-check_regression/results.compare | 26 +- 13-check_regression/results.compare2 | 48 +- 13-check_regression/results.regressions | 26 +- 14-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 54 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 26 +- sumfiles/g++.log.xz | Bin 2680968 -> 2664548 bytes sumfiles/g++.sum | 148 +- sumfiles/gcc.log.xz | Bin 2202728 -> 2229432 bytes sumfiles/gcc.sum | 2412 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 884228 -> 882812 bytes sumfiles/gfortran.sum | 48 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201232 -> 201100 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422612 -> 420620 bytes sumfiles/libstdc++.sum | 16 +- 42 files changed, 1524 insertions(+), 1440 deletions(-)