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 0076eddc0d3 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] discards ad9e2c84de9 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] discards 1a91ab9eac0 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] discards c1dd428bf54 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards b7b4b938be4 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 62ca7ce25ce 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 94470813473 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 82a3589dfc4 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards f31abee0365 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 617f77cd70b 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 87f7effb184 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 7758272107f 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards c2a82804469 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards 9119e57052e 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 9c6ae968570 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 4d45d83bdfd 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 90d803eac2c 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards d54e91f835b 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 06fa68f612a 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards ed90f1b46c4 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards a88165edd11 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 40d1f2d1ab9 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 1e30019be06 194: onsuccess: #1995: 1: Success after linux: 517 commits discards bf286f42948 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 40ece952e19 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards c0087ffe75a 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards c8abe2f788e 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards e3f55b7f9b7 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 244cbc7b9ce 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 558731f2baf 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards f839d07103b 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards 4689326d068 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 975dda2cdaf 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 889a3c62f41 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards a224475cc9b 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards bc36e09b9dd 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 16357469b88 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards 44048c2dc9c 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards 34bd3226f33 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards ec3eee9279c 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards a7aebc80735 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards e19930ca1d7 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards e4ee874f89f 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards 18dbf5aece3 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 9c032c4f919 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 98ac7a2779b 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 882f5bc655c 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards dd009b1654f 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards dbc71e2fb8c 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards 44daf297485 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards c26d35772ec 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards c563595f2bf 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 519bc8d7802 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 32808a6826f 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 59cf3497903 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards 17881245e66 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards bd45a725cb6 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards b4a3bdb3c55 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards adba9ec785a 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 758f112b033 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards 42d248d5052 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 35472a8d0f6 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 9ce1680fcfb 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 84b1efeabd1 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 35ac01634b2 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 8259a1b28a0 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards fd20899cfe2 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 3edb9f2c134 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards 7ad33f51996 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards e4b1195f465 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 23c46633d74 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards a582aa49a60 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 7ca8ff98f85 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 25a2fc56b10 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 9f45bbe9417 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards daab489286b 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 04ef23f6e26 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards 8df6765edf2 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 4e92d0d0721 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards c3d9a9e2038 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards b513c721b7d 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards b6b0a9ba8a1 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards b93c8f95511 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 6bdad9f8068 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards 5f184da7b92 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards 916f7613577 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards dfb9cd81128 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 5fdf36af31e 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards 40af554be38 128: onsuccess: #1723: 1: Success after linux: 12 commits discards a1e1f8f3053 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards 30835974d16 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards ded84429569 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards 0f209b26d1f 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 6997dcfb6fa 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards a2cc0fb6451 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards f7ff72cc853 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards 9df89605b83 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards c03fcbede83 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards d85ba7ab6f8 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards e58806dbc1e 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards c398adc38cd 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new a51ef4edde6 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new 8aed508daca 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new 395567487e0 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new 2715971ce8e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new 926188389aa 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new 57175d2753f 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new eb27257e2e7 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new 2639cdc8de6 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new 572fc9c2c2f 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new e11d552a8b1 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new d605e350847 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new b68980d5aeb 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new d9f2b618b35 128: onsuccess: #1723: 1: Success after linux: 12 commits new c03bcde1fbc 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new 8ada0509cac 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 1d23046651a 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new cb6b384810e 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new 33d9cf99807 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 584cdc98ac6 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 05f3c0b1ce3 135: onsuccess: #1733: 1: Success after binutils: 5 commits new cdf7f06c354 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new 266d9aca34c 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 562be0b3f86 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new 723adea606d 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 1aac635e345 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 7bd4557f071 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 311df1bb346 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new 3129fa10999 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new c57ef7b9089 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 1c71a471cfb 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new 97b19f9cbf0 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 1468f45c421 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new f5d8f3058c3 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 2b782205db4 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new d5468aa52a7 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 143e931cf91 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 9f4b1aedfb6 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 2b1b09cb38d 153: onsuccess: #1754: 1: Success after gcc: 2 commits new e1d65ba343d 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 509966d9594 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new b590537b7d5 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 68b42ea9a01 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new ad75f0a2765 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new c6a0350f375 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new d3b92cf5128 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 98acc730663 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 164eeefc8b4 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 31d9feda0fc 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new f30848eeac9 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new a261bfc5882 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new 22a385c4874 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 8b0c8c72dca 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 50e033fb829 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 039733b09c2 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 359dd68af56 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new aa57bae00d0 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 023afc6072d 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 4b2acfa44a4 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 8bad04b647a 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new 5bf8d1f1c9d 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new bdbbb5c7fdb 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new 112a520ee64 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new b8465cc23a3 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new ddf80304754 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 5b31d94c71c 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 41a360c3109 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new e5ae4792ded 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new 6277122bf59 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 187a4bde494 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new 88c05d400c7 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new 38187e948fb 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 0d119039394 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new d8dadd1374d 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new d94a94cac74 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 6c9eab2bf85 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new 8a94e83ea0d 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new b755bc57354 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new d883bfc7141 193: onsuccess: #1992: 1: Success after binutils: 151 commits new d6e909daa7a 194: onsuccess: #1995: 1: Success after linux: 517 commits new 4a2c9343e3b 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new 1edb02c3722 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 92f861e1366 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 01c713311dc 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new 5afa2b7f693 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 2931c40f2eb 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 0b96ee106b6 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new bf455963f19 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new 6019f8f209f 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new def30406e73 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new fea67b86980 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 3ac67aff41e 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 354a48bd047 207: onsuccess: #2010: 1: Success after gcc: 4 commits new ec8a9ae2b1c 208: onsuccess: #2012: 1: Success after linux: 12 commits new cf0dfc7cd26 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 20258edb388 210: onsuccess: #2017: 1: Success after binutils: 6 commits new d5c5ff1925c 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 9dda4cbc317 212: onsuccess: #2022: 1: Success after linux: 3 commits new 71268117ba5 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 4c25a13816f 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] new 5d306c4979a 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] new 8dd8b34a166 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] new 09702dbd1fd 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...]
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 (0076eddc0d3) \ 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 1796 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31664 -> 31676 bytes 04-build_abe-stage1/console.log.xz | Bin 92172 -> 92008 bytes 06-build_abe-linux/console.log.xz | Bin 8628 -> 8620 bytes 07-build_abe-glibc/console.log.xz | Bin 236128 -> 235608 bytes 08-build_abe-stage2/console.log.xz | Bin 225488 -> 225980 bytes 09-build_abe-gdb/console.log.xz | Bin 38816 -> 38944 bytes 10-build_abe-qemu/console.log.xz | Bin 30616 -> 30728 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2772 -> 2764 bytes 13-check_regression/console.log.xz | Bin 6864 -> 5668 bytes 13-check_regression/results.compare | 12 +- 13-check_regression/results.compare2 | 59 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_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 2724168 -> 2739692 bytes sumfiles/g++.sum | 32 +- sumfiles/gcc.log.xz | Bin 2315344 -> 2286892 bytes sumfiles/gcc.sum | 2208 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 892244 -> 889124 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213212 -> 213280 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435720 -> 429840 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 1199 insertions(+), 1248 deletions(-)