-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add TIOCSBRK and TIOCCBRK #1587
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
Conversation
r? @gnzlbg (rust_highfive has picked a reviewer for you, use r? to override) |
d3c18c1
to
e25a83e
Compare
Got a few errors on some platforms that just say "bash error XXX", so force-repushing to trigger a CI rerun. We'll see what happens. |
e25a83e
to
9c0772d
Compare
Looks like fetching some packages is failing on some builds, not really certain why or if it's a temporary thing (I would assume so). I'll let it sit a couple of days and rerun again. |
@bors: r+ |
📌 Commit 9c0772d has been approved by |
💔 Test failed - status-azure |
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 sparc64-unknown-linux-gnu failure is legit.
@Susurrus can you take a look at the failure? |
6915e9b
to
0a4e073
Compare
Don't know why that last one failed; couldn't tell what the error was. Force repushed to trigger a new CI run. |
So it's failing due to timing out, but the platforms that didn't get tested that last time were passing earlier so I think this is ready to merge, just needs some playing with CI flakiness. |
0a4e073
to
a459d0f
Compare
So, I've force-pushed twice and I'm still getting the same CI time-out failures. Don't know what to do to push this forward. |
Anything I can do to keep this moving forward? |
1 similar comment
Anything I can do to keep this moving forward? |
@bors: r+ |
📌 Commit a459d0f has been approved by |
💔 Test failed - status-azure |
Looks like it's still failing, but looks like a package is failing to install on one of the builds. However, it's been rerun several times now, and I think it's all been the same failure. Is this affecting other PRs or what can we do to resolve this? |
a459d0f
to
a0952c2
Compare
So now that And |
☔ The latest upstream changes (presumably #1719) made this pull request unmergeable. Please resolve the merge conflicts. |
a0952c2
to
be7b2c0
Compare
Only failing on |
The failure should be fixed by #1754, could you rebase? |
Reorganized some constants as well so they're grouped a bit better.
be7b2c0
to
524ec8f
Compare
CI finally passed! |
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.
Looks good, thanks!
No description provided.