Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/interesting-commits] branch master updated (212fdf3 -> 7f026e7)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 212fdf3 Add entry a3a956c78efaa202b1d75190136671cf6e87bfbe from https [...] new 7f026e7 Add entry f30e9fd33e56a5a721346ea6140722e1b193db42 from https [...] The 1 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: gcc/basepoints/gcc-13-3172-gf30e9fd33e5 | 1 + .../master-aarch64-bootstrap_lto}/build_url | 2 +- .../master-aarch64-bootstrap_lto/last_good | 1 + .../master-aarch64-bootstrap_lto/summary.txt | 1 + .../tcwg_gcc_bootstrap/status.txt | 24 ++++++++++++++++++++++ 5 files changed, 28 insertions(+), 1 deletion(-) create mode 120000 gcc/basepoints/gcc-13-3172-gf30e9fd33e5 copy gcc/sha1/{953e08fde44a596e4ec2491efd15cd645e1ddc48/tcwg_gcc_bootstrap/master- [...] create mode 100644 gcc/sha1/f30e9fd33e56a5a721346ea6140722e1b193db42/tcwg_gcc_boot [...] create mode 100644 gcc/sha1/f30e9fd33e56a5a721346ea6140722e1b193db42/tcwg_gcc_boot [...] create mode 100644 gcc/sha1/f30e9fd33e56a5a721346ea6140722e1b193db42/tcwg_gcc_boot [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (4a333928cb -> 8d668f8821)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from 4a333928cb 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 8d668f8821 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] The 1 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 1692 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 39540 -> 37880 bytes 04-build_abe-gcc/console.log.xz | Bin 214712 -> 215796 bytes 06-build_abe-linux/console.log.xz | Bin 8480 -> 9156 bytes 07-build_abe-glibc/console.log.xz | Bin 239492 -> 241228 bytes 08-build_abe-gdb/console.log.xz | Bin 38020 -> 37384 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3824 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2568 -> 2108 bytes 11-check_regression/console.log.xz | Bin 10936 -> 16532 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 53 +- 11-check_regression/mail-body.txt | 158 +- 11-check_regression/results.compare | 89 +- 11-check_regression/results.compare2 | 2816 +++++++++++++++++++- 11-check_regression/results.regressions | 89 +- 12-update_baseline/console.log | 9 + 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 | 160 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 89 +- sumfiles/gdb.log.xz | Bin 1872964 -> 1846500 bytes sumfiles/gdb.sum | 4255 +++++++++++++++++++++++++++++-- 30 files changed, 7153 insertions(+), 619 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (5d8febf5f6 -> d90b3e00c2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-arm in repository toolchain/ci/base-artifacts. discards 5d8febf5f6 175: onsuccess: #1795: 1: Success after binutils/gcc: 7 commits discards f3ba30bdbb 174: onsuccess: #1794: 1: Success after binutils/gcc: 17 commits discards f3296746e1 173: onsuccess: #1793: 1: Success after gcc: 12 commits discards 3201931564 172: onsuccess: #1792: 1: Success after binutils/gcc: 4 commits discards 9f114d1a10 171: onsuccess: #1791: 1: Success after binutils/gcc: 7 commits discards b543cb9d2a 170: onsuccess: #1790: 1: Success after binutils/gcc: 9 commits discards 3fb1b35b2f 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 commits discards 86f8f6ccc4 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits discards 2972679b75 167: onsuccess: #1787: 1: Success after gcc: 8 commits discards ec0030d9e9 166: onsuccess: #1786: 1: Success after gcc: 10 commits discards 7683a88cfe 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits discards 631b7473c0 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits discards 26e6a4c287 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits discards 4b99b7910d 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits discards 2d7f3afba6 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits discards a892f0873f 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits discards 64c35e2348 159: onsuccess: #1779: 1: Success after gcc: 2 commits discards a2fac4ac41 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits discards bbb6ac903d 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits discards 14ad6f383d 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits discards eafd44cebe 155: onsuccess: #1775: 1: Success after binutils: 2 commits discards b0a78223fd 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits discards 4ec5c64261 153: onsuccess: #1773: 1: Success after gcc: 4 commits discards d16effa37f 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits discards 6d7243ffaa 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] discards 01b99b9475 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] discards 50687a5d5b 149: onsuccess: #1769: 1: Success after gcc: 3 commits discards e05808cfa8 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits discards 8e3405aaf8 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits discards 8c763638c0 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards 10798c51ce 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards 77ba9e11a8 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards 2341fe61a0 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards bb724147d8 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards d2c9aa2f10 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards 611ab58832 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards 990a33d6cb 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards 5f54fc41c0 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards e56b4a9717 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards b3fc937928 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards 52bef6d0f6 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards 2810c26bfc 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards 87bec4d582 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 9d9c0d3836 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards bca69ab888 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards b645df88b3 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards 92be5fa00f 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards dd7c3e140c 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards 2313a5cb4a 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards 5a75e21399 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards c4aee5e29d 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards c84065820d 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards 675bf9b490 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards 0d7d3d7243 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards e4fee88e23 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards 45bb2e01ee 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards 57f824f100 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards 795827e151 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards 1c1fc0d139 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 1de6f42b20 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards b3f57d435b 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards 3b95e204ee 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards 9b7f42f1a1 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards fdbb1cd45e 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards 723b16237a 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards 674aacf811 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 622d25bf70 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards cecc83d744 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards 64793978ab 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards 6768041a2b 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards 8ac0a32d8d 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards bb83b882d6 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards ddfbe3a027 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards a7223a843a 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards 1d1d66e1d3 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards 6192b9f404 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards b98f0d0880 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards 3fbd4b6565 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards acf61f075a 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards 6f78918251 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards e18b196329 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards 632cd94f22 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards c3b0e96382 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards c72cb5b49b 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards 50c66cda52 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards 4deab014d0 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards fbe1e1e474 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards 11821325c5 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards 7d7f74470f 87: onsuccess: 1: Success after gcc: 6 commits discards 2feb0ecc13 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards c3cf826eec 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards fb711d1380 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards 5a0ab64fa5 83: onsuccess: 1: Success after gcc: 14 commits discards 7385aa4d3c 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 182b66a064 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards 2aa84db0b7 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards 0ae7c2ee0e 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards f269a50656 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards f6ae07cf6a 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 3c4d0ceef5 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 9cc1144aa9 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 43aee9cb94 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 5d272699df 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 8a4b91acd0 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 85b2831756 78: onsuccess: 1: Success after binutils/gcc: 17 commits new 82e70f8633 79: onsuccess: 1: Success after binutils/gcc: 23 commits new 4041e54398 80: onsuccess: 1: Success after binutils/gcc: 8 commits new efa9f464de 81: onsuccess: 1: Success after binutils/gcc: 8 commits new 188b64488a 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 9e5bd6da1f 83: onsuccess: 1: Success after gcc: 14 commits new f7a99345f9 84: onsuccess: 1: Success after binutils/gcc: 2 commits new aa6aed3b18 85: onsuccess: 1: Success after binutils/gcc: 19 commits new a4933cd65e 86: onsuccess: 1: Success after binutils/gcc: 8 commits new 50554c6be4 87: onsuccess: 1: Success after gcc: 6 commits new 38a8985a23 88: onsuccess: 1: Success after binutils/gcc: 2 commits new 54d0eecf58 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new ae1d3a773e 90: onsuccess: #1645: 1: Success after gcc: 2 commits new 085781dc93 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new aa87d461ae 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new d86ad8b4d8 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new 1a8a94424f 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new b3aff31b48 95: onsuccess: #1653: 1: Success after gcc: 13 commits new 98be224779 96: onsuccess: #1654: 1: Success after gcc: 5 commits new 902d04919e 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new 7e56d81cf3 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new 30fdf37fe1 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new ff6fbf78e1 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new 90047282d0 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new 3241f2b9bd 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new 9a0a51adf6 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new aacd77c830 104: onsuccess: #1700: 1: Success after gcc: 2 commits new d370ea5cab 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new 87af378b59 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 4defcd1a68 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new a0f38b403c 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new aeb0c28ace 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new 0ff82bb951 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new 1642747b6e 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new 4aa46f77e4 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new c1dfc9134e 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 33637620d6 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new a9353efa95 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new dd14216aca 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new 38feedcb28 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new 5b859cc12f 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new 927ca46bcd 119: onsuccess: #1715: 1: Success after binutils: 4 commits new a9bd906539 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new 38858fb9a9 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new 104c163ed1 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new 5caa2e9d7d 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new 6f30bedab0 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new d96c939f03 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new 1f90718fd9 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new 32452662a8 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new e707b33b93 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new 418cdb45b8 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new e90fabee32 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 857d28c7c2 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new e74c098101 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new 9a77bc911e 133: onsuccess: #1733: 1: Success after binutils: 3 commits new 6babdd5f75 134: onsuccess: #1736: 1: Success after binutils: 3 commits new 0f847dc067 135: onsuccess: #1739: 1: Success after binutils: 4 commits new 73e1c434a3 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new 12bf124d59 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new e045233620 138: onsuccess: #1749: 1: Success after binutils: 5 commits new 3d62c8c3b5 139: onsuccess: #1753: 1: Success after binutils: 5 commits new c87e1ba598 140: onsuccess: #1756: 1: Success after binutils: 3 commits new 45a325d248 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new a63cf9b421 142: onsuccess: #1761: 1: Success after gcc: 83 commits new e796d972e6 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new 230cd5d0fb 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new fedc7529b1 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new 570101c49c 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new 99e3ffa425 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits new f46b6a7bac 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits new 6ee61f7aa9 149: onsuccess: #1769: 1: Success after gcc: 3 commits new 4c324ec616 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] new 37fb39185f 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] new 8d223f4766 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits new 2b0108d054 153: onsuccess: #1773: 1: Success after gcc: 4 commits new 06b291ca22 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits new 937e6e148a 155: onsuccess: #1775: 1: Success after binutils: 2 commits new 68d965219e 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits new c49d14180c 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits new bc61943692 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits new 41a1f804f4 159: onsuccess: #1779: 1: Success after gcc: 2 commits new b5c0092301 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits new 8dc5308d16 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits new 7f6c2548de 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits new e81b9d08b4 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits new 5acf4ab954 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits new c6ed0937ba 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits new 7a710ebfc5 166: onsuccess: #1786: 1: Success after gcc: 10 commits new df6dba7504 167: onsuccess: #1787: 1: Success after gcc: 8 commits new 1839463965 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits new 771923087a 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 commits new 4a824284ef 170: onsuccess: #1790: 1: Success after binutils/gcc: 9 commits new 62e1794f3d 171: onsuccess: #1791: 1: Success after binutils/gcc: 7 commits new c6637849e0 172: onsuccess: #1792: 1: Success after binutils/gcc: 4 commits new 9ba80d5e45 173: onsuccess: #1793: 1: Success after gcc: 12 commits new e61ce88b65 174: onsuccess: #1794: 1: Success after binutils/gcc: 17 commits new 5135aae741 175: onsuccess: #1795: 1: Success after binutils/gcc: 7 commits new d90b3e00c2 176: onsuccess: #1796: 1: Success after binutils/gcc: 3 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 (5d8febf5f6) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (d9 [...] 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 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 51640 -> 52708 bytes 04-build_abe-gcc/console.log.xz | Bin 234120 -> 238068 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3856 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2964 -> 3392 bytes 07-check_regression/console.log.xz | Bin 5076 -> 4544 bytes 07-check_regression/mail-body.txt | 51 - 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 81 +- 08-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 53 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 2798436 -> 2774268 bytes sumfiles/g++.sum | 106 +- sumfiles/gcc.log.xz | Bin 2378944 -> 2380644 bytes sumfiles/gcc.sum | 4488 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 915660 -> 911692 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204600 -> 204704 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 462680 -> 468404 bytes sumfiles/libstdc++.sum | 10 +- 32 files changed, 2399 insertions(+), 2568 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (1f7afb67f3 -> 19a1909b8b)

by git＠git.linaro.org

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-aarch64 in repository toolchain/ci/base-artifacts. discards 1f7afb67f3 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 4d8774fa85 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards 2591ac7a9b 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 2104342eb8 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards c506410fa9 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 05d64ea5bf 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 70e268c690 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 6eac475fe6 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards fa7606c082 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards dc67714697 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 220bbfa96f 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards ad5b516905 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 28a5bdc30d 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards f935ccc50a 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 7f242e2c11 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards d5d55f946c 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards c4e3da3956 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 68b1a9798a 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 481221605b 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 60107ff445 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 155889dd55 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards a799cebbe9 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards fb6143b13e 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 4b82292c5d 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 9b3e63538b 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards e48dc0c737 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards acb5b8ae99 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 2cd85c60f8 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 733a78e715 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 33f2b9d88e 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 49178c341c 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards e1a35b1e96 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards f4e9e36a0f 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards ada1d33818 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 7bdebcd9b7 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 33bdc20b85 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards c80fb0f69a 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 90a6ee30c2 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards d52a26adde 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 6711fb1ab8 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards a2359ac45d 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards fdc4b6915b 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 169ab687ac 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 4930e4b9ca 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 1425c473e6 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 7054f484cc 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards d6d19326dc 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 1ab7f09e7f 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 3ade4b4389 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 9518cfd335 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards d7ce916451 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards f5a80ed131 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 99a5d856cf 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 8cd676c6b2 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 5d9cd90925 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards aa71205943 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards ff4334a77e 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 20d9fcad59 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 021c0ade0d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards aaeff03dc0 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 27be44135c 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 0e2c3a9afb 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 47faa46263 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 45ae2bcfe3 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 372db16cdc 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards bb67332941 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards ff8a993810 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 1812a33fcf 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 49c59bb051 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 3f84fe5581 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards b22ee34f35 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 68adcff119 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 461ec7ec4d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 571cbe89a6 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards af2e9c8189 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 797160124d 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 70b4ce501e 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 1cd7c94584 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards f7d521dad0 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 8af1d2a75d 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 66e2f26cfa 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 82502ce77f 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards c96db3ac93 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 729e8972cf 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 296a083542 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 1963748462 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 66f889d8d6 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards afdbfed702 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 54b90716f6 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards f993a7ea13 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 440f5d6a9d 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards cac180946a 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 9cbea1feac 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards b9d234f5d2 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 1974b37c48 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 82b3ef6b0c 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c54713a387 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0f86a44d7e 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards e7aad8cde0 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 14ebae6124 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b7817d2281 75: onsuccess: 1: Successful build after linux: 44 commits new 4a3b97eb01 75: onsuccess: 1: Successful build after linux: 44 commits new 39b7336e9e 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 420ad251c7 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 128da2251c 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 0599a70943 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9b4158a5e7 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1dfdae1ce0 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new ab88fcf918 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new fcbefa43b7 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 0bea8fa7ee 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 81935a3f1a 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 50e4c51a96 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 7a6a6dbc94 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new f1c3e6dd20 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 06bddf40bf 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 33d1fa1f9d 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 8eda5e8c96 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 90c4a82b22 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3c8f3cf064 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new ae5fcf5a24 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 5e82128882 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new beeb15d4f1 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 21d10c223a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 84738e472a 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 45db185a5b 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new f88336034b 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new bdbd84caf6 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 00235d1f93 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new abe3035f55 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new b2b2dfb136 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 6d656c802f 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new bc5a9315c7 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 4d50fd23ea 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 2e9f468705 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new a3833a4d97 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new f660066145 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 7c254b46b8 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new bca6124e86 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 819c712f27 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 61b94c2575 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new b0fa7bed55 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 642c75aac9 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new a26f74d75d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 8a6e839b7f 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 6b7e318cfe 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 62be23dfce 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new d30693f4d7 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 6fe414c055 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 91f6c52c98 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 8a3cd82e98 124: onsuccess: #2159: 1: Success after linux: 23 commits new c63957deb0 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 8f2b0a770f 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 184285697f 127: onsuccess: #2162: 1: Success after gcc: 9 commits new db1b0c9029 128: onsuccess: #2163: 1: Success after linux: 23 commits new fd531b9cfe 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new e805d7f386 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 3287920274 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 48da575c22 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new adc8b0725b 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new db35c06119 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 0dc7ca4d91 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new c7baa4f85a 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 12d30c91f8 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 3c6dd08535 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 6d85e978bb 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 81401379c5 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 7e2602bdc0 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 9d11439f1f 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 9a1d16493b 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new b7258c87d4 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new fb05391b41 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new cd3a596e0d 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 2197e4dabc 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new cfbd2d0c55 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new ba22dd1df9 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 351544510e 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 555bf676c6 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 6ebd35f1b3 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new cf92d332d9 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 924eb10eb4 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 8488f77197 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 3214c3fd58 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new d13758f6e7 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new e3818046f8 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 655d588be9 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 46708f3151 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new e9e07e49ca 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 194c84eadf 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 3f6ae22dc6 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new a73101c555 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new ed5de251ed 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new fa0fb3ab77 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new d14da345a5 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new e574fd7ef5 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new d98f35c58d 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new ab83d54e18 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new a791fc71cc 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new b2f32c5837 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new b33a8eba9e 173: onsuccess: #2208: 1: Success after gcc: 10 commits new cd30d35efb 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new fd6319c799 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 19a1909b8b 176: onsuccess: #2211: 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 (1f7afb67f3) \ 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 1712 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 31320 -> 30960 bytes 04-build_abe-stage1/console.log.xz | Bin 73284 -> 74712 bytes 06-build_abe-linux/console.log.xz | Bin 9048 -> 9204 bytes 07-build_abe-glibc/console.log.xz | Bin 240704 -> 240712 bytes 08-build_abe-stage2/console.log.xz | Bin 205472 -> 204396 bytes 09-build_abe-gdb/console.log.xz | Bin 38200 -> 37424 bytes 10-build_abe-qemu/console.log.xz | Bin 32048 -> 32052 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2940 -> 3668 bytes 13-check_regression/console.log.xz | Bin 7000 -> 6212 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 123 +- 13-check_regression/results.compare | 32 +- 13-check_regression/results.compare2 | 95 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 46 +- 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 | 125 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 26 - sumfiles/g++.log.xz | Bin 3424824 -> 3428376 bytes sumfiles/g++.sum | 116 +- sumfiles/gcc.log.xz | Bin 3034024 -> 3030436 bytes sumfiles/gcc.sum | 4422 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1037348 -> 1032772 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202248 -> 202468 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 427756 -> 430016 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 2398 insertions(+), 2690 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 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/release-aarch64-check_bootstrap updated (e7ca508d45 -> 410f99136f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check_bootstrap/release-aarch64-check_bootstrap in repository toolchain/ci/base-artifacts. from e7ca508d45 15: onsuccess: #138: 1: Success after binutils/gcc: 7 commits new 410f99136f 16: onsuccess: #139: 1: Success after binutils/gcc: 7 commits The 1 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 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 37924 -> 38132 bytes 04-build_abe-bootstrap/console.log.xz | Bin 263892 -> 265972 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3848 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 2304 -> 2412 bytes 07-check_regression/console.log.xz | Bin 5408 -> 5508 bytes 07-check_regression/extra-bisect-params | 2 +- 07-check_regression/fails.sum | 14 +- 07-check_regression/mail-body.txt | 58 +- 07-check_regression/results.compare | 23 +- 07-check_regression/results.compare2 | 52 +- 07-check_regression/results.regressions | 23 +- 08-update_baseline/console.log | 9 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/mail-body.txt | 58 +- manifest.sh | 18 +- results | 23 +- sumfiles/g++.log.xz | Bin 3594932 -> 3564644 bytes sumfiles/g++.sum | 42 +- sumfiles/gcc.log.xz | Bin 3126540 -> 3111088 bytes sumfiles/gcc.sum | 3910 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 1071720 -> 1074124 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2348 -> 2348 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 207548 -> 208292 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2728 -> 2724 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 454368 -> 438788 bytes sumfiles/libstdc++.sum | 2 +- 34 files changed, 2171 insertions(+), 2081 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled updated (e8d5f0931b -> 2d3baa009b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled in repository toolchain/ci/base-artifacts. from e8d5f0931b 55: onsuccess: #451: 2: Success after binutils/gcc: 57 commits new 2d3baa009b 56: onsuccess: #452: 2: Success after binutils/gcc: 41 commits The 1 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 1704 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 38668 -> 38148 bytes 05-build_abe-bootstrap_profiled/console.log.xz | Bin 515368 -> 515676 bytes 06-check_regression/console.log.xz | Bin 3100 -> 3140 bytes 07-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 13 files changed, 24 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-next-allmodconfig updated (8fd226180a -> 564c90483a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-next-allmodconfig in repository toolchain/ci/base-artifacts. from 8fd226180a 15: onsuccess: #707: all: Success after binutils/gcc/linux/q [...] new 564c90483a 16: onsuccess: #708: all: Success after binutils/gcc/linux/q [...] The 1 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 1724 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30188 -> 30348 bytes 04-build_abe-stage1/console.log.xz | Bin 69024 -> 68516 bytes 05-build_abe-qemu/console.log.xz | Bin 32112 -> 32260 bytes 06-build_linux/console.log.xz | Bin 3064 -> 3068 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4244 -> 4036 bytes 08-check_regression/mail-body.txt | 4 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 19 files changed, 29 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-aarch64-bootstrap_lto updated (05992b88d0 -> 719b912c71)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/release-aarch64-bootstrap_lto in repository toolchain/ci/base-artifacts. from 05992b88d0 15: onsuccess: #129: 2: Success after binutils/gcc: 7 commits new 719b912c71 16: onsuccess: #130: 2: Success after binutils/gcc: 7 commits The 1 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 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2708 bytes 04-build_abe-binutils/console.log.xz | Bin 37880 -> 38140 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 272564 -> 272604 bytes 06-check_regression/console.log.xz | Bin 2844 -> 2724 bytes 07-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- manifest.sh | 18 +++++++++--------- 10 files changed, 13 insertions(+), 13 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_lto updated (e7a1d01f6b -> 85bb07c05d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_lto in repository toolchain/ci/base-artifacts. from e7a1d01f6b 61: onsuccess: #461: 2: Success after binutils: 8 commits new 85bb07c05d 62: force: #463: 2: Success after gcc: 32 commits The 1 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 1624 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 38060 -> 38552 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 276984 -> 281144 bytes 06-check_regression/console.log.xz | Bin 2656 -> 2728 bytes dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 ++++++++-------- 11 files changed, 13 insertions(+), 13 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-stable-defconfig updated (9efda42c42 -> e3ef650169)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-stable-defconfig in repository toolchain/ci/base-artifacts. from 9efda42c42 13: onsuccess: #417: boot: Success after binutils/gcc/linux/ [...] new e3ef650169 14: onsuccess: #418: boot: Success after binutils/gcc/linux/ [...] The 1 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 1692 -> 1900 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 29920 -> 29932 bytes 04-build_abe-stage1/console.log.xz | Bin 86676 -> 86936 bytes 05-build_abe-qemu/console.log.xz | Bin 31688 -> 31476 bytes 06-build_linux/console.log.xz | Bin 3304 -> 3332 bytes 07-boot_linux/console.log.xz | Bin 5836 -> 5828 bytes 08-check_regression/console.log.xz | Bin 4248 -> 3976 bytes 09-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 33 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022