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 a96bf5d3b0 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards 164155607e 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 39f05b2b97 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards c1725ec08a 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards 58c673840c 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards 0410f35879 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards 721bab0878 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards c6b1d6aea8 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards b9c40021b9 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards 064e1d5b96 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards adc07acf69 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards 4ffd50466e 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards 751d5874c9 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards 0b6fc66319 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards e526f74dde 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards 46e390853a 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards e1a3c80dc2 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards 0288441901 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards 0e92ed9a3a 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards be1e9cec6b 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 14d1f2b5dc 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards c1f26b07a0 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards 10538c8095 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards d1d194ea6d 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards e61707b430 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 4571bdfcba 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards 5244e99528 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 9e6af8831b 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards d3dca8e1ca 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 5975b740c9 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards a7b949e168 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 5b80f70c8a 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 622cb52999 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards e0b23c4a34 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards d879f0c554 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 969cbacd24 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 7b482acd80 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards b9a912ba28 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 7d1742b1e7 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards abfdf23126 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards bd245bb205 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 66cabc2bed 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 9fe7d9097d 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards eb407b58b9 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards d461541f92 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards bfdad10811 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 8c0c6312f4 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 9f6b1985eb 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards b3b29b7f3a 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 08edb8b223 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards d6fcfc6b91 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards ab277053a0 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards c7914ed7ec 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards db89e87c55 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 6c9b4a7d2b 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 34887e1cb1 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 925e31101f 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards bc3871451f 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 2b6612ad51 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards ff5f1ca3fd 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards a300bbe3a5 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 338394297d 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 113291a174 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards f2cc8a71fe 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards b542e878d0 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 2c18a7181a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 808d2d291b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards b521ea4122 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards d4bf1b4e5e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards c1b35adfa5 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 9658bbcbe8 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 850dd8e5f5 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards fc103c868b 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards d511aa0049 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 7f20bf1e06 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards be4a0f5c29 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards de1e18b741 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 73cd3bda9a 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 8ebe0e5772 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 17299f5eef 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 71cbdf37b4 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 0492cc507b 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 6af13186a6 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 3c5ee38e1b 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 03e070b33a 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards f66923fcdd 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards c123dd5e76 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 1d28463952 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 6ae32a9fe0 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 9665865991 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 2751df6290 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 16df8c4426 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 6104bc01f7 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards e9150c8219 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 3f362c8f94 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 3ff95a7c9d 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 39b7c87096 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards f093bc63e3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards c47da0be23 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards c74f76c8e9 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 1fcf56ae5c 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 4af066a766 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new fe1a75b0ee 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new a155a24870 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 636bb65fe6 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 4348b5da99 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new b874839314 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new fc1a56dbf6 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 0adfc5d46f 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 8d86c7acfb 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 4be93ca602 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 6254037997 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 4909c8cb2d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new b1b1363c50 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 9339f88882 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 7c05b0934a 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new f802b58fb1 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new cac2512e3e 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 66c51d02b6 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 3557348a9d 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 9705fbedb1 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new f8aef3600f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new ce7ef20de2 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 24702c0528 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 4e056c8424 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 1b82de7aa4 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new fa3ff10c94 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new c04851cc0f 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 9fb355060a 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new dbda9ac7a3 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 397eb9d276 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new ffc9388cef 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new cd3eee61cf 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 32a4fc914d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 38e7365e62 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new f84b8b3564 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 284b5f01e8 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 6931e590e9 128: onsuccess: #1723: 1: Success after linux: 12 commits new d928f81a43 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 9386355952 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new ba288063d0 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 827c622205 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 5c8022b71b 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new d76a487ab9 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 2baa2d7d19 135: onsuccess: #1733: 1: Success after binutils: 5 commits new d9fcd4ae76 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new ae600e2b67 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 3826b1e1dc 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 03988eaeb7 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 5d25d57ce0 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new b70a94e821 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 529d91a678 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 7bb436dd48 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new fdc92b7cb3 144: onsuccess: #1743: 1: Success after glibc: 2 commits new e14a15cb9f 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 3bcaa22014 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 2f1872aa9e 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new e926b292a1 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 705406c299 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new a7742f2cb3 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 9b995f7438 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new bbc4445662 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new e80adcbcf8 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 9b70e3caa2 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 815aedfbb6 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 81a794b40f 156: onsuccess: #1757: 1: Success after gcc: 4 commits new c9500be00c 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 586ac36e64 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 6bfef6a2dc 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 18adc32340 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new fca4846aca 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new c7372346f0 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 309833f0a3 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 5ac43c1af0 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new dc7d633b17 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new 8f4e0ef711 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new 1982af377d 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new 07bb7a128b 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new b036fa53e8 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 93bba83d69 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new f86bc94396 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new c0c0b4dafe 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new 41e67680e1 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new d1668e3f23 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new 49b4cd156b 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new 513fdaf733 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new 796258692b 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new 8dca16cf8f 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new d5180928c4 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new 1600bf4677 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new f0a20159b4 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new 888d122b4d 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new cdbee36d94 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new 203ffe4b8a 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new fb020efdab 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new 03e7601094 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 867a08dbdf 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new 4e1dc80deb 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new 8ac1a35fa4 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 3645552889 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new 03d7932552 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new 65abd90eba 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new fb8ee3cd6e 193: onsuccess: #1992: 1: Success after binutils: 151 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 (a96bf5d3b0) \ 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 1692 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 31600 -> 31096 bytes 04-build_abe-stage1/console.log.xz | Bin 91532 -> 91880 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8636 -> 8804 bytes 07-build_abe-glibc/console.log.xz | Bin 235300 -> 235780 bytes 08-build_abe-stage2/console.log.xz | Bin 224728 -> 225128 bytes 09-build_abe-gdb/console.log.xz | Bin 39040 -> 39216 bytes 10-build_abe-qemu/console.log.xz | Bin 31324 -> 30888 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3148 -> 3152 bytes 13-check_regression/console.log.xz | Bin 5848 -> 5328 bytes 13-check_regression/mail-body.txt | 53 - 13-check_regression/results.compare | 38 +- 13-check_regression/results.compare2 | 49 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 55 +- mail/mail-subject.txt | 2 +- manifest.sh | 33 +- sumfiles/g++.log.xz | Bin 2739956 -> 2705292 bytes sumfiles/g++.sum | 126 +- sumfiles/gcc.log.xz | Bin 2230452 -> 2238396 bytes sumfiles/gcc.sum | 2714 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 889972 -> 892756 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 212812 -> 212868 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 426608 -> 432932 bytes sumfiles/libstdc++.sum | 16 +- 37 files changed, 1548 insertions(+), 1676 deletions(-)