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 5411faeab38 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 249b837b538 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 78f1b366b5f 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 20930657385 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards 013981500fc 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards f6b70a11682 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards f169656c45a 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards b674ff1fd2b 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 1f89fb33f89 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 5793db3a30c 194: onsuccess: #1995: 1: Success after linux: 517 commits discards b8fd1a9eb1f 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards a12a9a808f5 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards ce5f601edc2 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards badb7c9feec 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards ad98271b740 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards a3b0a674595 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards e1ad1d133bc 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards ccf5fa33a88 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards f90cf6f7b5f 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 2b1661e804d 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 6aa95f20b9c 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards feaf06b5c1e 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 58f5847462f 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards ee8becc9926 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards 7627dc38d2c 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards bf5659de77b 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards aee6538bc02 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards 070f9ac152e 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 25be8bed68e 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 48502d3eb32 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards 71e13c77a26 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 6f6f2891be4 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards e7cefe927e8 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 79e1aaa8a9f 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards 56f204566cc 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards d93b07c912f 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards a252871ea26 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards 22c0f8e05a6 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 1af88c67a59 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 566ebd2708f 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 4aac7d53d84 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 8d1dceb8872 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards 87f90e512fa 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards da36dec5b03 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 2ab3bb8e1be 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards da4b78250aa 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 830c483fa40 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards b85b9b893e3 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards ba9c1b44751 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 279759d98e8 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards fecb5e9e32d 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 35655de883d 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 1c64a62f765 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards f44a4acccd9 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 7977de97b36 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards 67799e29512 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards db05e170540 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards b39cca58b8f 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 51833389a24 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 92a39af8577 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 5fc8f848f3d 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 48e5255479f 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards 0832e7bafd8 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards d8bce6c323d 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards e8aacbf0d8d 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 35fa160ef9a 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards 23bf1e78dc6 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 128a9ab29f9 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards d3c0b0c5516 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards ae5dcc76e82 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards fd1655e4820 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards 70ef2165ee3 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards c44d5e8505e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards fe94464f4bc 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards d999b187b57 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards b62bfb13577 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 4ac05586fbb 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards 268ea654e88 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards d3fad9acbba 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards ed6053661d2 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards f195fda10d7 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards ed20f9156ec 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards 52482adb57b 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards 32509b2c86a 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards ed380184fd9 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards c4bbae0f9f9 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards a1b09553ac5 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards d74bdea9a5b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards 7ffd323b767 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards 95e6e525678 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 200a5c73be4 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] discards 63ea3e7faef 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] discards f58ea2a7a69 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] discards 2445194b4ea 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 9bc05162427 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] discards 1a4add35a41 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] discards d1a8e808ff8 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] discards 55f8cddb17d 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/ [...] discards f9d8a00bc1b 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38edde [...] discards bbf599fc724 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards d5b81a3cca0 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/ [...] new 49234ed522f 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/ [...] new 47fd8c263e7 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 4e4395e9d97 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38edde [...] new 2b3088e7d77 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/ [...] new f8ff3de59e9 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] new 282e475aac0 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] new 842535b98d1 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] new 83f7638bc32 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 27da207dac4 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] new c27d63c6cb0 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new 47c88926839 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new 69fb5e846ef 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 61ef0113af1 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new 5e5201b17e5 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new 34c6ed1de52 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new e597713fa0e 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new 9481b8f8df5 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new 46e17865c22 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new f0c4e72f2cd 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 64664ceb655 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new df360c70027 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new 032282a61bd 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 06907812d85 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new 22b474441d7 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new f4c06da0285 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new bf4ef2923a5 128: onsuccess: #1723: 1: Success after linux: 12 commits new 2d2c032a7d7 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new 6ac87e913dc 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 86129a36b4e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new 383c2dd25b8 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new cd94950c266 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 7d3db76d338 134: onsuccess: #1730: 1: Success after binutils: 2 commits new a60701c1d6e 135: onsuccess: #1733: 1: Success after binutils: 5 commits new f8350af317d 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new 1740955380d 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 554ef4826e9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new 45de75506a6 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 3b7f82a508e 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new fb123cc2e1f 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 3c111697a77 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new 24b7650b403 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 39ea47b24ea 144: onsuccess: #1743: 1: Success after glibc: 2 commits new b781efa3451 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new bc0ff329bf4 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 251b93d7294 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new d3519a8fae0 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 8930c26bd79 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 3fef091aa50 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 4a77ae27c94 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 54d90205bc7 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 3fd59454612 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 6df43c0609c 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 81c06cb3175 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new 00781161255 156: onsuccess: #1757: 1: Success after gcc: 4 commits new d849b57fd97 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new d26a9f728e0 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new 544108404a0 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new ff2f483a590 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new baa007db1c5 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 95dfabf6019 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 64010928414 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new a34c6ef6cca 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 52174d11a3c 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new 15a0342147f 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new d5fefc2a98a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 732951a62a9 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new ab749d2c9f2 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 2e660dbf07e 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 915030173c5 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 49f75e5035d 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new c0ecc6916e0 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 43d0fc1f800 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new 5f250333fb0 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new 6c8d7c407b0 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new 0bb82089f2f 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new da224c2d9f7 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new 49812204363 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 14840d10696 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new b48e600079d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 006f4741437 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new c21143c79cf 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 5d291b385f9 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new 0fc93c7daab 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new bb1d43114ea 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 286e2acec93 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 8e4dd236f6a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 9180933d312 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 3411394b65d 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new 3283bc82586 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new 6549199210e 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new e6266278aba 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 028706a9f53 194: onsuccess: #1995: 1: Success after linux: 517 commits new aca584e8cd9 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new 94b41893ff3 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new aefe76876a9 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 601ae8b8e68 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new a11e3fa465a 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 8925d35e7fb 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 36a18eabbbb 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 4710314b49a 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new 0f8177169ca 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new d5ee6079351 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...]

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 (5411faeab38) \ 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 1760 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32168 -> 31336 bytes 04-build_abe-stage1/console.log.xz | Bin 92852 -> 91304 bytes 06-build_abe-linux/console.log.xz | Bin 8672 -> 8660 bytes 07-build_abe-glibc/console.log.xz | Bin 238516 -> 235932 bytes 08-build_abe-stage2/console.log.xz | Bin 227576 -> 223788 bytes 09-build_abe-gdb/console.log.xz | Bin 39424 -> 38748 bytes 10-build_abe-qemu/console.log.xz | Bin 30972 -> 30368 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3020 -> 2436 bytes 13-check_regression/console.log.xz | Bin 5904 -> 5752 bytes 13-check_regression/mail-body.txt | 49 - 13-check_regression/results.compare | 22 +- 13-check_regression/results.compare2 | 51 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 51 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 2710896 -> 2714912 bytes sumfiles/g++.sum | 4 +- sumfiles/gcc.log.xz | Bin 2309872 -> 2305304 bytes sumfiles/gcc.sum | 2248 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 896484 -> 895992 bytes sumfiles/gfortran.sum | 64 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213124 -> 213028 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 430584 -> 425600 bytes sumfiles/libstdc++.sum | 2 +- 39 files changed, 1239 insertions(+), 1378 deletions(-)