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
Cherry pick #61869 to 24.1: Fix flaky tests 2 (stateless, integration) #62027
Cherry pick #61869 to 24.1: Fix flaky tests 2 (stateless, integration) #62027
Conversation
…r frequently and less time
Run pytest --pdb. On failure or breakpoint, it will fall back to PDB. Commands written here will be saved to a local file and loaded at the start of the next test run.
Fix flaky tests 2 (stateless, integration)
Dear @fm4v, @tavplubix, the PR is not updated for 1d24h1m40s. Please, either resolve the conflicts, or close it to finish the backport process of #61869 |
Dear @fm4v, @tavplubix, the PR is not updated for 1d25h0m7s. Please, either resolve the conflicts, or close it to finish the backport process of #61869 |
Dear @fm4v, @tavplubix, the PR is not updated for 1d24h59m59s. Please, either resolve the conflicts, or close it to finish the backport process of #61869 |
Dear @fm4v, @tavplubix, the PR is not updated for 1d24h58m5s. Please, either resolve the conflicts, or close it to finish the backport process of #61869 |
…pick/24.1/a63f4783bf88b78e919e53c0a813dbc73dde9716
Original pull-request #61869
This pull-request is a first step of an automated backporting.
It contains changes similar to calling
git cherry-pick
locally.If you intend to continue backporting the changes, then resolve all conflicts if any.
Otherwise, if you do not want to backport them, then just close this pull-request.
The check results does not matter at this step - you can safely ignore them.
Note
This pull-request will be merged automatically. Please, do not merge it manually (but if you accidentally did, nothing bad will happen).
Troubleshooting
If the PR was manually reopened after being closed
If this PR is stuck (i.e. not automatically merged after one day), check #61869 for
pr-backports-created
label and delete it.Manually merging will do nothing. The
pr-backports-created
label prevents the original PR #61869 from being processed.If the conflicts were resolved in a wrong way
If this cherry-pick PR is completely screwed by a wrong conflicts resolution, and you want to recreate it:
pr-cherrypick
label from the PRYou also need to check the original PR #61869 for
pr-backports-created
, and delete if it's presented there