We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I created this job: https://jenkins.plone.org/view/Experimental/job/Shuffle%20tests (it boils down to bin/test --shuffle).
bin/test --shuffle
On the first run we manage to create a stackoverflow! 🔥 https://jenkins.plone.org/view/Experimental/job/Shuffle%20tests/1/console
On the second run only 4 test failures: https://jenkins.plone.org/view/Experimental/job/Shuffle%20tests/2/console
I set it to run once a week.
Is there anything else that we should do here? Send email to someone? 🤔
/cc @Rotonen @tisto @plone/testing-team
The text was updated successfully, but these errors were encountered:
Yes, someone should attend to everything it finds. So we need to find someone interested in the quest and to have that person notified.
As for the run itself, it is doing exactly what that one should do.
Sorry, something went wrong.
No branches or pull requests
I created this job: https://jenkins.plone.org/view/Experimental/job/Shuffle%20tests (it boils down to
bin/test --shuffle
).On the first run we manage to create a stackoverflow! 🔥 https://jenkins.plone.org/view/Experimental/job/Shuffle%20tests/1/console
On the second run only 4 test failures: https://jenkins.plone.org/view/Experimental/job/Shuffle%20tests/2/console
I set it to run once a week.
Is there anything else that we should do here? Send email to someone? 🤔
/cc @Rotonen @tisto @plone/testing-team
The text was updated successfully, but these errors were encountered: