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 2d0cbe26ad5 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/ [...] discards f51a75e409b 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 2 [...] discards 6916474d902 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/ [...] discards 0de3cbb6993 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/ [...] discards 6a32b1a3b8e 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/ [...] discards 3385c0fb44b 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 1 [...] discards db3673c04f2 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 3db696ddeb1 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/ [...] discards 5fc8ff7e700 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/ [...] discards aa8db7d0bcb 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards efb348cc20c 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards b846fa96a63 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/ [...] discards fbcb5828127 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/ [...] discards 2ec062dff88 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-4 [...] discards 560391bb534 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/ [...] discards b83cd90eb43 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 1 [...] discards a4b5b97da39 225: onsuccess: #2039: 1: Success after binutils/linux/glib [...] discards 5869c292759 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/ [...] discards 372738c06eb 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/ [...] discards dc3e12d0f1a 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/ [...] discards 943d96b8411 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards aebde8cad30 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...] discards 31fbcc9ad36 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] discards 49807390316 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 32371ac8904 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] discards 181601d8986 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] discards 9d3566530dd 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] discards 93839e36f9e 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] discards b401f5f7193 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards f81229b7def 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 230609dda5e 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 2edde529569 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 0cfe787bca4 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 6d9c452bd6a 208: onsuccess: #2012: 1: Success after linux: 12 commits discards ddc8a50393b 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 98f646b282c 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 415892fa3c4 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards da2eda682de 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards 7ac1f68f620 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 904526e8cfe 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 36d0c8335f9 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 0954ffb0292 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards 35e42267f63 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards b56ffc399a1 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 589aa4ea3c8 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 6d8886c1c47 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards ce4683996d8 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 3bc88b896bb 194: onsuccess: #1995: 1: Success after linux: 517 commits discards e610d618e6a 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 21bbfc6da74 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards c5b99a676a8 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards c6f058dcc2d 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards 5f6e01680d1 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards eebaf3dcd34 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards d77331b7768 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards a07b527f662 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards c5747964f18 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards aebdd69a861 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 21c0c01b526 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 3965a156cd4 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 24cf2ec052d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 2c242ae543b 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards 75f54dbbe4f 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards d998a87a9c1 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards 0e7395b6558 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards 52ec4c006c5 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 820d2b994dc 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 8cc2d65af06 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards 3a80ea5c3a3 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards ba1751713a4 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 51ea246f889 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards f9c16bf51bc 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards 9f7c64640ac 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards f29c400d943 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards 75657260343 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards 5f000fa3870 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards dc164a6fb26 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 79e992b3bcb 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 94263591507 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 5ee502882e4 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards cd51c51eebb 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards 64ad024c3d4 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards a72b99001e6 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards 865571ce360 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards fa09adfabb3 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards 07ef7bf9cb5 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 91486c1e6d4 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 63b8180ee7d 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards a156699c5a7 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 309d86709f9 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 9f2581c6fde 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards d1314a68e6b 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 8509cc24e5d 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards 56b44bc3859 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards da9ea6c76c3 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 16ce7ab9777 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 72d85e8c543 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 3cb3c90681b 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 97488c10003 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 92ccee5bb52 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards 3303dfe852e 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 3e772600d9d 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 6ae3ae6afec 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new 31914255aeb 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new ae307b8077b 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 0ac7c3497da 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new 3b7644dba1e 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 92d7187698c 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new a41eb0b08dc 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 60110ee8668 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new f31c61832dd 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new e711524edf5 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 39dabf5a573 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 971dcfb7738 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 92252df3fd8 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 856eb34c42d 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new ed715682e9d 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 3590df10e59 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 1b51d5c048d 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new ba32095c8a0 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new e60ee79a8c6 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 28f6cee1f52 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new c9349002d84 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 5414b6bca4c 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 8469f706a49 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 7fd3ae555b3 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new 92a62f5811e 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 26d4f15ed52 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 5825205f132 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 8b9c5721d2d 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 7a09400eb90 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new b0a2806020b 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 921cc1dbd0c 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 85b3e5b9f56 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 5523ecc9495 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new 1aa0244cf92 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new f2e8cf795b0 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new 11865c4d438 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 5a4903d0949 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new e3ee5b7385c 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new b95d9e91b58 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new b36ea706b55 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 29fde4f8b3f 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new ae9362928a5 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new a4011490303 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new 0494cd2b249 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new eb0b895bb61 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 109ec3f5718 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new e006a41624e 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 5aac00b5751 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 001f408607a 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new 3b8e22a9f35 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new d72a22bf77a 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new f6e8f058bab 193: onsuccess: #1992: 1: Success after binutils: 151 commits new e870cfaf981 194: onsuccess: #1995: 1: Success after linux: 517 commits new fcfbdc8c197 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new e32cc450063 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new b47199f4ef8 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 14059ab7ee9 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new 54319ba76f5 199: onsuccess: #2000: 1: Success after gcc: 5 commits new fff16c28f79 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new eb67d4f9349 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new ce78ef86625 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new 6795e737ffe 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 9846a450149 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new 1d90918a802 205: onsuccess: #2006: 1: Success after gcc: 3 commits new f0e316b5473 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 4994f610e78 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 561d6a52cd9 208: onsuccess: #2012: 1: Success after linux: 12 commits new 1f5021bd9b4 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 5c774b35a02 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 25c387e219a 211: onsuccess: #2020: 1: Success after binutils: 10 commits new eb0dcbd032a 212: onsuccess: #2022: 1: Success after linux: 3 commits new 38d5df36e13 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 61fd0e07ad4 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] new b57da44f4e6 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] new 73dbae1ab77 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] new be60202de3f 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] new 18a3d3a0bde 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 7ba8e431a8d 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] new 50bd240d345 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...] new 68e9927b877 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 9ea4d02faa0 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/ [...] new 2e69b4625b9 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/ [...] new 2c8c8302c98 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/ [...] new f55f2f3aeba 225: onsuccess: #2039: 1: Success after binutils/linux/glib [...] new eb5fb968ef5 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 1 [...] new 57ee20f5161 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/ [...] new 340c4c295e4 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-4 [...] new c934cb9e58d 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/ [...] new ce6a52f8424 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/ [...] new a2194a6d43b 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 864a99f5864 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 5be19cc3ce1 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/ [...] new 03c5316a523 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/ [...] new 185c87decbf 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new c89de4d6a43 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 1 [...] new ea6a2077d47 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/ [...] new 61af069099a 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/ [...] new 8c4a34c1612 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/ [...] new f76b377acbd 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 2 [...] new 5221a2180b6 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/ [...] new 17122ff810e 242: onsuccess: #2058: 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 (2d0cbe26ad5) \ 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 1756 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2808 bytes 03-build_abe-binutils/console.log.xz | Bin 31508 -> 31532 bytes 04-build_abe-stage1/console.log.xz | Bin 91588 -> 92956 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 10616 -> 9628 bytes 07-build_abe-glibc/console.log.xz | Bin 234696 -> 235932 bytes 08-build_abe-stage2/console.log.xz | Bin 224520 -> 225028 bytes 09-build_abe-gdb/console.log.xz | Bin 38804 -> 38972 bytes 10-build_abe-qemu/console.log.xz | Bin 30504 -> 30784 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3924 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2964 -> 2504 bytes 13-check_regression/console.log.xz | Bin 7124 -> 6084 bytes 13-check_regression/results.compare | 22 +- 13-check_regression/results.compare2 | 108 +- 14-update_baseline/console.log | 66 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 2681956 -> 2686268 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 2237388 -> 2243280 bytes sumfiles/gcc.sum | 2370 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 890912 -> 900656 bytes sumfiles/gfortran.sum | 43 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213892 -> 214112 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 426724 -> 441452 bytes sumfiles/libstdc++.sum | 16 +- 39 files changed, 1390 insertions(+), 1455 deletions(-)