Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ecosystem (crater) testing for core crates #402

Open
ryankurte opened this issue Dec 3, 2019 · 4 comments
Open

Ecosystem (crater) testing for core crates #402

ryankurte opened this issue Dec 3, 2019 · 4 comments
Labels
triage-2024-keep Issues triaged in 2024 and considered OK to keep open

Comments

@ryankurte
Copy link
Contributor

given we have a set of foundational crates depended on by practically the whole ecosystem (like https://github.com/rust-embedded/embedded-hal/), the risk of changes to these foundational crates causing large volumes of annoyance is pretty high.

it'd be awesome to have https://github.com/rust-lang/crater (or something like it) running over consumers of these crates so we can be informed of and mitigate the impacts of any necessary breakage.

possibly related to: #381

cc. @therealprof

@jamesmunns
Copy link
Member

CC @pietroalbini

@pietroalbini
Copy link

Would you like just cross-compilation or also running tests?

@ryankurte
Copy link
Contributor Author

i think just cross compilation (including the test suite), afaik the issues we're looking to avoid are all around types and interfaces so should be p much (where things can compile for a given target) target independent, and shouldn't require test running.

@pietroalbini
Copy link

That should be possible, but I'm not sure how it's best to integrate it with Crater off the top of my head.

@BartMassey BartMassey added the triage-2024-keep Issues triaged in 2024 and considered OK to keep open label Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage-2024-keep Issues triaged in 2024 and considered OK to keep open
Projects
None yet
Development

No branches or pull requests

4 participants