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.

Sign up for GitHub

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

Jump to bottom

CI: consider using cargo-xtask instead #77

Open
tmplt opened this issue Nov 19, 2021 · 0 comments
Open

CI: consider using cargo-xtask instead #77

tmplt opened this issue Nov 19, 2021 · 0 comments
Labels
enhancement New feature or request
Milestone
v0.4.0

Comments

@tmplt
Copy link
Member

tmplt commented Nov 19, 2021

cargo-xtask seems like a better way to test the cargo-rtic-scope binary.
@tmplt tmplt added this to the v0.4.0 milestone Nov 19, 2021
@tmplt tmplt added the enhancement New feature or request label Nov 19, 2021
tmplt added a commit that referenced this issue Jan 11, 2022
@tmplt
sources/tty: apply user-supplied baud rate
dfdbc74 
Before this commit, dev in

    --serial /path/to/dev

would always be configured for 115200 B/s, even if the user supplied
another rate in the manifest via tpiu_baud, e.g. 9600 B/s. A baud rate
that converts to a nix::sys::termios::BaudRate that isn't B0 must be
supplied.

Ideally we should CI this, but that requires a CI refactor so that
--serial can be specified. This is non-trivial, and we better handle #77
first.
@tmplt tmplt mentioned this issue Jan 11, 2022
Merged
@tmplt tmplt modified the milestones: v0.3.1, v0.3.2 Jan 13, 2022
@tmplt tmplt modified the milestones: v0.3.3, v0.4.0 Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
v0.4.0
Development

No branches or pull requests
1 participant
@tmplt