Skip to content
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

[Test] Re-try paratest #3753

Merged
merged 1 commit into from
May 7, 2023
Merged

[Test] Re-try paratest #3753

merged 1 commit into from
May 7, 2023

Conversation

samsonasik
Copy link
Member

@TomasVotruba with various performance improvement and fixes for duplicate fixtures, let's try bring back paratest to speed up running test

@samsonasik samsonasik enabled auto-merge (squash) May 7, 2023 12:48
@samsonasik samsonasik merged commit 6c1045f into main May 7, 2023
@samsonasik samsonasik deleted the bring-back-paratest branch May 7, 2023 12:53
@samsonasik
Copy link
Member Author

@TomasVotruba it seems happen again in 98% run test:

https://github.com/rectorphp/rector-src/actions/runs/4907301256/jobs/8762329713

I will rollback

samsonasik added a commit that referenced this pull request May 7, 2023
@samsonasik
Copy link
Member Author

#3754

samsonasik added a commit that referenced this pull request May 7, 2023
@staabm
Copy link
Contributor

staabm commented May 7, 2023

does it always die at the same test-cases.. maybe we can put these in a group and let them run in serial fashion?

@samsonasik
Copy link
Member Author

Probably using --debug or --v can see the actual test that error, that error is on random run, so not always shown, @TomasVotruba suggest to not use it at all at #3754

samsonasik added a commit that referenced this pull request May 8, 2023
samsonasik added a commit that referenced this pull request May 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants