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-arm-bootstrap_profiled_lto_lean updated (9ceedffb5b -> 33b9a1058c)

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-arm-bootstrap_profiled_lto_lean in repository toolchain/ci/base-artifacts. from 9ceedffb5b 48: force: #428: 1: Failure after basepoints/gcc-13-2871-g1b [...] new 33b9a1058c 49: onsuccess: #429: 1: Success after gcc: 13 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 1680 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 51068 -> 51168 bytes .../console.log.xz | Bin 107408 -> 108624 bytes 06-check_regression/console.log.xz | Bin 3284 -> 2696 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 | 9 - 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 | 210 --------------------- 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 | 9 - 23 files changed, 33 insertions(+), 272 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-arm-bootstrap_profiled_lto_lean updated (87d08e0396 -> 9ceedffb5b)

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-arm-bootstrap_profiled_lto_lean in repository toolchain/ci/base-artifacts. from 87d08e0396 47: force: #427: 2: Success after gcc: 29 commits new 9ceedffb5b 48: force: #428: 1: Failure after basepoints/gcc-13-2871-g1b [...] 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 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 51008 -> 51068 bytes .../console.log.xz | Bin 944148 -> 107408 bytes 06-check_regression/console.log.xz | Bin 2804 -> 3284 bytes 06-check_regression/jira-body.txt | 2 +- 06-check_regression/mail-body.txt | 13 +- 06-check_regression/mail-subject.txt | 2 +- 06-check_regression/results.regressions | 9 + 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 | 210 +++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 13 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 11 +- 23 files changed, 275 insertions(+), 18 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 (734bea1 -> 72efba6)

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 734bea1 Add entry b04208895fed34171eac6bafb60c90048eb1cb0c from https [...] new 72efba6 Add entry 1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4 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: .../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/1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4/tcwg_gcc_bootstrap/{master- [...] copy gcc/sha1/1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4/tcwg_gcc_bootstrap/{master- [...] copy gcc/sha1/1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4/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-arm-bootstrap_profiled_lto_lean updated (5e39c4412d -> 87d08e0396)

by git＠git.linaro.org

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (ee7b66d021 -> a1e72573bc)

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 ee7b66d021 150: onsuccess: #1577: 2: Success after gcc: 3 commits discards 96f9c188f8 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits discards 32e6b657bc 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits discards b4a9d7d73d 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits discards 6d29c8f282 146: onsuccess: #1573: 2: Success after binutils: 7 commits discards e2a8e7662c 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits discards 4ea8dfe22d 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits discards 94cb635dcb 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards 80a3cdb044 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards 31e50d1a2b 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards c2f8ca5c1a 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards 0743fa020e 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards ce64493a65 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards ebd361714a 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards fd149a3a40 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards e1791e8333 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards 0289124de4 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards 84e41f5f4a 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 84c2b1fdd0 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards ba24f20a0c 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards eeeef968ca 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards a2c60d6c5d 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards 78edd610f5 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards b80125c53e 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards 277ac9da8b 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards a73a391a8b 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 4d75bf9fa7 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 0e55212faf 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards b792ef0bc5 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 9d3dc26928 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards d4329e63a9 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards ce0f7cc3b1 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards a44d7d8a77 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 10d7c10645 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards e9d65ab56c 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 3449903c77 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 27c9bdc28e 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 94a86a4f2d 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 0f6c0b9ca3 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 5737bfcfc2 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards b72bef24ff 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 7f78e02fb2 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 4eb547021b 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 34379e9698 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards e6755db199 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 05e26092a1 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards cf162303a3 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 964e9f8925 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards f1cfc6ba11 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards baef9e0521 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 11476046a0 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 5a9c1208f0 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 1f75bf8ed9 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 54804229b9 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 2208158987 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 62751df599 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 0639eace09 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 57198f2c59 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 6b1fd6ce19 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 8d3eff201d 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 792a7a5bdd 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 5355cf6daf 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 465b3e8e31 88: onsuccess: 1: Success after gcc: 20 commits discards a2fac8668a 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 16256ceae2 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards c56becdde4 85: onsuccess: 2: Success after binutils: 4 commits discards 149248a158 84: onsuccess: 2: Success after gcc: 9 commits discards a4c49ae8d3 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 54e20ab4b3 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 71a612a71f 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 05669a632a 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 18e7321282 79: onsuccess: 1: Successful build after gcc: 3 commits discards e9797a7c6f 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 26fb8a6d79 77: force: 2: Successful build after gcc: 32 commits discards 84c8576e7f 76: onsuccess: 2: Successful build after binutils: 10 commits discards f7781f4deb 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards d0d7930e3a 74: onsuccess: 2: Successful build after gcc: 13 commits discards ce1bd66462 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 1c54fb73ec 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 6aca6bb332 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 772729ddf6 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 1b9a0e68a5 69: onsuccess: 2: Successful build after baseline build: no [...] discards 37865c0590 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 705cb1c887 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 6b5a352522 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 6e576540e1 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards d17761fdb0 64: onsuccess: 2: Successful build after gcc: 7 commits discards ce51c007b3 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 6dca9da0ed 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 55d17ae059 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards f02607d5c2 60: onsuccess: 1: Successful build after gcc: 15 commits discards cc0bc0ad2a 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards a4415d2ce0 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 6355bb7d85 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards db1bff7504 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards eb875ba1f4 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a5bb581b58 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 91c0a6c3fb 53: onsuccess: 2: Successful build after gcc: 5 commits discards 988975894d 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards b8490b8adc 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 6030583097 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 5dcbeb15d2 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new bf7f6a4078 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 258f364da4 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 568955a8f8 53: onsuccess: 2: Successful build after gcc: 5 commits new 5a6fe7aa00 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 9fcb5c50c5 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 37441dcbf7 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 458e9d01df 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 5fd0efab6c 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 24d5162624 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 5a7065f7c2 60: onsuccess: 1: Successful build after gcc: 15 commits new db0b41b9fb 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new eedeab0191 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 47fc2ae29f 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 29da6e2c7b 64: onsuccess: 2: Successful build after gcc: 7 commits new 29bc2db2b8 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new dde92f4093 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 55cfd776ff 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new a01b9878ee 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 9f1963a59b 69: onsuccess: 2: Successful build after baseline build: no [...] new 6a0c04125d 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new e074cde162 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 25171fe0c4 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 03978191f0 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 361e3513fe 74: onsuccess: 2: Successful build after gcc: 13 commits new 085fa7770c 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 70e6ca2c7d 76: onsuccess: 2: Successful build after binutils: 10 commits new 71daf6a68e 77: force: 2: Successful build after gcc: 32 commits new 1ae55b92d2 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new bfb1c2d88e 79: onsuccess: 1: Successful build after gcc: 3 commits new 9a46016725 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new d857d5a970 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 7dd5207365 82: onsuccess: 2: Success after binutils/gcc: 26 commits new b1021a374c 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 2be6bc8b05 84: onsuccess: 2: Success after gcc: 9 commits new f060576f5c 85: onsuccess: 2: Success after binutils: 4 commits new d6852839dd 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 0f65a0c5f7 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new e4798dfa7a 88: onsuccess: 1: Success after gcc: 20 commits new 660b26f0f7 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 5d0ce913fe 90: onsuccess: #1472: 2: Success after gcc: 2 commits new a31a63307d 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 77c8345273 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new a8576e9fcb 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 1da3cb0e7b 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new 7800bd0ea6 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new da138b1c6a 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 467765cb6d 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 6fa8d9c8b3 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new d8093cab93 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new bb8ebdd697 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new a63e9a22e6 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 8b3a05a289 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 033c20a89d 103: onsuccess: #1524: 2: Success after gcc: 2 commits new b4d0eafde8 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 3e2ba7ceef 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 442bb3933f 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 668026cfd2 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new c2c48d723c 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 8eeab5251f 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new c092c20d68 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new c291e87033 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new d32d2b606b 112: onsuccess: #1533: 2: Success after gcc: 5 commits new a260fa03bc 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 6b3779c7d4 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 253bffb79f 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 7c2039926a 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 2e31d97564 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new 06ef455a0c 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new a36e3d62d9 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 53df66618e 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 4e56e02401 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 41a431ca38 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new cef6935280 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 5289bcc881 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new ca801d9ef6 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 5e6269ea5d 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 0ff466561b 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new 03b77b16af 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new 6861fcb913 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new d41ba945e9 130: onsuccess: #1554: 2: Success after gcc: 9 commits new b30ebf0be2 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 98141d0f92 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new e8126dfd71 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 6617807ae1 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 193bec6f3d 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new d97cadd6c1 136: onsuccess: #1561: 2: Success after binutils: 3 commits new 5a6c398f0a 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new d26404a36e 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new 8620bb10ce 139: onsuccess: #1566: 1: Success after gcc: 5 commits new 8a68b772fb 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new 68ec4f2419 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new 4c8a5b47e8 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new 1be71f1064 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new 1763c420ef 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits new f12c9516ee 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits new 2a7b355e5a 146: onsuccess: #1573: 2: Success after binutils: 7 commits new cd9fdec514 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits new 1a882c2da9 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits new 7dec13eeac 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits new a7085f579a 150: onsuccess: #1577: 2: Success after gcc: 3 commits new a1e72573bc 151: onsuccess: #1578: 2: Success after gcc: 2 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 (ee7b66d021) \ 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 1672 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2708 bytes 04-build_abe-binutils/console.log.xz | Bin 38324 -> 37588 bytes 05-build_abe-bootstrap/console.log.xz | Bin 271232 -> 270556 bytes 06-check_regression/console.log.xz | Bin 2572 -> 2528 bytes 07-update_baseline/console.log | 64 +++++++++++++++++----------------- 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 ++++---- 12 files changed, 44 insertions(+), 44 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-master-aarch64-stable-allmodconfig updated (3ac8b1ef0e -> cebe1a2c9a)

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-master-aarch64-stable-allmodconfig in repository toolchain/ci/base-artifacts. from 3ac8b1ef0e 19: onsuccess: #506: 36: Success after llvm: 19 commits new cebe1a2c9a 20: onsuccess: #507: boot: Success after binutils/llvm/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 1700 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30184 -> 30160 bytes 04-build_kernel_llvm/console.log.xz | Bin 63508 -> 63956 bytes 05-build_abe-qemu/console.log.xz | Bin 30576 -> 31592 bytes 06-build_linux/console.log.xz | Bin 3764 -> 3368 bytes 07-boot_linux/console.log.xz | Bin 0 -> 508 bytes 08-check_regression/console.log.xz | Bin 3120 -> 4596 bytes 08-check_regression/mail-body.txt | 13 +++++-------- 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 | 15 ++++++--------- mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- results | 6 +++++- 19 files changed, 40 insertions(+), 39 deletions(-) create mode 100644 07-boot_linux/console.log.xz -- 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-stable-allyesconfig updated (e3028dd695 -> 6966cab867)

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-stable-allyesconfig in repository toolchain/ci/base-artifacts. from e3028dd695 10: onsuccess: #364: all: Success after binutils/gcc/linux/q [...] new 6966cab867 11: onsuccess: #365: all: Success after binutils/gcc/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30132 -> 30228 bytes 04-build_abe-stage1/console.log.xz | Bin 68192 -> 68420 bytes 05-build_abe-qemu/console.log.xz | Bin 31196 -> 31872 bytes 06-build_linux/console.log.xz | Bin 3308 -> 3292 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 4136 -> 4232 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_cross_check_gcc/master-arm updated (ff621dbcb5 -> a882f4e730)

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-arm in repository toolchain/ci/base-artifacts. discards ff621dbcb5 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 1d951e2f2b 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards b16227dd10 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards a6fc1ce02f 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 8c86bef3f5 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards b116803e8f 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 4a1f0daa06 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards b0c205f361 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 2370dabc5e 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards f502d4b80f 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 83fa9c15ba 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 0f77eb2d08 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards b61fdb3f75 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 57fbed27c3 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 6781fbda9e 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards feffe4ff61 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards effd140662 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 7f05b6169d 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards d9ff36d65e 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards b34e037cf2 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards d4b6c07010 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 8fc0a90ff0 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 6789dc87b5 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards d2f395d18d 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 6988545518 128: onsuccess: #1723: 1: Success after linux: 12 commits discards de42f3f702 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards a7f854a471 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 44e7a26ba7 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards df0907cf82 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 55037aaa95 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards ee5cb5f870 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 13ce89ec29 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 3a2992c529 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards fe49b21234 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 3a93a2a3f0 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 135ef10d37 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards bcf87233c2 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards c7c0451111 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 4ee84a9b94 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards ef382abf50 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 2c5cda828f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 356277c100 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 3ebe1593d7 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 7e97687fb8 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards cb4dc7ea42 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 2ecba69575 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 6884d2ae4c 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 15ea730c70 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards bc75d391f6 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 8cf311e582 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 39b82befcd 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 9ae613b91d 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 4244d31dd2 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 87c62c8f8e 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 03d7a7f7e6 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards f4efd47fa9 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 599745eb24 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards ab9645916e 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards e474484e94 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 88ccc41a41 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 861572f7c4 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 9eee0cb5eb 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 9d52fdba53 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 37d1a1ae5f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 576b82762b 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 47515cd280 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards e2461ac2cf 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards b073c139a2 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 6187bab771 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards f3eb8dc38b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 991676dc99 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 3f69ca9ce0 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 787a2c277f 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards f3b145f502 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 39228cefdd 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards add019f0ff 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 698245907e 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards f7aa18647d 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5d49feac1f 74: onsuccess: 1: Successful build after linux: 44 commits discards bb09e1d495 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 155e968124 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0e12ff442e 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 0d8ab57085 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards a0d9f01b1b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards db6032f131 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 12eabb1d94 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4ab06fdddc 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b47ec9fca8 65: onsuccess: 1: Successful build after gcc: 4 commits discards 2db3a1a7f3 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1c788be814 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e9265d5f66 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards b2ea7b0380 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 2d63cc63d6 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 65af3c3fea 59: onsuccess: 1: Successful build after glibc: 2 commits discards 6e177482ef 58: onsuccess: 1: Successful build after binutils: 2 commits discards 339e4e945e 57: onsuccess: 1: Successful build after gcc: 7 commits discards 5d8748cb2d 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 03eb593d1a 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 39172c2e80 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 0688911fb7 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 06420c7c7c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new e8551f24e9 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 8ba4b2067a 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new eb8e007954 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 9d5b309c6d 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5c6f11b0c2 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a355157ce4 57: onsuccess: 1: Successful build after gcc: 7 commits new 57d05c5b00 58: onsuccess: 1: Successful build after binutils: 2 commits new 39dba10390 59: onsuccess: 1: Successful build after glibc: 2 commits new 8984294400 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new bbcb2ad845 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e9c2019cf3 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new d57abef12b 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7f682b3b4c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 45dcfc6a49 65: onsuccess: 1: Successful build after gcc: 4 commits new a242ea9424 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c0ffa6796b 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 51156f628e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 30d11270a7 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 46d80d9643 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new dd5af60c44 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new de43a37264 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9627f29912 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new a1a47f8568 74: onsuccess: 1: Successful build after linux: 44 commits new b96f696f82 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2fb8c62346 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 7d66e1c4d9 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fa8c8ae89f 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 77b85d12d0 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c3a01f6120 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 23e897cf8b 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new d62c49152e 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 6e936d87cd 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new b3d6bb1a3d 84: onsuccess: 1: Success after gcc/glibc: 9 commits new d4daa9a413 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 698cd6dde8 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new e08367dd1a 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 25d3bffd77 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 644d99e5cf 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 54a74a99d0 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 8fa2fe3666 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new b6f1b90a08 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 13dadffb3d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new ddde8d07d5 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new a56fe2dfd8 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 88683acb7d 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new fae1611214 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new f106b3cd1d 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 6c9117c315 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new f698ec0705 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 8e6e936e42 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 14da978944 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 6dbb07463d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 886c27a001 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 0b919f121c 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new d6f4f738d1 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 238d385e60 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new ee67e17f28 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new a2d0a8b2f5 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 037e6acccb 110: onsuccess: #1703: 1: Success after gcc: 6 commits new abdaea57f8 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 19dab87b43 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 8ecda5ecfa 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new da6660e8a1 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new ecef0c6c2c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 02bd0b232e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 1678eb05fd 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 5414124dc7 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new f339e3633c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new b7653d7340 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 6de80566d0 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 7f98c1bfa7 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 8fce5a14c7 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 4c78fc981d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new ca65df3b26 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new a51d539072 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 4bbb3f79a1 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new ba372532b3 128: onsuccess: #1723: 1: Success after linux: 12 commits new 02633937aa 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new a36c47fb82 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 2549c671f5 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 4db58376ea 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 75b55f826f 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 4708f044b9 134: onsuccess: #1730: 1: Success after binutils: 2 commits new f4cbabb336 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 7ebf9d5804 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 111319437a 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 0c27b588d9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 93ee7abe0f 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new b9a391e3a7 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new c439c4a94c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new fce064f1db 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 6633c37870 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 889681194d 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 54efb27810 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new eb2b668a42 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 41139d194c 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new f6d7e2e8a2 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new e034c5f96b 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 48d55df16a 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new fc5fc48993 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 58774adb1f 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new a882f4e730 153: onsuccess: #1754: 1: Success after gcc: 2 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 (ff621dbcb5) \ 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 1920 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29916 -> 29860 bytes 04-build_abe-stage1/console.log.xz | Bin 90860 -> 90276 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8612 -> 8572 bytes 07-build_abe-glibc/console.log.xz | Bin 234432 -> 233840 bytes 08-build_abe-stage2/console.log.xz | Bin 224160 -> 224272 bytes 09-build_abe-gdb/console.log.xz | Bin 37192 -> 36944 bytes 10-build_abe-qemu/console.log.xz | Bin 31368 -> 31776 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2820 -> 2816 bytes 13-check_regression/console.log.xz | Bin 6464 -> 5392 bytes 13-check_regression/mail-body.txt | 40 - 13-check_regression/results.compare | 37 +- 13-check_regression/results.compare2 | 48 +- 14-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 42 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- sumfiles/g++.log.xz | Bin 2691360 -> 2668044 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 2202388 -> 2231760 bytes sumfiles/gcc.sum | 2166 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 881524 -> 890340 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201600 -> 201416 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422168 -> 432600 bytes sumfiles/libstdc++.sum | 10 +- 37 files changed, 1259 insertions(+), 1344 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-lts-defconfig updated (0f71275924 -> c898cad8d5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-lts-defconfig in repository toolchain/ci/base-artifacts. from 0f71275924 12: onsuccess: #414: boot: Success after binutils/gcc/linux/ [...] new c898cad8d5 13: onsuccess: #415: 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 1680 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 29884 -> 30020 bytes 04-build_abe-stage1/console.log.xz | Bin 86288 -> 87232 bytes 05-build_abe-qemu/console.log.xz | Bin 31048 -> 31596 bytes 06-build_linux/console.log.xz | Bin 3308 -> 3320 bytes 07-boot_linux/console.log.xz | Bin 5796 -> 5820 bytes 08-check_regression/console.log.xz | Bin 4148 -> 4252 bytes 09-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 33 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-norov-allnoconfig updated (07bc11c29d -> b434fd181e)

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-master-arm-norov-allnoconfig in repository toolchain/ci/base-artifacts. from 07bc11c29d 12: onsuccess: #49: all: Success after binutils/llvm/linux/q [...] new b434fd181e 13: onsuccess: #50: all: Success after binutils/llvm/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1704 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 29828 -> 30060 bytes 04-build_kernel_llvm/console.log.xz | Bin 63224 -> 65076 bytes 05-build_abe-qemu/console.log.xz | Bin 31040 -> 31896 bytes 06-build_linux/console.log.xz | Bin 522196 -> 3496 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4292 -> 4604 bytes 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 | 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022