CI Failure #306
Labels
Comments
|
This failure was deliberate and tests that the scheduled CI job worked and can report failures. |
bors bot
added a commit
that referenced
this issue
Dec 9, 2020
307: Finish setting up scheduled CI job r=jonas-schievink a=adamgreig The scheduled CI seems to have worked (#306), so this PR removes the forced failure and sets the time to a hopefully sensible saturday morning, though I suppose it doesn't really matter that much what time of week it is. Co-authored-by: Adam Greig <[email protected]>
adamgreig
pushed a commit
that referenced
this issue
Jan 12, 2022
306: fix #74 r=jonas-schievink a=spookyvision special-cased linker section names to satisfy macos linker constraints Co-authored-by: Anatol Ulrich <[email protected]>
adamgreig
added a commit
that referenced
this issue
Jan 12, 2022
310: Only emit link_section for cortex-m r=jonas-schievink a=adamgreig Previously we always emitted `link_section`, even though it only had an effect when our linker script was being used (and only made sense on cortex-m targets). This breaks building the code for a MacOS target, which is occasionally useful for running `cargo check` etc. In the macros crate we don't have the target information available, so instead we continue to emit `link_section` except specifically on MacOS. This keeps the fix from #306 but hopefully resolves the confusion in rust-embedded/cortex-m-rt#74 (comment). Co-authored-by: Adam Greig <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Scheduled CI run failed. Details:
https://github.com/rust-embedded/cortex-m/actions/runs/409279614
The text was updated successfully, but these errors were encountered: