Closed ankeXiao closed 1 week ago
The following west manifest projects have been modified in this Pull Request:
Name | Old Revision | New Revision | Diff |
---|
Note: This message is automatically posted and updated by the Manifest GitHub Action.
@ankeXiao , there are several build failure
CASE_NAME | ZEPHYR_VERSION | RESULT | PLATFORM | TEST_PATH -- | -- | -- | -- | -- mgmt.mcumgr.fs.mgmt.hash.supported.crc32 | v3.6.0-3542-g8c0bff829db0 | Build failure | frdm_ke17z | tests/subsys/mgmt/mcumgr/fs_mgmt_hash_supported mgmt.mcumgr.fs.mgmt.hash.supported.sha256 | v3.6.0-3542-g8c0bff829db0 | Build failure | frdm_ke17z | tests/subsys/mgmt/mcumgr/fs_mgmt_hash_supported mgmt.mcumgr.fs.mgmt.hash.supported.all | v3.6.0-3542-g8c0bff829db0 | Build failure | frdm_ke17z | tests/subsys/mgmt/mcumgr/fs_mgmt_hash_supported sample.drivers.flash.shell | v3.6.0-3542-g8c0bff829db0 | Build failure | frdm_ke17z | samples/drivers/flash_shell`
now build and board testing are clean.
The soc module files depends on this PR "pull/71670" and is shared with KE15Z platform, so will be updated after it is reviewed and merged.
Please address the compliance error
Hi all, there is a compilation failure in the "build-docs" under the "Documentation Build(HTML)" step, I have no idea which file caused it, please help to check. Thanks!
There was a site-wide CI failure going on. Appears to have been addressed.
Hi @ankeXiao! Congratulations on getting your very first Zephyr pull request merged 🎉🥳. This is a fantastic achievement, and we're thrilled to have you as part of our community!
To celebrate this milestone and showcase your contribution, we'd love to award you the Zephyr Technical Contributor badge. If you're interested, please claim your badge by filling out this form: Claim Your Zephyr Badge.
Thank you for your valuable input, and we look forward to seeing more of your contributions in the future! 🪁
Hello @ankeXiao, and thank you very much for your first pull request to the Zephyr project! Our Continuous Integration pipeline will execute a series of checks on your Pull Request commit messages and code, and you are expected to address any failures by updating the PR. Please take a look at our commit message guidelines to find out how to format your commit messages, and at our contribution workflow to understand how to update your Pull Request. If you haven't already, please make sure to review the project's Contributor Expectations and update (by amending and force-pushing the commits) your pull request if necessary. If you are stuck or need help please join us on Discord and ask your question there. Additionally, you can escalate the review when applicable. 😊