-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Specify units for test timeout environment variables #68097
Conversation
r? @shepmaster (rust_highfive has picked a reviewer for you, use r? to override) |
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.
In the realm of being clear, instead of "Clarify test timeout evironment variables", let's say
Specify units for test timeout environment variables
(note typo fix as well)
Care to link to the appropriate place so we can verify you read the code correctly? 👼 |
Sure. Here is code that parses env vars: Line 95 in f795e8a
|
Thanks! @bors r+ rollup |
📌 Commit 91e9531 has been approved by |
Specify units for test timeout environment variables I think it is not obvious (I got it from reading libtest sources), so it is worth mentioning in docs.
Specify units for test timeout environment variables I think it is not obvious (I got it from reading libtest sources), so it is worth mentioning in docs.
Rollup of 8 pull requests Successful merges: - #67313 (Document more use cases of dataflow) - #67959 (rustdoc: improve stability mark arrows) - #68097 (Specify units for test timeout environment variables) - #68135 (restore some rustc_parse visibilities for rustfmt) - #68145 (Expose `context::CheckLintNameResult`) - #68156 (Fix crate paths in comments) - #68157 (Clean up E0186 explanation) - #68161 (Fix system call docs for time::Instant) Failed merges: r? @ghost
I think it is not obvious (I got it from reading libtest sources), so it is worth mentioning in docs.