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 f2c848fffb 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 98c83c1291 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards bd63c3f3ac 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 7935331b89 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 4dfdfd64de 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 739f5ebf25 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 738db955d9 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards f6d252c968 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 96a52fb236 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 3cbe051dc8 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards d28e17d771 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 87ebda3d91 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 1d6fc392b2 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 6e7a3ee799 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards afde9137b3 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 122e109062 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 8b824eb4f9 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards c675cbc154 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards fb9b70e9de 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 1db93cf34c 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 536336db4b 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 4eaa9c5730 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 840a813c92 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 88e1401e84 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 6deb68fd54 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 9401618ec8 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards e2e1a3c2a9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 421f788183 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards c9fe0195c6 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 1bdf408fb5 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards ed68f415b2 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards b9e1076c77 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 03175318a1 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 2bacb8e1c5 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards ba429452c8 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 39a3371ad9 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards e099c2408b 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 45f8d4f44e 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 4dd7a206bb 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 70caa0ecfe 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 426b74dc4e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 52d98df9fa 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 39121bb457 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards cc8f029cb7 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 4afd045c83 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 97531635db 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards e2fa023722 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards ff312dbbe8 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards bbb7a76b48 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 9e8b3c2a66 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards d8e8787f17 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards de71a8f997 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 5b89b729eb 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 9e1138302c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards ae0ec6d099 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 1177425c3c 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 6425a8391e 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 0cfb705a19 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards f695dcf072 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 586ab21c66 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 4489b554a8 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 57208266ab 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards d2b4976c05 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 38dbb2acd1 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 0a1fe02b36 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 9f00223304 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 9784a18677 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 163ce16f60 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards b470bfbc3a 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 7038229704 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards bf26233056 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 0f99751928 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 44638ad445 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards aeb383503a 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 32869c1956 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e4cc7e43f1 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 43c29eb70a 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 968326432c 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards ad3242200c 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards ae68286378 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards aafa20102a 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 253d959aa0 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 2d3b2cb469 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 1689c3d468 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 4dcffd2c2e 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards fcec1814c2 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 0627b90040 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5d35a015f6 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5b2c699948 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 78444ae301 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9bf1417551 74: onsuccess: 1: Successful build after linux: 44 commits discards f33dbd38fa 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards d9dffeba62 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eac7b2b8f0 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards c3501b72dd 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 8d81ed5110 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 478af8add7 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d74a3d2fee 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9941270645 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3d476c5362 65: onsuccess: 1: Successful build after gcc: 4 commits discards 444ceba509 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 10a3bd36df 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bbbcd697e1 65: onsuccess: 1: Successful build after gcc: 4 commits new 8788292721 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new cfcf3b36fa 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5ba7d61d48 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 00c4fe41db 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 31fe049bcd 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 4ed787c3d4 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 3f8305d43d 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 09e65853c9 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 2b4894484d 74: onsuccess: 1: Successful build after linux: 44 commits new 00c89a963d 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 59ec10231c 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 83400720ed 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 88fcc66b3a 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 88ad7b89c4 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 145a42c9ac 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new f55269aff1 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new ef02335826 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new ee62204c31 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 83b26c7940 84: onsuccess: 1: Success after gcc/glibc: 9 commits new a190e8a0bd 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new b671f02d33 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new e9237c8182 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new e8466b10f7 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 43c078976d 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 709cea2b94 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3168a256eb 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new d062271954 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 3e8af37cb3 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new e028cbfbb7 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new b9b5b1e83f 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 682cadfd75 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 9e263e7891 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new e83833ab14 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 6dc605bce0 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 42f7d70b5b 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 412ecdd15c 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 49ed296544 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 7ac523ab45 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 51c5243516 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 858d0417e5 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 29b5e30497 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 4eabc0d07c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new d543e5f93a 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 0c0486e13f 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 82c95b5b07 110: onsuccess: #1703: 1: Success after gcc: 6 commits new f22b86bf04 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 89a5ee5945 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 9589e26ea1 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new f3ac79a304 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new f168ea5bbe 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 4aabf6a5f1 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 4735780cee 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 7a35833dd9 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 31fc15ff04 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 72d7450930 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new e5c432383b 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new ceae208f02 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new ad6c604268 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 93d648441b 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 3cfc77c290 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 38da561415 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 9e0841a9f1 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 3d9cde6214 128: onsuccess: #1723: 1: Success after linux: 12 commits new 9ff876506a 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 03f37de322 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 636d94e0bb 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 00d4a57690 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new b92273fbed 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new c74a6ee741 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 9632f23ffe 135: onsuccess: #1733: 1: Success after binutils: 5 commits new bd682250ac 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 37661e68e8 137: onsuccess: #1736: 1: Success after gcc: 5 commits new f50f67269f 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 94bb29cfda 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 6f64060a08 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new fe7b50c7ad 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 38a453ad3c 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new c181afc983 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new f51f99cd8e 144: onsuccess: #1743: 1: Success after glibc: 2 commits new f38b35e470 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 74d7bed634 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new d0d8238e60 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new d9fa3077ea 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 0e418815a5 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new fc6dda2b5a 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 343ec42f94 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 95a7ce1673 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new b28c2de0f8 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 7eeac5432c 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 1bcce449de 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new e077f9405c 156: onsuccess: #1757: 1: Success after gcc: 4 commits new a252262c83 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 84d336be4b 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 560a94d92f 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 90e54ce055 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 339dbad657 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new a41687fddd 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 61811b3db9 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new e578650742 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 689c09a1e6 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...]

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 (f2c848fffb) \ 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 1700 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30024 -> 30436 bytes 04-build_abe-stage1/console.log.xz | Bin 90620 -> 90960 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9152 -> 8496 bytes 07-build_abe-glibc/console.log.xz | Bin 233800 -> 233264 bytes 08-build_abe-stage2/console.log.xz | Bin 224084 -> 224672 bytes 09-build_abe-gdb/console.log.xz | Bin 37640 -> 37660 bytes 10-build_abe-qemu/console.log.xz | Bin 31844 -> 31628 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2608 -> 2752 bytes 13-check_regression/console.log.xz | Bin 6412 -> 6840 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 40 +- 13-check_regression/results.compare2 | 202 +-- 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 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- sumfiles/g++.log.xz | Bin 2690272 -> 2661780 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2212152 -> 2199188 bytes sumfiles/gcc.sum | 2498 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 884764 -> 886428 bytes sumfiles/gfortran.sum | 56 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201500 -> 201408 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 432940 -> 429724 bytes sumfiles/libstdc++.sum | 18 +- 41 files changed, 1491 insertions(+), 1649 deletions(-)