Skip to content

add torture test on azure #4697

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

Closed
wants to merge 2 commits into from
Closed

add torture test on azure #4697

wants to merge 2 commits into from

Conversation

bagder
Copy link
Member

@bagder bagder commented Dec 10, 2019

This is a more complete torture test than what has run on travis, as a first shot to see how much it can complete on azure.

@bagder bagder added the build label Dec 10, 2019
@bagder
Copy link
Member Author

bagder commented Dec 10, 2019

Running through them all, even excluding the FTP ones, just takes too long time. Look at the final one before azure timed out the job:

test 0556...[send and recv HTTP]
 28450 functions to make fail

I'll land #4699 first to allow us to limit the hammering per test a bit and see if I can then tweak this to go through more tests.

@bagder
Copy link
Member Author

bagder commented Dec 11, 2019

Immediate success. First PR as a result: #4705

@bagder bagder force-pushed the bagder/azure-torture branch 3 times, most recently from c0b41d6 to 98dba8b Compare December 13, 2019 07:20
@bagder bagder force-pushed the bagder/azure-torture branch from 98dba8b to 92c18ef Compare December 13, 2019 12:02
@bagder
Copy link
Member Author

bagder commented Dec 13, 2019

Green!

To observe: test 1456 seems to have failed (unrelated) on both azure and github recently. Area for research/marking as flaky.

@bagder bagder closed this in ec3758b Dec 13, 2019
@bagder bagder deleted the bagder/azure-torture branch December 13, 2019 13:53
@lock lock bot locked as resolved and limited conversation to collaborators Mar 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

Successfully merging this pull request may close these issues.

1 participant