Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_lto updated (abbac0802c -> b01e5874e3)

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 abbac0802c 53: force: #452: 1: Failure after basepoints/gcc-13-2887-gb0 [...] new b01e5874e3 54: onsuccess: #453: 1: Success after gcc: 17 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 1696 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 38444 -> 38352 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 83336 -> 79932 bytes 06-check_regression/console.log.xz | Bin 3420 -> 2672 bytes 06-check_regression/jira-body.txt | 2 +- 06-check_regression/mail-body.txt | 20 +- 06-check_regression/mail-subject.txt | 2 +- 06-check_regression/results.regressions | 11 - 06-check_regression/trigger-bisect | 2 - 06-check_regression/trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 1061 ----------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 20 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 11 - 23 files changed, 33 insertions(+), 1127 deletions(-) delete mode 100644 06-check_regression/results.regressions delete mode 100644 06-check_regression/trigger-bisect delete mode 100644 06-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- 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 updated (bfe53c88b3 -> b6a90f490c)

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 in repository toolchain/ci/base-artifacts. discards bfe53c88b3 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits discards 21862ede51 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits discards ce85d5ee45 146: onsuccess: #1573: 2: Success after binutils: 7 commits discards dc4d32b752 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits discards 798122fdb0 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits discards 39c09ceccd 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards 0d77997693 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards cd99650c7e 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards cd564ae176 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards 5da55089de 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards a9cd8164c8 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards ce0eb295a5 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards 7e4dcf8c0e 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards d70e0519ea 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards c4114c2212 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards 67cf755765 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 467cc28510 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards 0b4adb3577 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards 7b95756e2d 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards da46fa1043 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards ccfc395e86 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 17cb94fe80 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards cb46017dc0 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 9653bb3b82 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 9255e6a254 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards ea48fad149 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 6ce87c5e71 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards fc20a7edd4 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards d3afb20cb9 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards d29d010349 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 51931a55cf 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards a2086de446 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards b5d479c7af 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards a0622307c4 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 2eae2afc85 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 2a2066fe60 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 704a202270 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 756c0fd212 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards ab67871510 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 97c6fcd8ff 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 8a7c421e7e 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards ddc292b161 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 6484142a4b 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards e211126c09 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards d9de502f2b 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards f7f3579e1f 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 2df7ee7142 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 2cf4546282 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards f66075ad4c 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 08e2401af8 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards b618d094b4 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 10ead55aa7 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 964fb32c07 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 4a98d28fe8 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 63ecc62504 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 5c4f43fc2f 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 1b778ac8d3 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 970843b721 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 1b0410ee6c 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 508ad15a5f 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards fd42cd5f49 88: onsuccess: 1: Success after gcc: 20 commits discards 88797b3299 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 0dd23ae23e 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 7a523d9087 85: onsuccess: 2: Success after binutils: 4 commits discards 2bda9906e5 84: onsuccess: 2: Success after gcc: 9 commits discards b9626ea56a 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 159eda4d2a 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards df9ff84332 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards daaaa5d296 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 97f9f9716c 79: onsuccess: 1: Successful build after gcc: 3 commits discards 6f43d5fa1c 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 30705c1e44 77: force: 2: Successful build after gcc: 32 commits discards af27bcd5d9 76: onsuccess: 2: Successful build after binutils: 10 commits discards 879e13f457 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 5fccf8909f 74: onsuccess: 2: Successful build after gcc: 13 commits discards e332c3ebaf 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 3c1c002458 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 62902d0745 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a219dbe1ff 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 0f44d398c0 69: onsuccess: 2: Successful build after baseline build: no [...] discards d01357bf89 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 0b20fbc6fa 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 547dc56d7c 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards a83ed04fea 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 34a27b6253 64: onsuccess: 2: Successful build after gcc: 7 commits discards 983a15cf3f 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 4487afbfed 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 74e162cc61 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards f3c46aac55 60: onsuccess: 1: Successful build after gcc: 15 commits discards a69b9c2ecb 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 86616e9831 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards d64f97f0f2 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 7fbec5c273 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 3574db5669 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 0258e5cf05 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a2828f8846 53: onsuccess: 2: Successful build after gcc: 5 commits discards e323f54454 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards e7f2c381e7 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 09c9701ecc 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 112ea13975 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards cbd83f7782 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new b4a965286f 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new ae2a002a2b 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 1d58882cde 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new cc2c6b7512 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 4ae6559cd0 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 75fed7da3c 53: onsuccess: 2: Successful build after gcc: 5 commits new 5a505e86e4 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new b3c320dbbb 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new bcc7330e4b 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new cadf87e0ee 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 611a265c08 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new fcbc68a6e9 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new e1fe65398d 60: onsuccess: 1: Successful build after gcc: 15 commits new 63754cc99c 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new cbd36816a3 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new b8c25854eb 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 957d828ebb 64: onsuccess: 2: Successful build after gcc: 7 commits new 3e304bbdb9 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new f88dbd9cc6 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new b1daf97ea9 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 72a3a8e8f2 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new a441650377 69: onsuccess: 2: Successful build after baseline build: no [...] new d016b68f82 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 1f78d67946 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ec2af3a61b 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 5cd67e6054 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 93e70c27a4 74: onsuccess: 2: Successful build after gcc: 13 commits new 3c7cfb1653 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 4cac9035bb 76: onsuccess: 2: Successful build after binutils: 10 commits new de1394c417 77: force: 2: Successful build after gcc: 32 commits new b14c87c840 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new f449ffbbf0 79: onsuccess: 1: Successful build after gcc: 3 commits new ff3818fbe5 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new cbf6f785bd 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 8655172494 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 3faef8e62f 83: onsuccess: 2: Success after binutils/gcc: 7 commits new f4e08839a1 84: onsuccess: 2: Success after gcc: 9 commits new 2c45a8f723 85: onsuccess: 2: Success after binutils: 4 commits new 1bec249d08 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 68e0bcb775 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new b445b8c033 88: onsuccess: 1: Success after gcc: 20 commits new f566f0bcbd 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 30d4c697b9 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 48c3c647ce 91: onsuccess: #1473: 2: Success after gcc: 2 commits new d8078e5fe8 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 32b87ee68b 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 02ff7c2713 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new e99748b8c7 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 22e9d596ad 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 16731c5caa 97: onsuccess: #1481: 2: Success after gcc: 8 commits new d2a639d925 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 738c8fdac6 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 44c7ebb4d9 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 12a2532a9e 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new dd8d1c8ae1 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new d188f8299d 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 1dc1c42a77 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 7e51ff4798 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 19cdca73d7 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 2ba80a7c3c 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new fc30e01ca5 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new b5be17c291 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 2023b6c634 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 7b6369efdf 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 15df5b50a9 112: onsuccess: #1533: 2: Success after gcc: 5 commits new e48ceb93e6 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new d84d611b8a 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 3ccd8937f3 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 89aac0a04e 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new bcd2817843 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new f6d6dba286 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 97b214103a 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 340e573135 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 8714baa7d1 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new b833d10fb9 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 1020a2a88b 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 78ba38dec0 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new edd06a0e02 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 6142cf4b3d 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 7995cfd802 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new f2d3dc94e7 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new 454a591af0 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new c745d59691 130: onsuccess: #1554: 2: Success after gcc: 9 commits new 78fa02aa73 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 336945620b 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new 8de8695b3c 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new dbc84c98a5 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 303183c1d5 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new 5f4770833d 136: onsuccess: #1561: 2: Success after binutils: 3 commits new 8344e7204d 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new 3a60d3ef2a 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new bfb6fda6fb 139: onsuccess: #1566: 1: Success after gcc: 5 commits new d3038fa375 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new 0a58bf2898 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new 5819892fa9 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new 4d1f13a002 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new 8e86b771ed 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits new b3933a40e3 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits new 3b28e39842 146: onsuccess: #1573: 2: Success after binutils: 7 commits new 0b1466da42 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits new d83b4db6ef 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits new b6a90f490c 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 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 (bfe53c88b3) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 1716 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 37892 -> 38304 bytes 05-build_abe-bootstrap/console.log.xz | Bin 269900 -> 274448 bytes 06-check_regression/console.log.xz | Bin 2988 -> 2824 bytes 07-update_baseline/console.log | 62 +++++++++++++++++----------------- 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, 46 insertions(+), 46 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 (06681a897d -> abbac0802c)

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 06681a897d 52: force: #451: 2: Success after gcc: 4 commits new abbac0802c 53: force: #452: 1: Failure after basepoints/gcc-13-2887-gb0 [...] 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 1780 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 37844 -> 38444 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 277240 -> 83336 bytes 06-check_regression/console.log.xz | Bin 2648 -> 3420 bytes 06-check_regression/jira-body.txt | 2 +- 06-check_regression/mail-body.txt | 15 +- 06-check_regression/mail-subject.txt | 2 +- 06-check_regression/results.regressions | 11 + 06-check_regression/trigger-bisect | 2 + .../trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 1061 ++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 15 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- results | 13 +- 23 files changed, 1133 insertions(+), 17 deletions(-) create mode 100644 06-check_regression/results.regressions create mode 100644 06-check_regression/trigger-bisect copy 07-update_baseline/console.log => 06-check_regression/trigger-notify (100%) create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/interesting-commits] branch master updated (60a5a82 -> 4a9fcf4)

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 60a5a82 Add entry aa3e1ec495ab2fc3f22fc9240ad53a23b21fe0a1 from https [...] new 4a9fcf4 Add entry b04208895fed34171eac6bafb60c90048eb1cb0c 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: .../tcwg_gcc_bootstrap/master-aarch64-bootstrap_lto}/build_url | 2 +- .../last_good | 0 .../summary.txt | 0 .../tcwg_gcc_bootstrap/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy gcc/sha1/{953e08fde44a596e4ec2491efd15cd645e1ddc48/tcwg_gcc_bootstrap/master- [...] copy gcc/sha1/b04208895fed34171eac6bafb60c90048eb1cb0c/tcwg_gcc_bootstrap/{master- [...] copy gcc/sha1/b04208895fed34171eac6bafb60c90048eb1cb0c/tcwg_gcc_bootstrap/{master- [...] -- 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 (ff85d75117 -> 06681a897d)

by git＠git.linaro.org

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-mainline-defconfig updated (a6c5ec81fa -> 00aad069ec)

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-master-aarch64-mainline-defconfig in repository toolchain/ci/base-artifacts. from a6c5ec81fa 15: onsuccess: #488: boot: Success after binutils/gcc/linux/ [...] new 00aad069ec 16: onsuccess: #489: 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 1908 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30116 -> 30184 bytes 04-build_abe-stage1/console.log.xz | Bin 72196 -> 72040 bytes 05-build_abe-qemu/console.log.xz | Bin 31692 -> 32008 bytes 06-build_linux/console.log.xz | Bin 5236 -> 5212 bytes 07-boot_linux/console.log.xz | Bin 6248 -> 6228 bytes 08-check_regression/console.log.xz | Bin 4392 -> 4364 bytes 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 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 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_build/release-aarch64 updated (f332480a47 -> db6062da92)

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_build/release-aarch64 in repository toolchain/ci/base-artifacts. from f332480a47 20: onsuccess: #129: 6: Success after binutils/gcc/gdb: 10 commits new db6062da92 21: onsuccess: #130: 6: 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 1864 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 37832 -> 38516 bytes 05-build_abe-gcc/console.log.xz | Bin 208620 -> 209432 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8536 -> 8692 bytes 08-build_abe-glibc/console.log.xz | Bin 239580 -> 239676 bytes 09-build_abe-gdb/console.log.xz | Bin 36892 -> 37116 bytes 10-check_regression/console.log.xz | Bin 3340 -> 4300 bytes 11-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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++++++++------------------ 20 files changed, 28 insertions(+), 37 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[dejagnu] branch PR58065 updated (3554566 -> af17601)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch PR58065 in repository dejagnu. from 3554566 Add initial mockvfs support for internal unit tests new af17601 Add initial unit tests for lib/dg.exp 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: ChangeLog | 10 +++ testsuite/runtest.libs/dg.test | 166 ++++++++++++++++++++++++++++++++++++ testsuite/runtest.libs/mockutil.tcl | 18 +++- 3 files changed, 193 insertions(+), 1 deletion(-) create mode 100644 testsuite/runtest.libs/dg.test -- 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_build/master-arm updated (80815acba3 -> 23d8bda47a)

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_build/master-arm in repository toolchain/ci/base-artifacts. discards 80815acba3 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards c082faab18 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards 964d8b89de 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards f955358f55 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards be3157cf8f 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards e64f218900 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards 9d394cd639 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 4406ffe4ee 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards 49892f617b 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards 84a8cfef70 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 276f2b2b3d 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 12ea6ddea8 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 3fe7371204 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 3b8d33ab8e 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 264a060d9d 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 58e3a808c2 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards d6da03761e 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 68bc381268 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards ff1216a3d7 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards da39b1e787 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards ac50e03bb8 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 704306dbc7 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 0ab9c4d392 132: onsuccess: #1645: 7: Success after linux: 23 commits discards bb3ee28e37 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 689d4d38a1 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards a7585dbf1d 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 0314e1ad43 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards e41c249dfa 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 9dce4cd734 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 055598dd1c 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards cb5a32d14d 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards dc03947076 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 28860e8579 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards f5a9c524b0 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 1c0cf455a9 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 860d9ba816 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 369ea1f47b 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 0775f8cfba 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 0ca3fd587a 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards b75815ee22 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 1aaf05fc9b 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 46aa9b55c9 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 916d9b9108 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 55efbe3cad 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards adbc7f7413 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards ee6d802258 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards c015873e69 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 427ee4c7f1 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 35c954685d 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 08e7d5057c 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards f38e0f8cc1 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards bc5f74a46c 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards d59641cd59 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards fd9e01cbf1 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 701a863c59 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 36652ef85b 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 493a7d144b 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards f97f205f9f 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 3249b5e9b5 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 37060f2d30 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 7512e4f015 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 07e5699cc8 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards d8b304d622 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 9f893babc4 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 220e6e4c4d 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5adbc4e110 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards f0ac4d8b5e 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 60d4de58bc 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards d956174fc6 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 29e7a779ec 85: onsuccess: 7: Success after gcc: 9 commits discards bb58dd4a4c 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 73651dc241 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 0fb0bf7597 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 2747549b5b 81: onsuccess: 7: Successful build after gcc: 2 commits discards 0da51ad775 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards ed09bb3187 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 195d34fdf9 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a868337a79 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 8df26a27e3 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0a9fe88898 75: onsuccess: 7: Successful build after linux: 44 commits discards ce08152868 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards fc2bd31069 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f98025c1a1 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards c5cd771cd7 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 10536ec21c 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 1d395c748c 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 53d26d96ee 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4a31b3e1cb 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards daacf134af 66: onsuccess: 7: Successful build after gcc: 3 commits discards 16b86f7eec 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9b7964e647 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6cdf83a575 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 9953efa9ba 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 80e0f1bcc6 61: onsuccess: 4: Successful build after gcc: 15 commits discards 5a07979d84 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards d3d82a3827 59: force: 7: Successful build after gcc: 2 commits discards 8977414cb6 58: onsuccess: 7: Successful build after glibc: 2 commits discards 5f29e6db27 57: onsuccess: 7: Successful build after gcc: 7 commits discards bb4a388229 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e0e8e59e3c 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards bf2674a59a 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new f62745d207 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 466d4cb0c0 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 668369e046 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 70706f669a 57: onsuccess: 7: Successful build after gcc: 7 commits new b33764fcc5 58: onsuccess: 7: Successful build after glibc: 2 commits new bcbc5d6a04 59: force: 7: Successful build after gcc: 2 commits new e520de46b7 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 2836b3a8c0 61: onsuccess: 4: Successful build after gcc: 15 commits new 95cac1939e 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 7f036f88d2 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new c4e540196f 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 34f33fc47b 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new dffad8d835 66: onsuccess: 7: Successful build after gcc: 3 commits new 86ff3cedc7 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new c779c7ddff 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ebce4357a7 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 20ef014f0c 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 2a6996bc68 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 895a864236 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 09d07747fa 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c9a0bc82da 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 43951710c0 75: onsuccess: 7: Successful build after linux: 44 commits new 35ddd4cab8 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ddf9b717da 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 47c4bca3e9 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c3ed4d84dc 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 44afb099e3 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new db1afba845 81: onsuccess: 7: Successful build after gcc: 2 commits new 216180d1f1 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 1d226837a1 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 7cefcb6d25 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 1836d29fd4 85: onsuccess: 7: Success after gcc: 9 commits new 7c8475ae3b 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new c7b909c75f 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 275b27477c 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 9987b8feca 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 97a25ec627 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a01fe051a5 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new dafa7a9425 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new fd75cbae91 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 65ac1cc468 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new a0af6f81ff 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 2d3ecc880c 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new a41093a4d5 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 7cbad3a220 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new d3eca9139e 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 9cc3b6bc7c 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 6814a23fdc 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 1bc1bf9843 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 4a8007bb0b 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new aa2dd8ec7b 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new b40e480710 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new dcfdc168b9 106: onsuccess: #1617: 7: Success after gcc: 2 commits new aa3442d744 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 1d0cd3007a 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new c230b95375 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 718085d095 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 097c4f1317 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new d55cd39f4b 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 11cc3a610b 113: onsuccess: #1624: 7: Success after gcc: 6 commits new bfa01e9bc9 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new e35ee75fff 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 0049d2a33c 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 1320ab0620 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 75e9d2fc31 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 5d03fb33ff 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new ab5087987f 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 50596ef698 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new b855116e85 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new ce019bd461 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 5733655264 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 959b1637bd 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new f3c7aef0a2 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new e6955536bc 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new d08ec090ac 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new dd8c58515a 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new f1c8920699 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new b2000ab569 131: onsuccess: #1644: 7: Success after gcc: 10 commits new f23ee1faef 132: onsuccess: #1645: 7: Success after linux: 23 commits new 18a927c389 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new d52d8ae693 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 8d0efa7cc1 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 7f5873013e 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 8497b1247e 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new 555a25c1fc 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 2749749f2a 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 92569c0e4e 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 98dc547eec 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 40f79e1b8d 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 814ef567c2 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new dc8a5a8722 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 7ca50aaa2d 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new be88b35496 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 9d639ed0a4 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new 62a32d93a6 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 504d146467 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new d64e6eefdd 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new 4564ada396 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new 51e2ab23a7 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new 196a695d0c 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new bd1dfe9057 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new 23d8bda47a 155: onsuccess: #1670: 7: 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 (80815acba3) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1700 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 30148 -> 29664 bytes 05-build_abe-stage1/console.log.xz | Bin 91136 -> 90672 bytes 07-build_abe-linux/console.log.xz | Bin 8656 -> 8576 bytes 08-build_abe-glibc/console.log.xz | Bin 233736 -> 234356 bytes 09-build_abe-stage2/console.log.xz | Bin 224288 -> 223824 bytes 10-build_abe-gdb/console.log.xz | Bin 37476 -> 37240 bytes 11-build_abe-qemu/console.log.xz | Bin 31376 -> 31340 bytes 12-check_regression/console.log.xz | Bin 4488 -> 4316 bytes 13-update_baseline/console.log | 42 +++++++++++++++++------------------ 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 ++++++++++++++++----------------- 21 files changed, 50 insertions(+), 50 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_build/master-aarch64 updated (e19dc3d295 -> ee68299923)

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_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards e19dc3d295 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards b4a9416e62 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 76123cfe37 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 5c28a506e6 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards aad7879eb3 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards 9c3f5c6c46 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards 9ff41cbf60 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 6b914a2ac4 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards c0491206dc 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards dbfd26ee42 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 504d71d5df 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 46f0eba61d 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 4115fadad1 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards e04a6fe2a0 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards c4ecc7d5a3 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 729a91c88b 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 6ec201adbb 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 78f8fcaa9a 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 2a15581337 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards fb5865ce69 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 875a917acb 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards f4175f2140 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards 93623b2000 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 9eb5dd02b9 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 31eda81b71 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 6cf0b5a4aa 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 750c588471 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards eb77b36443 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 42b6482aa3 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards aa8c73a2ab 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 6f275adfd2 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards f1f3493ee2 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards b935c1eb89 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 90e8cebb1b 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 66ee97dee1 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 4d0a802fe0 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 4eaa9f63c4 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 7a1434469a 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 4f25974fc3 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 34abed9c36 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 4a29ea1fe5 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards abd2fe3b78 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 4338f78beb 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards c220db1c74 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 087c145baf 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 6626fd9ab5 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards fe1872db29 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards e10ad07e67 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 6eb14d96f2 102: force: #1551: 1: Failure after gcc: 306 commits discards a7b484a5e3 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 2ed851d00b 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards cfa4ed2f1e 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 9d53b1f4c5 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 58f75eaf48 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 9b9c8c488f 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 47215ee23c 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 175392d033 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 66a66dd7b1 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 55c7430a45 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards e1527ec993 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 10faab4f4e 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 1188a5032f 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 25c9b14dd5 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards f0463e5422 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 316bde4182 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 72050842db 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 5288c73379 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 86abc121ca 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards da58c21c6a 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 4db26b6cac 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 759e63b4f4 80: onsuccess: 7: Successful build after linux: 44 commits discards 8f28027165 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 6f4cd10498 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards ebb7d1d870 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8be3a73027 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 69d1fbeaeb 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards e5cf0f6be3 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 597d6e267f 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cca67bfb27 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b0fe21063d 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 52273cdc86 70: onsuccess: 7: Successful build after gcc: 4 commits discards a85864339f 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 891348c50a 68: onsuccess: 7: Successful build after linux: 6 commits discards 56310234dc 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards a35f01138e 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 2138e19228 65: onsuccess: 7: Successful build after binutils: 3 commits discards f3cef8d6ab 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 1fc5772a04 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 37abe245d4 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 6492a3a9b9 61: onsuccess: 4: Successful build after gcc: 5 commits discards 5a32f5167e 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards d3b0621f15 59: force: 7: Successful build after gcc: 3 commits discards 7aa5a5cf2d 58: onsuccess: 7: Successful build after glibc: 2 commits discards 17c279db1e 57: onsuccess: 7: Successful build after gcc: 7 commits discards 2278b88f0f 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e3bc225115 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 824ce943c3 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards b21ae178c0 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards a79b17200a 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards 123b90c766 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 39bba0e279 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ef7bee3575 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 226302a3bf 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 9ec1c43462 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new 0e7c8b5f5b 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 90fdb66513 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 98a20171fd 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c5d3576f53 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 55a246c6e7 57: onsuccess: 7: Successful build after gcc: 7 commits new 5f40222e1e 58: onsuccess: 7: Successful build after glibc: 2 commits new 88db660b26 59: force: 7: Successful build after gcc: 3 commits new a57cb323d0 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 83f10cdfb0 61: onsuccess: 4: Successful build after gcc: 5 commits new b828b3452d 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 0b78cd01eb 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new a1abc5f1e5 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 27686d6861 65: onsuccess: 7: Successful build after binutils: 3 commits new 9fbf25df55 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 1fe834cd6b 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new d55010b20a 68: onsuccess: 7: Successful build after linux: 6 commits new 5ce5d5a068 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 58de55f17a 70: onsuccess: 7: Successful build after gcc: 4 commits new 76701ca976 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new a149c01a47 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new bd67ad851e 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6a0955eb8c 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new f74a2b6ef8 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new e28e6d3109 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 7b759549e3 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5638125268 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 7b19e7100c 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new d33cf4142f 80: onsuccess: 7: Successful build after linux: 44 commits new c2caad1508 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 55a30c519c 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 145d5508d0 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d7254bb482 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 7b30354374 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new bc6195a315 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 232058de5a 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 1f6b059bbe 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new e2869a20ae 89: onsuccess: 7: Success after gcc/glibc: 8 commits new b24e5cc3b5 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new ba3bcd10b7 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new b9d83ed9f0 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 2615b2c521 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 30897d3979 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 8cca2314e3 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new d3fa9867f8 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a4184703ef 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new ef6ecaf861 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 330ceda1fd 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 6ed84ffc2a 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 8d0fa414ca 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 02230fdd00 102: force: #1551: 1: Failure after gcc: 306 commits new 6aa5d3bebf 103: onsuccess: #1552: 1: Success after gcc: 5 commits new e65f9f8ff1 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new af7331b397 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 75f4a6566b 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 2e1b3d21f2 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new b07f0518d7 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 64927a7fca 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 9df72ebac7 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 8cad3c3879 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 42dfeddcce 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 8213365e01 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new ba88e8714e 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 8dd3f38022 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new c90af8913e 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 9db61768b4 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 5fd789224c 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new d732be2b5f 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 84a06927bd 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 583b0c649c 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 9698537d32 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 6288e2cce9 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 3d4ce51975 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 9abd141a06 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new ae644e93f6 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new dba3e196c0 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new b2271cbace 128: onsuccess: #1579: 7: Success after linux: 12 commits new 54410d9cb6 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new dffb6f758d 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 88665a430d 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 979ab643bf 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 5017c91b22 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new d2f21714ab 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new ba0ee51b89 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new b95956b86e 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new beb610b2e4 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 5fbffd9dbe 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new d91cc228e5 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 849f5388bc 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 7009a7a28b 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 9aa86bae33 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new a7b005c9b0 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 0154ea4689 144: onsuccess: #1595: 7: Success after glibc: 2 commits new d77060e6c4 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new a5ad82a442 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 8909ac7b91 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 41a39edda3 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new e28184ae51 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new 692a41d4ab 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new ee68299923 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] 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 (e19dc3d295) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1672 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2708 bytes 04-build_abe-binutils/console.log.xz | Bin 30388 -> 30176 bytes 05-build_abe-stage1/console.log.xz | Bin 72780 -> 72928 bytes 07-build_abe-linux/console.log.xz | Bin 8656 -> 8780 bytes 08-build_abe-glibc/console.log.xz | Bin 239916 -> 239704 bytes 09-build_abe-stage2/console.log.xz | Bin 203196 -> 203112 bytes 10-build_abe-gdb/console.log.xz | Bin 37712 -> 37692 bytes 11-build_abe-qemu/console.log.xz | Bin 32012 -> 32092 bytes 12-check_regression/console.log.xz | Bin 4492 -> 2964 bytes 13-update_baseline/console.log | 62 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 29 +++++++--------- 17 files changed, 48 insertions(+), 53 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