fix(example): portable chip path so the nightly H5 gate runs in CI#87
Merged
Conversation
system.yaml referenced the H5 chip config by an absolute path into a local
labwired checkout, so the nightly failed in CI ('No such file'). Reference it
relatively as stm32h563.yaml (gitignored); the nightly copies it from the
cloned labwired-core, and the README documents the same one-line copy for local
runs. Gate re-verified 27/27 with the relative path.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #86. The node system.yaml referenced the H5 chip config via an absolute path into a local labwired checkout, so the nightly failed in clean CI. Now referenced relatively (gitignored); the nightly copies it from the cloned labwired-core. Gate re-verified 27/27 with the relative path.