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 003217aef8e 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards e7be90a2b32 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards ec9758bd248 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 0a5a52836ba 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards ccb29c5f571 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards adcd7d27113 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 8593e5b114e 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 3e50627e1eb 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards 95214c86b30 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards c7b07e3d8ef 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 4c37b4f0c64 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 1039b5968ee 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 9342251788d 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards ec1ee285035 194: onsuccess: #1995: 1: Success after linux: 517 commits discards efda9f16848 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards c64a55f024c 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards 7d3ef72fa39 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 9c3a36750e2 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards 02c3d74fc7f 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards d62771ca000 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 2b0526b2811 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards f0e679cf36c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards a59ead2494f 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards ddfb95f71e7 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards b68dc154fd8 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 5b305fb0345 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 55ae8aa91d8 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards c26197969da 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards 8f215142e8e 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards 1b6810620ab 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards 78aaf0dcce5 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards d6c54ba3ce9 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards c0278fdcd80 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 22b82369931 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards c3509cbb6c4 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards ff97dd5228c 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards d60e7cfadc8 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 218da5b8270 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards bff427ebd03 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards a232ec810d1 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards 7ca6e060c8a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards 7ea7d21734c 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 44f1975f011 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 96df0b6aeb4 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 5705fd5ba5d 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 57d57bba9df 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards a49d292a583 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards d5bd84185c8 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 22f73ce6108 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards 8b2c2592077 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 4335f67f002 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards b297b73da89 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 4f6004aeb0c 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards f0398411ab4 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 83f43769b7a 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 91a16c1a749 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards f9c9eb7ac49 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards 997dfcbd438 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards dbe665a0dea 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards 89e13b5ada7 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards a9dd265baf8 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards ba66bbbb7eb 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 4874fb46ba1 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 80c1fa09cf2 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 34026b0c753 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards e1c243999f2 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards 8329cb778f5 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 83d95237431 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards 02e44c9b4b6 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 5d48015ee3c 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards a49ad79b642 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards e7726d05191 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards a0d9b8f7b7a 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards f61cbf07519 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards a4a37b9d193 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards d101b2ec5f8 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards aa32ca2ceca 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards 47d950db33d 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards faa75e76ed2 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards b610404e806 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 627c81ad1e3 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards e77df884d42 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards b1995d632c6 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards 5bb4b4919aa 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 13b39a02351 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards 23a39f2e0d8 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards 97fe73335b4 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards b610ece685c 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards 2d4ffa77018 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards 2140975ce18 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards 847b15e6d11 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards ffd5093ab9c 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards 53e72ae965b 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards d0e85eaec8f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 8dc6e09e4da 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] discards a1a090b6f1d 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] discards f3f01792338 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] discards 3353ebc09fe 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 8f6fe9fdaff 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] discards 0af2aecfbad 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] discards 1899aadc51c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] new c89d1a66953 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] new d63511679a1 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] new 4ee4edfb0b7 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] new 7346ae05476 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 79ffbf6aacc 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] new c911b152b5b 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new 1f34efaf5ae 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new 967fd745074 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 3aa2c1d4580 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new 5b8ff6f3d89 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new 9da1b912c90 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new e46d97d8e70 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new 793383dd865 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new 5568ad39b4b 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new 77edebc9ad5 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 997f55732c9 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new 758841e7110 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new 84719070458 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 172f0d0d25d 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new 9d4e72eb955 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 534a624c486 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new 792409f7bc5 128: onsuccess: #1723: 1: Success after linux: 12 commits new 18b7ebb3f6f 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new b2325a332f1 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 0c1f2823e38 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new a98529a477d 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new 3c818605c18 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new e359282308f 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 1e601b18d15 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 120cb5f5fdd 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new 62ed542d74f 137: onsuccess: #1736: 1: Success after gcc: 5 commits new e9870940dc9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new 1abc8439a4c 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 02333b72450 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 7fcf0df7c45 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 955c3cfd3af 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new 0c81d58396c 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 503ab697f3e 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 5d11d1c703d 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new d4685c8b18f 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 59dbc9677e5 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new 25331ec27f2 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 4719e7499c3 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 21b140f1bc5 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 243ce48002b 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 375c9280e5a 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 7cecadb7534 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 177ccb406e2 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 6b3a5efee2a 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new b3666fbd991 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 8f41954a530 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 2c88b057067 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new a11cb153e07 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new 3011d72fb14 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 3466968ca67 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 3fb03deb914 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 93930f368d8 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 2dbb6b46e3b 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 52172b33258 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new 0ce77217be8 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new d6365693259 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 52247a0921d 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new a1b14730bcc 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new ec0f1c53274 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new f6c513f97be 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 820f927d452 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 1dc328f5cdb 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 5163150df12 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new f04221fba08 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new edd543c2bd7 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new 8bfd2627ecb 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 4813f22fac3 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new 24e9dedd209 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 3add6eda7ea 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new e2ff37a8e53 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 2dd55a07e80 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new 847a5f74fd3 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 7ce50ec13ce 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new 3f1041bac10 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new f4fe1b24efc 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new f384b004c4f 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 08b6f2ff951 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new da98baf9188 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new d0a0fdfccc2 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new a91125117ea 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new c39eacc9d7d 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new 985e8cd61d1 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 7c7ec89d611 194: onsuccess: #1995: 1: Success after linux: 517 commits new 545a534564d 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new a373bfa398c 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 2746ba299cb 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new cbc707fd53d 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new 0ff40ea2dda 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 639b5a7aca6 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new a11d6b0a997 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 0dfe5b44c54 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new ec7c611f16e 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new be235021a9a 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new 72b09cc6d6d 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 15a4c6a17dc 206: onsuccess: #2007: 1: Success after gcc: 2 commits new cb1f13b5da1 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 41a9b7bca14 208: onsuccess: #2012: 1: Success after linux: 12 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 (003217aef8e) \ 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 1800 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31808 -> 31436 bytes 04-build_abe-stage1/console.log.xz | Bin 91632 -> 91804 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8888 -> 8496 bytes 07-build_abe-glibc/console.log.xz | Bin 237640 -> 236756 bytes 08-build_abe-stage2/console.log.xz | Bin 225308 -> 225952 bytes 09-build_abe-gdb/console.log.xz | Bin 38868 -> 38728 bytes 10-build_abe-qemu/console.log.xz | Bin 31136 -> 30620 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2464 -> 2460 bytes 13-check_regression/console.log.xz | Bin 5140 -> 5368 bytes 13-check_regression/mail-body.txt | 42 - 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 44 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- sumfiles/g++.log.xz | Bin 2736252 -> 2711992 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 2276584 -> 2313940 bytes sumfiles/gcc.sum | 2712 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 894432 -> 892248 bytes sumfiles/gfortran.sum | 48 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213064 -> 213232 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 438576 -> 434364 bytes sumfiles/libstdc++.sum | 16 +- 37 files changed, 1549 insertions(+), 1631 deletions(-)