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 a8f8407162 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards c2ce308a5c 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards d82fb97655 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards ee62460293 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 7a735e6a99 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 1a9f4bcc49 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 3a64834055 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 345d1df94e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards f6b7474171 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 394ad9a0d4 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards ba5142408f 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 1a568c5b74 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards b64a40bfb5 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards d770085d1e 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards ce1e672d3f 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards ed534a3e8b 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 89b3a60c53 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 1be46a29d2 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards e3429b2f27 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 2e1874e447 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 6905c13af5 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards ef220d6186 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards fbabb89b6e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 5e39eeded5 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 6574bbeab9 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 0fa8e2d1d1 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 527ffffd29 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 50944e1bd0 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards c83cac278c 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 93c899aeaa 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 0fed3f0fb3 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 7df3d9b8fb 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards d5af97c474 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards afb44ee523 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards f1f9cf3960 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards e173ca6e1f 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards abbac48c3e 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards ba114e188b 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 3a7565930a 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 928327f1c7 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards f8ef13a549 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards b6fa5c0bf6 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 1e162a93be 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards dc0f9dc544 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 1c80e341a3 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 534e1813de 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 22eea54203 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards cad6b3cd75 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 666ec359d5 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 165f61d354 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 6023e9bcb6 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards d16d2608ff 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards e5e3fdfe5d 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards b8e46e00cd 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards d42f46a81f 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 18af5fd077 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 9b379bdd92 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards f14dbc5ceb 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards edfdfe8134 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 63526d5e65 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 3f7df73ca9 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4f1517cdcd 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 032c017429 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 9abc42b661 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3fa513ed46 74: onsuccess: 1: Successful build after linux: 44 commits discards cafa787998 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards b739d7cf1a 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e1e257906e 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards a0d5ac626f 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 42d01a2a11 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards c78cfec73d 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bff83260c0 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 452298937b 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e4e9594e4f 65: onsuccess: 1: Successful build after gcc: 4 commits discards ed7f9df0bd 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6adef7b11c 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 941db5f332 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 1114777e09 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 422b03c34c 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 111cd4b3eb 59: onsuccess: 1: Successful build after glibc: 2 commits discards 80d8097cfd 58: onsuccess: 1: Successful build after binutils: 2 commits discards 2d5cac2c10 57: onsuccess: 1: Successful build after gcc: 7 commits discards 5b55016466 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1f39d4b9b8 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 577fb92abb 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 8e8dc7870a 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 13ada7dc8e 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards fbe5771b81 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b1e0a02197 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 044244907a 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d0bb452eff 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards d0452093d4 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8501f1e253 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 70e89371b8 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 65927593db 44: onsuccess: 1: Successful build after linux: 34 commits discards 168e5a68f8 43: onsuccess: 1: Successful build after gcc: 2 commits discards 3ce9ae241c 42: onsuccess: 1: Successful build after baseline build: no [...] discards abebb6d9b7 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5b1de2d0fa 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9d6a27ac60 39: onsuccess: 1: Successful build after gcc: 2 commits discards 99a1e615c2 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 769fb11f9f 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2e6a03e1c6 39: onsuccess: 1: Successful build after gcc: 2 commits new c6257a0d22 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 70231ce0c5 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 27d7d59d20 42: onsuccess: 1: Successful build after baseline build: no [...] new 2747a8c5d2 43: onsuccess: 1: Successful build after gcc: 2 commits new 3ccf0d5a4d 44: onsuccess: 1: Successful build after linux: 34 commits new 3e26cfd710 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 388e4477ce 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new c1386fbddc 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a85b783f6d 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 4810fd7266 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2cd03e1193 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dd593def3f 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d1f5d4c610 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new e84009f544 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new c2c403e4d9 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new e9c3b5b879 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 529ce05fe8 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f7fb6afd44 57: onsuccess: 1: Successful build after gcc: 7 commits new 3a69d7ff09 58: onsuccess: 1: Successful build after binutils: 2 commits new 76820e02a1 59: onsuccess: 1: Successful build after glibc: 2 commits new ff5176ee52 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new d18b82c9b0 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 72ba669122 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 3fef4b9de8 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 24e56b7f16 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d0800491b4 65: onsuccess: 1: Successful build after gcc: 4 commits new 59da1be873 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 146599258e 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0687fbe3b5 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 87cca07173 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 3023a0db07 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 0fae71da31 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new b7d7004577 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 59094c0eef 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 950592bfce 74: onsuccess: 1: Successful build after linux: 44 commits new 3d0d5c19b0 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fea82367bb 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new b5071b8962 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new eb177abd24 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c1b3c5691a 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 013a1749c5 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 067019b5cf 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 3b19e1c428 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new ba07a48759 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new c797c88aed 84: onsuccess: 1: Success after gcc/glibc: 9 commits new ebc3e9f42e 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new a67cb15a22 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new caf470bb0f 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 4868458e4c 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new e20bcd47ea 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 55bcc472ca 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 60d0fa4dee 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 104f89d1f9 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 59bfaa8ecf 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new dc19f54cad 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 467f11c529 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 53e632b7e2 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 4154b53681 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new b7b91b20a2 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 374ebc386f 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 31e4713907 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 301d46a8b8 101: onsuccess: #1693: 1: Success after glibc: 14 commits new f2e49149e8 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 6f798d26e2 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 4f2a496ec5 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 7d87d8a58e 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new c3b0b70172 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new ff20b755f2 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 51cc06e963 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 3ba2752e6c 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 878de3f862 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 23a3f55f24 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new fb819db57e 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new ba9cc66280 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 61405bbb26 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 98d81b45a3 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 400f20d957 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 53efadb627 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 04caa3c719 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 6de09c03e7 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new fc3fdd5549 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new cf03a2e827 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 1df33c9498 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 4d5dfd4176 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 87e2dfc1ea 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 07ce9c1ecd 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 3f309f1914 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new d5563b320e 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 1bdd13438b 128: onsuccess: #1723: 1: Success after linux: 12 commits new 36a0e4e05a 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 6e4a7cb9de 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 77cfd0df53 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 51779a06ff 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new b9750c177f 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new d960a96983 134: onsuccess: #1730: 1: Success after binutils: 2 commits new d32c42492e 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 74c31aa563 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new b6fd93a39c 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 70be6a9cbf 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 3556e38fc2 139: onsuccess: #1738: 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 (a8f8407162) \ 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 1724 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30672 -> 30112 bytes 04-build_abe-stage1/console.log.xz | Bin 91800 -> 90648 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8636 -> 9264 bytes 07-build_abe-glibc/console.log.xz | Bin 233968 -> 233912 bytes 08-build_abe-stage2/console.log.xz | Bin 225092 -> 223620 bytes 09-build_abe-gdb/console.log.xz | Bin 37368 -> 37124 bytes 10-build_abe-qemu/console.log.xz | Bin 31036 -> 31216 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3928 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2884 -> 2624 bytes 13-check_regression/console.log.xz | Bin 7280 -> 7276 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 8 +- 13-check_regression/mail-body.txt | 76 +- 13-check_regression/results.compare | 44 +- 13-check_regression/results.compare2 | 118 +- 13-check_regression/results.regressions | 44 +- 14-update_baseline/console.log | 68 +- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 78 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 44 +- sumfiles/g++.log.xz | Bin 2661340 -> 2651084 bytes sumfiles/g++.sum | 183 ++- sumfiles/gcc.log.xz | Bin 2233748 -> 2203804 bytes sumfiles/gcc.sum | 2602 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 886740 -> 881380 bytes sumfiles/gfortran.sum | 56 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201260 -> 201352 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 430752 -> 424028 bytes sumfiles/libstdc++.sum | 14 +- 45 files changed, 1786 insertions(+), 1637 deletions(-)