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 09702dbd1fd 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] discards 8dd8b34a166 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] discards 5d306c4979a 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] discards 4c25a13816f 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] discards 71268117ba5 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 9dda4cbc317 212: onsuccess: #2022: 1: Success after linux: 3 commits discards d5c5ff1925c 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 20258edb388 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards cf0dfc7cd26 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards ec8a9ae2b1c 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 354a48bd047 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 3ac67aff41e 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards fea67b86980 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards def30406e73 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards 6019f8f209f 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards bf455963f19 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 0b96ee106b6 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 2931c40f2eb 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards 5afa2b7f693 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 01c713311dc 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 92f861e1366 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 1edb02c3722 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 4a2c9343e3b 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards d6e909daa7a 194: onsuccess: #1995: 1: Success after linux: 517 commits discards d883bfc7141 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards b755bc57354 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards 8a94e83ea0d 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 6c9eab2bf85 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards d94a94cac74 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards d8dadd1374d 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 0d119039394 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards 38187e948fb 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards 88c05d400c7 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 187a4bde494 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 6277122bf59 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards e5ae4792ded 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 41a360c3109 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 5b31d94c71c 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards ddf80304754 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards b8465cc23a3 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards 112a520ee64 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards bdbbb5c7fdb 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 5bf8d1f1c9d 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 8bad04b647a 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards 4b2acfa44a4 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 023afc6072d 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards aa57bae00d0 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 359dd68af56 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards 039733b09c2 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 50e033fb829 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards 8b0c8c72dca 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards 22a385c4874 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards a261bfc5882 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards f30848eeac9 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 31d9feda0fc 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 164eeefc8b4 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards 98acc730663 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards d3b92cf5128 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards c6a0350f375 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards ad75f0a2765 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 68b42ea9a01 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards b590537b7d5 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 509966d9594 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards e1d65ba343d 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 2b1b09cb38d 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 9f4b1aedfb6 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 143e931cf91 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards d5468aa52a7 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 2b782205db4 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards f5d8f3058c3 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 1468f45c421 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 97b19f9cbf0 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 1c71a471cfb 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards c57ef7b9089 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 3129fa10999 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 311df1bb346 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards 7bd4557f071 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 1aac635e345 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards 723adea606d 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 562be0b3f86 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards 266d9aca34c 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards cdf7f06c354 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards 05f3c0b1ce3 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 584cdc98ac6 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 33d9cf99807 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards cb6b384810e 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards 1d23046651a 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards 8ada0509cac 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards c03bcde1fbc 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards d9f2b618b35 128: onsuccess: #1723: 1: Success after linux: 12 commits discards b68980d5aeb 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards d605e350847 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards e11d552a8b1 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards 572fc9c2c2f 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 2639cdc8de6 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards eb27257e2e7 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards 57175d2753f 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards 926188389aa 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards 2715971ce8e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards 395567487e0 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards 8aed508daca 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new 2e55412f163 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new 0b422785476 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new 58e6bc454c5 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new d33da0f5c4c 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new f2f29614319 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 7a3672860a6 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new 9425d1a8961 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new bc6836fa94f 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new a4894f889f6 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new 2f4c3d73c38 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new d5fffcdb563 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new 9af278ddcff 128: onsuccess: #1723: 1: Success after linux: 12 commits new d5be6cf8398 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new 631df490410 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 71711d3ac3c 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new d424c1afe7b 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new 3723f2544e2 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new f84ee677b40 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 4e1f4776649 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 268be33cbe1 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new c40afebf330 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 4ece171c8cd 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new 4f66220c400 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 65929e3d481 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 87545d04039 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new f600a5655c7 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new bccfe98a499 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 9a9e8bea153 144: onsuccess: #1743: 1: Success after glibc: 2 commits new abe45e9a9de 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new 87cf4242a87 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 5abad60bb5a 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new db7eab694d5 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new aabc92f2304 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new ccc551a1472 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new af547a05e7d 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new dd2f3ddc29b 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new de0c3bf52bd 153: onsuccess: #1754: 1: Success after gcc: 2 commits new f96f663d1fe 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 77477e5fba3 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new f01b779349c 156: onsuccess: #1757: 1: Success after gcc: 4 commits new f3f22c161f3 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new d82d98ec458 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new a2f203c6b6d 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new 440064e6004 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 12f0eee7752 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 4736c352a91 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 71e1ea66e63 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 39d87a96c23 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new ea2b156dce2 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new 1c859a4db6c 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new f0385e2a975 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 73084f1ae21 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 071d041f6ef 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 6cf9c3b65b8 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new b39ca2115cf 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new a70a2a24087 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new f3511c24ac0 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 7ce2a4f5312 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new cc07cf4cc5f 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new f5181395a6d 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new d3e7daa1b3e 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 5bee1dba30f 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new e49423d249b 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 46f27dc1a69 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 16cfd2474b3 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 2708104cf3b 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new f697198f204 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 66682027cc1 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new 532c67e099d 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new 5c1e8fd1fb1 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new f7962ab28e4 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new fe61d3d6fb9 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 52b441c77c8 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 953c6abc9d1 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new 2643ba150b8 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new 311156f7af7 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new 8932eb288ab 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 959a426fe92 194: onsuccess: #1995: 1: Success after linux: 517 commits new 9e613f9a9b4 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new 65b1cc3bdd7 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new f8a6abaad3c 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 4d9ad4206fd 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new a7575c95ab7 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 37bc452185b 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 70918233631 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 9f1947540f4 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new 7c9b4168621 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new e6b1b7dd982 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new 9507d137d6e 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 39fcfe04cdd 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 29fe6df74e6 207: onsuccess: #2010: 1: Success after gcc: 4 commits new f2e3876bc46 208: onsuccess: #2012: 1: Success after linux: 12 commits new 35de6cf9cfe 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 94017c8faaa 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 4794455f97f 211: onsuccess: #2020: 1: Success after binutils: 10 commits new c43cd854a8b 212: onsuccess: #2022: 1: Success after linux: 3 commits new 167e739b831 213: onsuccess: #2024: 1: Success after binutils: 3 commits new bf74e819d65 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] new 60628b2b943 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] new 184593d6080 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] new 71ea808608f 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] new 64364846f9c 218: onsuccess: #2030: 1: Success after gcc: 5 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 (09702dbd1fd) \ 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 1768 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31676 -> 32052 bytes 04-build_abe-stage1/console.log.xz | Bin 92008 -> 91512 bytes 06-build_abe-linux/console.log.xz | Bin 8620 -> 8592 bytes 07-build_abe-glibc/console.log.xz | Bin 235608 -> 236444 bytes 08-build_abe-stage2/console.log.xz | Bin 225980 -> 225404 bytes 09-build_abe-gdb/console.log.xz | Bin 38944 -> 38940 bytes 10-build_abe-qemu/console.log.xz | Bin 30728 -> 30588 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2764 -> 2488 bytes 13-check_regression/console.log.xz | Bin 5668 -> 5484 bytes 13-check_regression/results.compare | 20 +- 13-check_regression/results.compare2 | 17 +- 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- sumfiles/g++.log.xz | Bin 2739692 -> 2743112 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2286892 -> 2280792 bytes sumfiles/gcc.sum | 2296 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 889124 -> 889184 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213280 -> 213260 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429840 -> 429972 bytes sumfiles/libstdc++.sum | 2 +- 35 files changed, 1228 insertions(+), 1217 deletions(-)