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 3556e38fc2 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 70be6a9cbf 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards b6fd93a39c 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 74c31aa563 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards d32c42492e 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards d960a96983 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards b9750c177f 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 51779a06ff 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 77cfd0df53 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 6e4a7cb9de 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 36a0e4e05a 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 1bdd13438b 128: onsuccess: #1723: 1: Success after linux: 12 commits discards d5563b320e 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 3f309f1914 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 07ce9c1ecd 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 87e2dfc1ea 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 4d5dfd4176 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 1df33c9498 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards cf03a2e827 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards fc3fdd5549 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 6de09c03e7 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 04caa3c719 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 53efadb627 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 400f20d957 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 98d81b45a3 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 61405bbb26 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards ba9cc66280 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards fb819db57e 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 23a3f55f24 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 878de3f862 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 3ba2752e6c 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 51cc06e963 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards ff20b755f2 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards c3b0b70172 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 7d87d8a58e 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 4f2a496ec5 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 6f798d26e2 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards f2e49149e8 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 301d46a8b8 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 31e4713907 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 374ebc386f 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards b7b91b20a2 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 4154b53681 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 53e632b7e2 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 467f11c529 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards dc19f54cad 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 59bfaa8ecf 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 104f89d1f9 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 60d0fa4dee 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 55bcc472ca 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e20bcd47ea 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 4868458e4c 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards caf470bb0f 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards a67cb15a22 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards ebc3e9f42e 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards c797c88aed 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards ba07a48759 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 3b19e1c428 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 067019b5cf 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 013a1749c5 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards c1b3c5691a 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards eb177abd24 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b5071b8962 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fea82367bb 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 3d0d5c19b0 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 950592bfce 74: onsuccess: 1: Successful build after linux: 44 commits discards 59094c0eef 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards b7d7004577 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0fae71da31 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 3023a0db07 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 87cca07173 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 0687fbe3b5 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 146599258e 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 59da1be873 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d0800491b4 65: onsuccess: 1: Successful build after gcc: 4 commits discards 24e56b7f16 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3fef4b9de8 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 72ba669122 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards d18b82c9b0 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards ff5176ee52 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 76820e02a1 59: onsuccess: 1: Successful build after glibc: 2 commits discards 3a69d7ff09 58: onsuccess: 1: Successful build after binutils: 2 commits discards f7fb6afd44 57: onsuccess: 1: Successful build after gcc: 7 commits discards 529ce05fe8 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e9c3b5b879 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c2c403e4d9 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards e84009f544 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards d1f5d4c610 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards dd593def3f 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2cd03e1193 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4810fd7266 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a85b783f6d 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards c1386fbddc 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 388e4477ce 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 3e26cfd710 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3ccf0d5a4d 44: onsuccess: 1: Successful build after linux: 34 commits discards 2747a8c5d2 43: onsuccess: 1: Successful build after gcc: 2 commits discards 27d7d59d20 42: onsuccess: 1: Successful build after baseline build: no [...] discards 70231ce0c5 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c6257a0d22 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2e6a03e1c6 39: onsuccess: 1: Successful build after gcc: 2 commits new 4e5eeb2787 39: onsuccess: 1: Successful build after gcc: 2 commits new 85e24cf9ab 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b0a6ffba7b 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f11efd137c 42: onsuccess: 1: Successful build after baseline build: no [...] new 067c2e17bd 43: onsuccess: 1: Successful build after gcc: 2 commits new 04272e0d28 44: onsuccess: 1: Successful build after linux: 34 commits new a29484542a 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3b2bda828f 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 0c9af7dc14 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new afb1de8d40 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new a26103810a 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2dd370379f 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 702c2b4be7 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 69b18c878d 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 75894393de 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 92ea8b779e 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 2d57596b3d 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 87594c0f96 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6ede81134d 57: onsuccess: 1: Successful build after gcc: 7 commits new 5723c03b9e 58: onsuccess: 1: Successful build after binutils: 2 commits new 1d64d36c4d 59: onsuccess: 1: Successful build after glibc: 2 commits new 70fd01f8c0 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new c01854ba70 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 3c28b20584 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 345d390c5c 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d7b09ccb7f 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 20b9dd90be 65: onsuccess: 1: Successful build after gcc: 4 commits new 3d1654a860 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b2d3f05ce2 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bce4b9acdd 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 61c4dd3867 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 5b9b5840dc 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 2ec1836e1f 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 06c78be3e0 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cf408bda7a 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new ffb48cad6c 74: onsuccess: 1: Successful build after linux: 44 commits new 676430d9aa 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2dcd0bc190 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new d6f8afd6d0 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f232784a1c 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0d9f14d77d 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 9e3b924c9a 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new e18048507d 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 5205ee1dd2 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 3547d6ea80 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new b0ab24af11 84: onsuccess: 1: Success after gcc/glibc: 9 commits new aa96468e44 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new c2726ca53e 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 1157af0f51 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 4c3d4769f9 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new f5ff5ebc92 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new b266305685 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 962f8cf3a0 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new ae606a81f1 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 026a6f2351 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new c369fa1e37 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 0dea98c2ea 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new ffee6f3fdc 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new ac02ba651b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new d9a08227d2 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new e11835e128 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 7366a21d15 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new a57fbaa51a 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 939d8d35b1 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 6dd493a90e 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 8419a90bd1 104: onsuccess: #1697: 1: Success after gcc: 4 commits new b5c5530c80 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 49bcf2b16b 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new d53919b4a2 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 87bfe63fe0 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 63b58754c3 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new d8e97695e0 110: onsuccess: #1703: 1: Success after gcc: 6 commits new bf1f8dadf8 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 0bebcbe3d3 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 0b3abe612a 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 8d356d823e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 0259bae3cd 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 4dbf74e179 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new eaf2d444f5 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 69073bf3f5 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 9f1a9148bb 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 0da6989d6b 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 899cea9910 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new b19df5c513 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new b922365cb4 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 7791e7f5fc 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 28cb8ca259 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new c8da2d8f5a 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 6096f4593e 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 2afa7b5b35 128: onsuccess: #1723: 1: Success after linux: 12 commits new 780cbb3bad 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 3c33a8d422 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 383b3961de 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new ba01608552 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new cd217258b2 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 22e502d1d5 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 60926a7f6f 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 5e2fc0330d 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 53364f304a 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 3fae5e1ec9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new ccb31be952 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 11a6acb864 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 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 (3556e38fc2) \ 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 1704 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30112 -> 30436 bytes 04-build_abe-stage1/console.log.xz | Bin 90648 -> 90724 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9264 -> 9272 bytes 07-build_abe-glibc/console.log.xz | Bin 233912 -> 235260 bytes 08-build_abe-stage2/console.log.xz | Bin 223620 -> 225352 bytes 09-build_abe-gdb/console.log.xz | Bin 37124 -> 37824 bytes 10-build_abe-qemu/console.log.xz | Bin 31216 -> 31080 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2624 -> 2612 bytes 13-check_regression/console.log.xz | Bin 7276 -> 5972 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 8 +- 13-check_regression/mail-body.txt | 84 +- 13-check_regression/results.compare | 40 +- 13-check_regression/results.compare2 | 111 +- 13-check_regression/results.regressions | 40 +- 14-update_baseline/console.log | 66 +- 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 | 86 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 40 +- sumfiles/g++.log.xz | Bin 2651084 -> 2688184 bytes sumfiles/g++.sum | 146 +- sumfiles/gcc.log.xz | Bin 2203804 -> 2210948 bytes sumfiles/gcc.sum | 2394 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 881380 -> 895240 bytes sumfiles/gfortran.sum | 53 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201352 -> 201088 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 424028 -> 427332 bytes sumfiles/libstdc++.sum | 14 +- 43 files changed, 1555 insertions(+), 1601 deletions(-)