-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Add documentation for Run extended tests command
#15463
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
| code works when there are hash collisions as well as running the relevant | ||
| portions of the entire [sqlite test suite]. | ||
|
|
||
| You can run the extended tests on any PR by leaving the following comment (see [example here]): |
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.
so to run extended tests, is it optional or is it to rerun failed tests?
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.
Normally extended tests don't run on PRs, only after merges to main
If you want to run extended tests on a PR prior to merge, now you by leaving a Run extended test comment on the PR
comphead
left a comment
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.
lgtm thanks @alamb
|
Thanks @comphead and @xudong963 |
* Add documentation for `Run extended tests` command * Update docs/source/contributor-guide/testing.md --------- Co-authored-by: Oleks V <comphead@users.noreply.github.com>
Which issue does this PR close?
extendedtest suite from a PR #14319Run extended tests#15101Rationale for this change
@danila-b made a workflow action to run extended tests in #15101 and I would like to make sure it documented
What changes are included in this PR?
Add a note in the contributor guide about how to run the tests
Are these changes tested?
Are there any user-facing changes?