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 ebccba794d 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 9af2fa35c8 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 62d59b4e77 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 1cd151a29d 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards fabfa1ac5e 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 3a84a02c5b 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards dcfcbb4533 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards dd8390e727 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 6348b003eb 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards afaabcc932 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 2b2c3b52d1 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 9f57a6cd68 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards e337db5fce 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 1b777fe23b 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards e882f855b6 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 0c777cc9cb 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards fa09e80cb4 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 3beebe4241 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards a1088150c6 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 553467d5c5 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards e41b02d3ad 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards d06f5f0aba 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards a2f8477937 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 49652ca0f5 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards da93af8e04 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 65929ff61f 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 9cae6bef7d 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 7bcad40a59 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 2d9ff1f765 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 85f401c44a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards a6b05eee0b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 809b2f0401 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards ca36de303c 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 9b6387d3ca 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 3c0032822e 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards a3e97142c5 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 6de7ad4fc2 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 185600ea17 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 06c6b51e1c 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards ed681e6fbd 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards bc99b41690 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards a20147f819 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards a33ce18f1f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 26df55c527 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 5e440d9da4 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 7135137f33 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 3f30ad3e83 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 5301abe0b0 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards f1d8afdf6c 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 52af317d70 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 7cac034bd5 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 379d2fc911 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 4e323516b4 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards f136f97440 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards b20af5dd17 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards b28e5da168 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards aeb5bfb8f6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 079e9018b8 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards a65b879e18 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards e1579594d5 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards b79f965a52 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 7e7dfb3787 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards dc8197d646 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 78367c3d1d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 9b06b11a67 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 6e48fe47cc 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 6799706386 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2762a9c258 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3be5d40b63 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards eed676315e 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards c9c5729a86 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards f8c5b3f397 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards e1324f9c99 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 7008d1464e 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 96f0f69f72 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards baf77675ba 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 29de8d109c 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 4a97824bd5 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 54bbdd9ed9 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 12effb090d 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fafbe541dd 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards e4622fe5a2 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards da50b2ab01 74: onsuccess: 1: Successful build after linux: 44 commits discards ebfa0dd5df 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 9572351a85 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1ff93305a6 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 37947d456b 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards b1205e8f33 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards ee8eb078e6 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ca05f5fd8f 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f907217910 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0249e4d029 65: onsuccess: 1: Successful build after gcc: 4 commits discards baa3f1cf7e 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fa861a46ed 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 268335eaf3 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 874dfe7435 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 3b05677f0f 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b2e49a621c 59: onsuccess: 1: Successful build after glibc: 2 commits discards 08086c420d 58: onsuccess: 1: Successful build after binutils: 2 commits discards 56daf03552 57: onsuccess: 1: Successful build after gcc: 7 commits discards 84c6ccb287 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2d3b1a39a9 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5668360fe0 57: onsuccess: 1: Successful build after gcc: 7 commits new 45294a07b5 58: onsuccess: 1: Successful build after binutils: 2 commits new d5c654dd7d 59: onsuccess: 1: Successful build after glibc: 2 commits new f5e0f6d887 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 8766b9982d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 0bd234bbaf 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 1567f0b79f 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aea51986cf 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c93a6cebed 65: onsuccess: 1: Successful build after gcc: 4 commits new 886a88ec46 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ce8cb66de0 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9edd0d1d03 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e0afcd4e53 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 4c39bcd74b 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 8920c9dd7a 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 1a3f0baa64 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3544a24dd2 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new deb1ef4af0 74: onsuccess: 1: Successful build after linux: 44 commits new 1b179d1fdd 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5df569e563 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 8d63ce45f0 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5b3a19e5ff 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a895817304 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2f26b37c3b 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new bc64bff956 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 03029ca8aa 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new fe79e20ce7 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 3d16d80b30 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 40da81c920 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 56abce38e1 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 2adb753fe8 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 6ea96986da 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 4255c80f5d 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3afbfdaafc 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3f784b01a4 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new d632a4d99e 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new d46cc3da38 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 886129b699 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new c7c41a21ba 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 9c6742eab6 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new ce6fa07c3a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 357926a576 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 722e7ec551 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 44f24b26f6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 8f706581ba 101: onsuccess: #1693: 1: Success after glibc: 14 commits new c4bb99fdc6 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new b9dd739de6 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new b909bb8fea 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 13a14ffab5 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 6394d41002 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 90f5d4cbac 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 660168e940 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 8bc646729a 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new a5475a242b 110: onsuccess: #1703: 1: Success after gcc: 6 commits new b17fdd341a 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 2f491d33d0 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 68fe4b45b3 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 2404fb0813 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new e16ddc3a9c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 2217732be8 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 290a5e15f0 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 4b772ca222 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 6d68a4c99d 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 9086b73b7d 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 1abc3ef5bb 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new f4eb9e27e4 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 0abb50db5b 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 03b73a43a1 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 668872cbcc 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 80b117d534 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 9d7b9c42a0 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 7be11d9954 128: onsuccess: #1723: 1: Success after linux: 12 commits new 822cb98a20 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new a0e5265358 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new b5420abb87 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 9e6005598e 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 382579a31b 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 718719eace 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 6914395f41 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 86b7c1f7ef 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 0ba633710c 137: onsuccess: #1736: 1: Success after gcc: 5 commits new a88998f3b9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 01008fadd6 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 88b80a1030 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new b0f79df819 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new b7c59dcb72 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 001d9b0533 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new d19d6e37c1 144: onsuccess: #1743: 1: Success after glibc: 2 commits new f3a36367ad 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 875fe07cb0 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 928a584857 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 1b3c2b66df 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new ff770dc302 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 457b485c2d 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new af219a0ec7 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 858a6ee4c4 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new e5e8b84557 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 37970634b0 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new c51b96d517 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new d9b7b677f5 156: onsuccess: #1757: 1: Success after gcc: 4 commits new f740145c1e 157: onsuccess: #1758: 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 (ebccba794d) \ 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 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30076 -> 30184 bytes 04-build_abe-stage1/console.log.xz | Bin 90648 -> 90880 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8956 -> 8532 bytes 07-build_abe-glibc/console.log.xz | Bin 233936 -> 233852 bytes 08-build_abe-stage2/console.log.xz | Bin 223468 -> 222592 bytes 09-build_abe-gdb/console.log.xz | Bin 37192 -> 37328 bytes 10-build_abe-qemu/console.log.xz | Bin 32072 -> 31272 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2872 -> 2564 bytes 13-check_regression/console.log.xz | Bin 5688 -> 6160 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 44 +- 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 37 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 46 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 26 - sumfiles/g++.log.xz | Bin 2696696 -> 2655104 bytes sumfiles/g++.sum | 142 +- sumfiles/gcc.log.xz | Bin 2205840 -> 2234564 bytes sumfiles/gcc.sum | 2560 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 887700 -> 882444 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201532 -> 201476 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 432028 -> 428400 bytes sumfiles/libstdc++.sum | 16 +- 44 files changed, 1501 insertions(+), 1620 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions