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
Process --run
and --skip
in the envtool
itself
#3969
Comments
AlekSi
added
code/chore
Code maintenance improvements
not ready
Issues that are not ready to be worked on; PRs that should skip CI
labels
Jan 12, 2024
AlekSi
added
good first issue
Good issues for new external contributors
and removed
not ready
Issues that are not ready to be worked on; PRs that should skip CI
labels
Jan 12, 2024
9 tasks
@korzio Hi, I see we have a conflict here 😢 |
@fadyat ah I see thx. Well, next time for me than 😢 |
That's exactly why we ask contributors to leave a comment on the issue before starting working on it (https://github.com/FerretDB/FerretDB/blob/main/CONTRIBUTING.md#finding-something-to-work-on) |
AlekSi
added
community
Issues and PRs assigned to community members
and removed
good first issue
Good issues for new external contributors
labels
Jan 24, 2024
9 tasks
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What should be done?
Currently, when
envtool tests run
is invoked with--run
and/or--skip
flags, we just pass those values togo test
's-run
and-skip
, skip tests listing and sharding. That makes the output less useful: there is no known number of total tests, the progress indicator is worse, etc.Let's get a list of tests as usual, then apply
--run
and--skip
's regular expressions ourselves, then shard the resulting list.Where?
FerretDB/cmd/envtool/tests.go
Lines 356 to 398 in 1e736b9
Definition of Done
envtool
code updated;envtool
's unit tests added/updated;The text was updated successfully, but these errors were encountered: