-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
[beta] Release notes, dist with time crate, and #48092 #48146
Conversation
Note that #48092 has not yet been approved for beta backport, but it seems like a minimal patch that eddyb has cherry picked cleanly. If we don't make a decision by the time we're going to begin cutting stable this'll probably not go in. |
@bors: r+ p=100 |
📌 Commit 3ed7697 has been approved by |
⌛ Testing commit 3ed7697 with merge 29b633c09f17d329878af0b0c569a2ff7d0e469c... |
💔 Test failed - status-travis |
no space left on device -- #48144 |
This should save a lot of space on musl test cases (whose standard library are linked statically).
This isn't a perfect heuristic, but since the amount of run-fail tests is far lower than run-pass tests for now, it should be sufficient to ensure that we don't run into CI limits. This makes it possible to run the test binary manually (e.g., under gdb/lldb) if it failed to attempt to find out why.
@bors r=alexcrichton |
📌 Commit 17d0d6a has been approved by |
⌛ Testing commit 17d0d6a with merge bc4f7624eada6eb7adcdbda87fce95fb1be123e9... |
💔 Test failed - status-travis |
@bors retry Looks spurious.
|
⌛ Testing commit 17d0d6a with merge 97374005c34adb40f0e94d3ae014c50423afe08d... |
💔 Test failed - status-appveyor |
@bors retry -- appveyor timed out |
☀️ Test successful - status-appveyor, status-travis |
Backports of