-
Notifications
You must be signed in to change notification settings - Fork 151
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
Improve ci #221
Improve ci #221
Conversation
Also added `--list` to show what test cases would have been run using the current filters
Also implements an alternate way to choose toolchain
Hey @Emilgardis, ACKing this as seen, looks good overall, will have more time tomorrow (2018-05-21) to look at this. I'd add one open issue: IMO It probably makes more sense to move all the test cases to one or more json/toml/yaml files rather than keeping it in code. |
use std::io::prelude::*; | ||
use std::path::PathBuf; | ||
use std::process::{Command, Output}; | ||
use tests::TestCase; | ||
|
||
static CRATES_ALL: &[&str] = &["bare-metal = \"0.1.0\"", "vcell = \"0.1.0\""]; | ||
static CRATES_ALL: &[&str] = &["bare-metal = \"0.2.0\"", "vcell = \"0.1.0\""]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Emilgardis is this info stored anywhere in svd2rust
that we could use to prevent dual maintenance here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only place where this can be fetched from is the docs. We could also make svd2rust output $PWD/Cargo.toml
needed via a flag
Overall LGTM, if we can dedupe the dependent crates somehow, that would be nice, also feel free to open up one or more follow-up issues for the |
svd_url: None, | ||
should_pass: false, | ||
run_when: Never, | ||
svd_url: Some("https://raw.githubusercontent.com/wez/atsamd21-rs/master/svd/ATSAMD21G18A.svd"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be a specific commit
bors try |
🔒 Permission denied Existing reviewers: click here to make mathk a reviewer |
bors try |
tryMerge conflict |
Ping from triage: @Emilgardis can you rebase/merge. |
@jamesmunns what is the current status of this PR? Does it need some discussion/changes or can it be merged right now? |
bors try |
tryBuild succeeded |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, let's land this and take it from there.
bors r+ |
221: Improve ci r=therealprof a=Emilgardis This pr includes - Support for the changes done in v0.13 - `--toolchain foo` to specify what toolchain to build the chips with (makes building locally easier, no need to rebuild `svd2rust-regress`) - Add support for `--chip XXX YYY` - Added validators to chip, manufacturer and architecture - `-vv` will now output all stderr logs - Added `--list` to quickly troubleshoot what test cases will be run - A patched ATSAMD21G18A svd, thanks to @wez ## Open "issues" - Should we ignore case when filtering? - Should a `--chip XXX` always run even if it is set to only run on `--long-test` (and possibly `--bad-test`) - Add a `--` command to pass arguments to `svd2rust` and possibly also a way to pass arguments to `cargo check` - Colorize output - Add regress:beta test to gitlab-runner - Move test cases to a or multiple config file(s) (e.g json/toml/yaml) cc @jamesmunns Co-authored-by: Emil Gardström <emil.gardstrom@gmail.com> Co-authored-by: Vadim Kaushan <admin@disasm.info>
Build succeeded |
This pr includes
--toolchain foo
to specify what toolchain to build the chips with (makes building locally easier, no need to rebuildsvd2rust-regress
)--chip XXX YYY
-vv
will now output all stderr logs--list
to quickly troubleshoot what test cases will be runOpen "issues"
--chip XXX
always run even if it is set to only run on--long-test
(and possibly--bad-test
)--
command to pass arguments tosvd2rust
and possibly also a way to pass arguments tocargo check
cc @jamesmunns