Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[binutils-gdb] branch binutils-2_39-branch updated (bab2efac55f -> 18c74565c4a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch binutils-2_39-branch in repository binutils-gdb. from bab2efac55f Automatic date update in version.in new 18c74565c4a Automatic date update in version.in 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[binutils-gdb] branch master updated (06bed95d8d2 -> f7052ade774)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 06bed95d8d2 Automatic date update in version.in new f7052ade774 Automatic date update in version.in 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 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 (2ac5ce1b8e -> 8252ad57c2)

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 2ac5ce1b8e 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] discards 750b3e72bb 149: onsuccess: #1769: 1: Success after gcc: 3 commits discards b0d553bd14 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits discards 4529d6ad97 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits discards ebe3834494 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards 0fe26985b9 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards 34d37ef84c 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards 30ebe219b9 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards ccc766bd28 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards 03c8fb9b33 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards c14417dbd4 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards ad692ccb6d 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards f21966f8e7 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards 5e66b4d1e3 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards fc80d705b4 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards 49d4c7855a 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards 2b3a7ba163 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards 91400bedf9 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 11efad646c 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards 1d19059d70 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards 1919048838 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards 22f25d731c 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards 7b46c6d68c 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards e5f568694e 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards 3ca8308c4f 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards 5d4e90b16d 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards c97a3c4e71 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards b3a899cf74 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards 6265cd1642 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards fb6c03cb6c 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards d7a484dacf 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards 87647a93ae 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards f40152f9c1 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards a9090065d1 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards 80e09b395b 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards 53bc4af2e7 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards 756e582fc4 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards ad41295a92 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards bc5b1cebbf 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards e5cc6d0a68 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards 3b3d3d17f8 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 1388bb18bd 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards 9cc51ef2f6 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards f72268e5d9 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards da378f930c 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards 936283142d 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards 18614a4d36 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards be43dcc824 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards 94e381563e 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards 29b0014b66 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards acf389e13d 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards 4b460ced55 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards 624367e711 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards c1ce389e79 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards 74c3c868b5 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards 5dffc74a7c 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards 27ac58bd00 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards e98a464d58 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards b43c4b1fb6 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards ff2f0025a3 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards f7a4b3e3b0 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards 2a8660c1c5 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards 8fc05fdad7 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards 70bc6134ae 87: onsuccess: 1: Success after gcc: 6 commits discards fb6aee0b83 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards a4df7a023a 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards f4a0212584 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards 8971e6f23c 83: onsuccess: 1: Success after gcc: 14 commits discards c4c84a9723 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 305886de78 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards aae67f1013 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards 85d610458b 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards 71265270c3 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards 25ef63ec09 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 38840e6591 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 004a7d8459 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards e1ac1e2f15 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards 43fd712c91 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 4218f74da8 72: onsuccess: 1: Successful build after baseline build: no [...] discards 51a223ac0c 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards d2d7bc6e5f 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards d6b77bbc47 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] discards 0e140aaf07 68: onsuccess: 1: Successful build after gcc: 2 commits discards 06a9c238f1 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 11840fe018 66: onsuccess: 1: Successful build after gcc: 4 commits discards 580097dfd6 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 3a426ff3bb 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards fc0667105a 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 4c41da5845 62: onsuccess: 1: Successful build after gcc: 4 commits discards cf3f0362b6 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 1131868960 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards 7566dfb793 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits discards 0d469dd76b 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] discards c9c3492b8e 57: onsuccess: 1: Successful build after binutils: 2 commits discards 37d516fd75 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards 2763692e68 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards 5d9f5d80ab 54: onsuccess: 1: Successful build after gcc: 5 commits discards 6c77ea39ee 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards ffb25ce2f8 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 4c9bfad595 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 1a2de760e5 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 2154b5ece1 50: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 6aada5cdd5 51: onsuccess: 1: Successful build after binutils/gcc: 4 commits new a17d5e5306 52: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 3431e899a6 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new febc174e1b 54: onsuccess: 1: Successful build after gcc: 5 commits new ed5e039ced 55: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 3e68e23104 56: onsuccess: 1: Successful build after binutils/gcc: 7 commits new 69ec72b5c3 57: onsuccess: 1: Successful build after binutils: 2 commits new 33d3d299c8 58: onsuccess: 1: Successful build after binutils: ld: pe: M [...] new 5b82ec5ee5 59: onsuccess: 1: Successful build after binutils/gcc: 29 commits new c2d4e6e306 60: onsuccess: 1: Successful build after binutils/gcc: 12 commits new 5183e91c40 61: onsuccess: 1: Successful build after binutils/gcc: 8 commits new f7797fe175 62: onsuccess: 1: Successful build after gcc: 4 commits new d0a7cb0089 63: onsuccess: 1: Successful build after binutils/gcc: 3 commits new d1c786b33e 64: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 14bde71a79 65: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 0336a58b77 66: onsuccess: 1: Successful build after gcc: 4 commits new 053df96435 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new e7c706baff 68: onsuccess: 1: Successful build after gcc: 2 commits new c409d92978 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] new 137caefcc5 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 1f03851f78 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new 1482db717f 72: onsuccess: 1: Successful build after baseline build: no [...] new c6676566b4 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 2eba5ac023 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new 4210965588 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 316f0ee0c7 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 270c123e92 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 5c496db8f7 78: onsuccess: 1: Success after binutils/gcc: 17 commits new c4ea4fb4ae 79: onsuccess: 1: Success after binutils/gcc: 23 commits new 61bb6261c4 80: onsuccess: 1: Success after binutils/gcc: 8 commits new 26dfd5985e 81: onsuccess: 1: Success after binutils/gcc: 8 commits new 7de068bc28 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 69b8026f37 83: onsuccess: 1: Success after gcc: 14 commits new b13c8660da 84: onsuccess: 1: Success after binutils/gcc: 2 commits new f5c76203a5 85: onsuccess: 1: Success after binutils/gcc: 19 commits new a856f46a20 86: onsuccess: 1: Success after binutils/gcc: 8 commits new c8fce2df60 87: onsuccess: 1: Success after gcc: 6 commits new e9689c610b 88: onsuccess: 1: Success after binutils/gcc: 2 commits new 7f482a0c3a 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new c9e081261d 90: onsuccess: #1645: 1: Success after gcc: 2 commits new 7a2c26e4d6 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new 5ecfc6055d 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new 9dd915a8bd 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new fc74b2651b 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new 58e107dab1 95: onsuccess: #1653: 1: Success after gcc: 13 commits new cebdc1eaa9 96: onsuccess: #1654: 1: Success after gcc: 5 commits new d97f9eb513 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new 19340a4c26 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new 17be3ca69d 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new 99afe472cf 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new 402b4d3fc1 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new 24d25f98af 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new 6c83ac685f 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new 393235d6f5 104: onsuccess: #1700: 1: Success after gcc: 2 commits new 63a661d43c 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new e6a5a991af 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 43f9adf9a0 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new e1425e0ce3 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new cd4767e8ca 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new 1d5c88298b 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new b8ca22c2a6 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new 364e67efca 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new 74ca8c1d95 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 6545a60580 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new 505f86683f 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new 8b8ffbb53a 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new 32e62b1141 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new 5b0aa135f4 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new 2a4d03dc55 119: onsuccess: #1715: 1: Success after binutils: 4 commits new 0ec75e473a 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new c38afaab6c 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new 65d7f8c81e 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new 29cc79515e 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new 7827dc6653 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new ad11990c1c 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new 1c1a00e790 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new b57608edf3 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new bd116e8eeb 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new fcf2262f3c 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new 90e1910555 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 12cf2f6fcb 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new 1dc76b3afb 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new 7efdf16a78 133: onsuccess: #1733: 1: Success after binutils: 3 commits new cb6e896de8 134: onsuccess: #1736: 1: Success after binutils: 3 commits new f883b02837 135: onsuccess: #1739: 1: Success after binutils: 4 commits new 2fd8f7a994 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new 1e7880fabb 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new 9e57021a49 138: onsuccess: #1749: 1: Success after binutils: 5 commits new df8b26136f 139: onsuccess: #1753: 1: Success after binutils: 5 commits new e49f5d623a 140: onsuccess: #1756: 1: Success after binutils: 3 commits new 61a132bc58 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new f004d68850 142: onsuccess: #1761: 1: Success after gcc: 83 commits new 37c804988e 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new f1d7283423 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new e777791f3c 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new 72431b586c 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new 5f314de0f4 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits new d8c67e4f11 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits new 439eafbee9 149: onsuccess: #1769: 1: Success after gcc: 3 commits new 4952b9848e 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] new 8252ad57c2 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] 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 (2ac5ce1b8e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (82 [...] 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 1644 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 50620 -> 51336 bytes 04-build_abe-gcc/console.log.xz | Bin 233228 -> 233392 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3880 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2644 -> 2620 bytes 07-check_regression/console.log.xz | Bin 4396 -> 4616 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 43 +- 08-update_baseline/console.log | 58 +- 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 | 14 +- sumfiles/g++.log.xz | Bin 2815440 -> 2784096 bytes sumfiles/g++.sum | 112 +- sumfiles/gcc.log.xz | Bin 2372740 -> 2375072 bytes sumfiles/gcc.sum | 4718 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 904396 -> 912312 bytes sumfiles/gfortran.sum | 70 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 205052 -> 204536 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2532 -> 2536 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 465744 -> 463828 bytes sumfiles/libstdc++.sum | 10 +- 30 files changed, 2566 insertions(+), 2511 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 (e6438df687 -> d8c3fe1d26)

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 e6438df687 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards c186696221 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 3781117740 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 2eb2e09f04 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 81952a59ca 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 6e26704665 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards e1e13951b5 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 4a1f24a92e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards f3bf294a8c 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 0746420734 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards bfaee73947 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards a33ded6894 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 36622b15c3 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 99c6da183c 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 32f5482ab3 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 9da815801b 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards c3172eb8b0 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 7dfd0ce638 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards ef9712fcc0 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 1acc64abd2 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 5e61f8e71e 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 5618709d8f 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 5ad8f3420c 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 9e88a336eb 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 899185f3db 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 23f66441df 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 116c2d91c3 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 9336ab6f63 124: onsuccess: #2159: 1: Success after linux: 23 commits discards ecac712530 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards f281393b0c 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards dc5a37d7a8 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 87740866b4 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 6cca899bee 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards c45308d954 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 16770253ac 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards e653209cb1 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 8c0b6e2f75 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 2e67d1c7f2 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 52108643d0 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8e118c9b3d 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 4f09e584e0 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards b8552d8f41 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 14aead96a8 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 0b921c00ce 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards fca395bc31 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards c4b843f500 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 23bbb22461 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 1a00e6566f 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards a94519ca0b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 1fa98d81a3 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 1bd70fdbe8 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 82543d9b4b 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 16bd20a9f3 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards b20db61f5d 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 9d8875decb 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 764e790fd7 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards d31ce8d33e 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards fe21c4113c 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 93c83a4f89 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 5e282f3b8a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 60e1688217 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards ee20939a8a 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards d3653ccfc4 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards f2e9c352d7 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards b731a62853 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards cd8c03396b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards fda7541c8c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards fb22afbf7d 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards a328704a65 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 7f7c600717 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 4b5d78e4a5 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 8513f6306f 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ce537a1ca0 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f3761975d2 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 26e49df14a 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards b5a6625b93 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 92fdb6add9 75: onsuccess: 1: Successful build after linux: 44 commits discards f50420b867 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 9c3e447af1 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7bf7b52fb3 72: onsuccess: 1: Successful build after linux: 12 commits discards c9e14f5f52 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards d69c299ed5 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards a8d51ec456 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 14585422cc 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1b02fbe001 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards b410f816a6 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards e05ef882e9 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3e57bc0e0b 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fe184a6add 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards fc00e91859 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards dcf44eff59 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 3ff75e1fdf 60: onsuccess: 1: Successful build after glibc: 2 commits discards 577e843f00 59: onsuccess: 1: Successful build after binutils: 2 commits discards 60443b2561 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 59655c07ec 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 88915b49f7 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c275f03fb4 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 43b9d4a9b6 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 08743b3fdd 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards b3a2507915 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 0bf7feca28 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d4920f934f 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b8d26046d6 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new acee7af3c1 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 3ac44e44b8 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 18614bd02a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 00c5bbc850 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e4e68beeaa 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0417ff5cca 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 7b18926549 59: onsuccess: 1: Successful build after binutils: 2 commits new 092ade8c85 60: onsuccess: 1: Successful build after glibc: 2 commits new f9de5fa520 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 6a0d49642d 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 5becb79a90 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2ee14d9715 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dc34eed820 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ae503a0953 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new dfdeb3c4da 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 220e18170c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4c04f277f9 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 0761aa3ce4 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new aef1f635d3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new cfcf575760 72: onsuccess: 1: Successful build after linux: 12 commits new 52d4b1de96 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ad2f7f09db 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 1afdbc4eae 75: onsuccess: 1: Successful build after linux: 44 commits new 8656b64b8e 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 89e374cb9c 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new c73ada8051 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new c6e1e974d4 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1363080bbd 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d523cedda7 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 40f13e8a2b 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new a2834d31ec 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 98eca2b187 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 5613d12e4c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new b0d88fb795 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 519861e50a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 1761460875 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 3de00f745d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new a900ed8698 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new d9211b8db1 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 6ec4826787 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new ba2c8b932b 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 5872eccd35 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new c11ef400d6 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new ae02da8b4c 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 177f987fc3 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 983956e668 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 0067b93e69 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new ac8f36cab4 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 934a139ae3 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 9bbf7a0cb8 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 03c591b401 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 1f8acc9750 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new b5100f8b66 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 8dfd72cfe3 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new cb838bce82 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 0b0d7447c4 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 5d755e1c8e 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 165fce0b7e 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 48e68689d2 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 1b8fbaccce 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new aa99a97982 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 32fb46244e 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 17514b4380 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 2a1cfdaeef 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 7fac25b697 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 466b9fb17c 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new b1b08ea7ed 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 1ccdd20e86 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new be4e97d9da 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 17d9b587a1 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new cd7448bc58 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 8eb77bbd6e 124: onsuccess: #2159: 1: Success after linux: 23 commits new da42910593 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 39e417160d 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 5965b9088a 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 636b0befc1 128: onsuccess: #2163: 1: Success after linux: 23 commits new fe3ae2a3e5 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new e78b22551a 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 597e496d36 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 489d03abe6 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 6778a7124c 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 4051a5662e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new dcc22bcec8 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 3b23288adb 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 8ab35bf65e 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 7e00e1b7ba 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new a7758c4970 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new cca0bca499 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 9b31385d80 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 8a94dc384a 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new c308c9f499 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new f34e05c534 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 6f49237c28 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new cf5937fd21 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 03652fcecc 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new f04888c058 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 18433d903f 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new b090ef2ba0 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 17fe5be600 151: onsuccess: #2186: 1: Success after gcc: 2 commits new d8c3fe1d26 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 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 (e6438df687) \ 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 1704 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30292 -> 30156 bytes 04-build_abe-stage1/console.log.xz | Bin 72612 -> 72668 bytes 06-build_abe-linux/console.log.xz | Bin 8556 -> 8920 bytes 07-build_abe-glibc/console.log.xz | Bin 239464 -> 240060 bytes 08-build_abe-stage2/console.log.xz | Bin 203232 -> 203076 bytes 09-build_abe-gdb/console.log.xz | Bin 37504 -> 37404 bytes 10-build_abe-qemu/console.log.xz | Bin 31836 -> 31844 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2848 -> 2752 bytes 13-check_regression/console.log.xz | Bin 9660 -> 19812 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 272 +- 13-check_regression/mail-body.txt | 244 +- 13-check_regression/results.compare | 410 ++- 13-check_regression/results.compare2 | 4149 ++++++++++++++++++++----- 13-check_regression/results.regressions | 146 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 246 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 146 +- sumfiles/g++.log.xz | Bin 3405440 -> 3414820 bytes sumfiles/g++.sum | 2617 ++++++---------- sumfiles/gcc.log.xz | Bin 3026724 -> 3030236 bytes sumfiles/gcc.sum | 5177 +++++++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 1030676 -> 1033340 bytes sumfiles/gfortran.sum | 34 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202360 -> 202640 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2652 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 421788 -> 427340 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 8159 insertions(+), 5413 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_native_check_gcc/master-arm updated (72ef2b43d3 -> e01db3839c)

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_gcc/master-arm in repository toolchain/ci/base-artifacts. from 72ef2b43d3 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new e01db3839c 54: onsuccess: #497: 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 1676 -> 1872 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 50776 -> 52220 bytes 04-build_abe-gcc/console.log.xz | Bin 232840 -> 234696 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8588 -> 8900 bytes 07-build_abe-glibc/console.log.xz | Bin 232340 -> 232288 bytes 08-build_abe-gdb/console.log.xz | Bin 48560 -> 49700 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3808 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2612 -> 2688 bytes 11-check_regression/console.log.xz | Bin 7984 -> 6528 bytes 11-check_regression/mail-body.txt | 73 - 11-check_regression/results.compare | 27 +- 11-check_regression/results.compare2 | 333 +-- 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 | 75 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 2872312 -> 2843824 bytes sumfiles/g++.sum | 136 +- sumfiles/gcc.log.xz | Bin 2487760 -> 2496020 bytes sumfiles/gcc.sum | 4959 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 942832 -> 946996 bytes sumfiles/gfortran.sum | 70 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 217444 -> 217312 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 464364 -> 464360 bytes sumfiles/libstdc++.sum | 10 +- 38 files changed, 2702 insertions(+), 3059 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_O3 updated (35ef69a2e0 -> 802b4e95d5)

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_O3 in repository toolchain/ci/base-artifacts. from 35ef69a2e0 52: onsuccess: #445: 1: Success after gcc: 17 commits new 802b4e95d5 53: onsuccess: #446: 2: Success after binutils/gcc: 152 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 1716 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 37780 -> 37996 bytes 05-build_abe-bootstrap_O3/console.log.xz | Bin 79280 -> 272812 bytes 06-check_regression/console.log.xz | Bin 2672 -> 3244 bytes 06-check_regression/mail-body.txt | 13 +------------ 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 | 15 ++------------- mail/mail-subject.txt | 2 +- manifest.sh | 19 ++++++++++--------- results | 2 +- 15 files changed, 28 insertions(+), 40 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/llvm-release-arm-lts-allmodconfig updated (40cc2a2303 -> eb561b3562)

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/llvm-release-arm-lts-allmodconfig in repository toolchain/ci/base-artifacts. from 40cc2a2303 19: onsuccess: #266: 21887: Success after binutils/llvm/linu [...] new eb561b3562 20: onsuccess: #267: 21892: Success after binutils/llvm/linu [...] 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 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 29952 -> 29780 bytes 04-build_kernel_llvm/console.log.xz | Bin 64264 -> 64560 bytes 05-build_abe-qemu/console.log.xz | Bin 30920 -> 31388 bytes 06-build_linux/console.log.xz | Bin 4604 -> 4612 bytes 08-check_regression/console.log.xz | Bin 4112 -> 4344 bytes 08-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 18 files changed, 27 insertions(+), 27 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_debug updated (3d216a3105 -> c27f863b34)

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_debug in repository toolchain/ci/base-artifacts. from 3d216a3105 15: onsuccess: #139: 2: Success after binutils/gcc: 9 commits new c27f863b34 16: onsuccess: #140: 2: Success after binutils/gcc: 15 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 1672 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 37236 -> 37504 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 262420 -> 263488 bytes 06-check_regression/console.log.xz | Bin 2860 -> 2924 bytes 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 | 20 ++++++++++---------- 12 files changed, 16 insertions(+), 16 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 (b01e5874e3 -> 93ad7712dd)

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 b01e5874e3 54: onsuccess: #453: 1: Success after gcc: 17 commits new 93ad7712dd 55: onsuccess: #454: 2: Success after binutils/gcc: 152 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 1716 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 38352 -> 37288 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 79932 -> 274656 bytes 06-check_regression/console.log.xz | Bin 2672 -> 3140 bytes 06-check_regression/mail-body.txt | 13 +------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 15 ++------------- mail/mail-subject.txt | 2 +- manifest.sh | 19 ++++++++++--------- results | 2 +- 14 files changed, 19 insertions(+), 40 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-norov-allyesconfig updated (f04119c835 -> 1e52960fdc)

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-norov-allyesconfig in repository toolchain/ci/base-artifacts. from f04119c835 10: onsuccess: #39: all: Success after binutils/gcc/qemu: 17 [...] new 1e52960fdc 11: onsuccess: #40: all: Success after binutils/gcc/linux/qe [...] 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 1712 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30576 -> 30292 bytes 04-build_abe-stage1/console.log.xz | Bin 69020 -> 68796 bytes 05-build_abe-qemu/console.log.xz | Bin 31500 -> 31996 bytes 06-build_linux/console.log.xz | Bin 3428 -> 3424 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 3692 -> 4188 bytes 09-update_baseline/console.log | 8 ++++---- 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, 28 insertions(+), 28 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