-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
merged doctests: regressions due to examining process arguments #130796
Copy link
Copy link
Closed
Labels
A-doctestsArea: Documentation tests, run by rustdocArea: Documentation tests, run by rustdocA-edition-2024Area: The 2024 editionArea: The 2024 editionC-bugCategory: This is a bug.Category: This is a bug.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.Relevant to the rustdoc team, which will review and decide on the PR/issue.
Metadata
Metadata
Assignees
Labels
A-doctestsArea: Documentation tests, run by rustdocArea: Documentation tests, run by rustdocA-edition-2024Area: The 2024 editionArea: The 2024 editionC-bugCategory: This is a bug.Category: This is a bug.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.Relevant to the rustdoc team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
Done
The crater run for merged doctests (#130285) detected a large number of regressions due to tests examining the process arguments. (I don't have an exact number, but let's say ~50 projects.)
Previously, there were no arguments, but now it gets arguments like
*doctest-inner-test 0which the user's CLI parsing code isn't expecting.For example, using something like
StructOpt::from_argswill now fail.It seems to be fairly common to have objects whose default constructor will parse the arguments from the command line.
I'm not sure if or how we should resolve that. One idea is to use a different mechanism for passing in the test information (like via an environment variable).
Meta