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 782c15e279 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards fc4734cff9 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 439bf6db34 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards b8e71afc96 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 835809e8e2 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards b25bc19c66 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards d9ce77a6e4 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards a83196d85b 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards a58df84cdb 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 5df45acfa4 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 0ab8704a96 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 277c2578d2 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 7b59f5e7a2 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 9b0c62a331 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 459268cc21 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 4145032150 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 1539a087b8 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 927ec93fa3 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 4034d8c2b8 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards e6c48e643c 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards cc52c1ea0a 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards d4fa75bfde 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 61d96312cc 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 788b158f1d 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards b37149d27c 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards a7fb194afd 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 7018865cf1 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 2678572c4e 128: onsuccess: #1723: 1: Success after linux: 12 commits discards b8633c3f9c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 4714590f5f 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 347215527d 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 6d5b202f22 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 02b0833778 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards d407d27e55 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 7fc8b849c7 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards ffe21f6a10 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 13c677f027 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards d16de88b59 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 87af198a63 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 7d86e378b8 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards f798298e80 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 6d3e12e92a 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 197421cef5 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards a01c16fa57 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards f65076c256 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards dfbc9deb0c 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 194297f8f1 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 7bafa89633 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 21451aa70a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 8c443b42c5 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 8179d129b5 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 8f83c67218 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 14eb40d58d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 0cd5cf68c6 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 81c8d77316 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 0eb707729d 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards a8b01858c0 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 95cb27af6f 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 71f73b2969 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 16cceaa7df 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards bb560e45ee 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 8345610ea1 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 21573f47ed 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards b92e83bec0 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 947a4bac27 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 8b88393473 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards ee46a68547 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards c3a3910b30 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards a38245a177 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 23eb873116 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 64a1de7507 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 3f47e8f14f 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 10e1a05c19 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards bb05826da9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards cbadbad84c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards e6eb2bad3f 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 7602705a5f 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 54a8a93d22 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 65103ae17b 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6cabba42c2 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards bb4fa8c424 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 28d897959c 74: onsuccess: 1: Successful build after linux: 44 commits discards 838f3dd98c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 6cd38c226a 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8b7ec4ded4 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 0ac8b36af8 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 4228b0f2ad 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 6c60ef15f4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 97ed350313 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8130da6213 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a6f24dc039 65: onsuccess: 1: Successful build after gcc: 4 commits discards 012eba71a6 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6831f0f2f5 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b1d8f12ace 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 74d589a6bd 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards dca794fe44 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b2df515570 59: onsuccess: 1: Successful build after glibc: 2 commits discards 1414b5a3c0 58: onsuccess: 1: Successful build after binutils: 2 commits discards bff3df3c20 57: onsuccess: 1: Successful build after gcc: 7 commits discards 0d704ec40b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9ad8167a90 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new be34df0668 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 84c6ccb287 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 56daf03552 57: onsuccess: 1: Successful build after gcc: 7 commits new 08086c420d 58: onsuccess: 1: Successful build after binutils: 2 commits new b2e49a621c 59: onsuccess: 1: Successful build after glibc: 2 commits new 3b05677f0f 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 874dfe7435 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 268335eaf3 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new fa861a46ed 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new baa3f1cf7e 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0249e4d029 65: onsuccess: 1: Successful build after gcc: 4 commits new f907217910 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ca05f5fd8f 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ee8eb078e6 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b1205e8f33 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 37947d456b 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 1ff93305a6 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 9572351a85 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ebfa0dd5df 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new da50b2ab01 74: onsuccess: 1: Successful build after linux: 44 commits new e4622fe5a2 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fafbe541dd 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 12effb090d 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 54bbdd9ed9 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4a97824bd5 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 29de8d109c 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new baf77675ba 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 96f0f69f72 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 7008d1464e 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new e1324f9c99 84: onsuccess: 1: Success after gcc/glibc: 9 commits new f8c5b3f397 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new c9c5729a86 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new eed676315e 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 3be5d40b63 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 2762a9c258 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 6799706386 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 6e48fe47cc 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 9b06b11a67 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 78367c3d1d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new dc8197d646 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 7e7dfb3787 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new b79f965a52 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new e1579594d5 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new a65b879e18 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 079e9018b8 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new aeb5bfb8f6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new b28e5da168 101: onsuccess: #1693: 1: Success after glibc: 14 commits new b20af5dd17 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new f136f97440 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 4e323516b4 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 379d2fc911 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 7cac034bd5 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 52af317d70 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new f1d8afdf6c 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 5301abe0b0 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 3f30ad3e83 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 7135137f33 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 5e440d9da4 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 26df55c527 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new a33ce18f1f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new a20147f819 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new bc99b41690 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new ed681e6fbd 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 06c6b51e1c 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 185600ea17 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 6de7ad4fc2 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new a3e97142c5 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 3c0032822e 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 9b6387d3ca 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new ca36de303c 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 809b2f0401 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new a6b05eee0b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 85f401c44a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 2d9ff1f765 128: onsuccess: #1723: 1: Success after linux: 12 commits new 7bcad40a59 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 9cae6bef7d 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 65929ff61f 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new da93af8e04 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 49652ca0f5 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new a2f8477937 134: onsuccess: #1730: 1: Success after binutils: 2 commits new d06f5f0aba 135: onsuccess: #1733: 1: Success after binutils: 5 commits new e41b02d3ad 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 553467d5c5 137: onsuccess: #1736: 1: Success after gcc: 5 commits new a1088150c6 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 3beebe4241 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new fa09e80cb4 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 0c777cc9cb 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new e882f855b6 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 1b777fe23b 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new e337db5fce 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 9f57a6cd68 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 2b2c3b52d1 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new afaabcc932 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 6348b003eb 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new dd8390e727 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new dcfcbb4533 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 3a84a02c5b 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new fabfa1ac5e 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 1cd151a29d 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 62d59b4e77 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 9af2fa35c8 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new ebccba794d 156: onsuccess: #1757: 1: Success after gcc: 4 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 (782c15e279) \ 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 1668 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30112 -> 30076 bytes 04-build_abe-stage1/console.log.xz | Bin 90876 -> 90648 bytes 06-build_abe-linux/console.log.xz | Bin 8928 -> 8956 bytes 07-build_abe-glibc/console.log.xz | Bin 234276 -> 233936 bytes 08-build_abe-stage2/console.log.xz | Bin 223936 -> 223468 bytes 09-build_abe-gdb/console.log.xz | Bin 37120 -> 37192 bytes 10-build_abe-qemu/console.log.xz | Bin 31540 -> 32072 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2432 -> 2872 bytes 13-check_regression/console.log.xz | Bin 5700 -> 5688 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 44 +- 13-check_regression/results.compare | 18 +- 13-check_regression/results.compare2 | 19 +- 13-check_regression/results.regressions | 18 +- 14-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 46 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 18 +- sumfiles/g++.log.xz | Bin 2664664 -> 2696696 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 2232560 -> 2205840 bytes sumfiles/gcc.sum | 2602 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 886828 -> 887700 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201752 -> 201532 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423444 -> 432028 bytes sumfiles/libstdc++.sum | 10 +- 39 files changed, 1476 insertions(+), 1423 deletions(-)