-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Status of tests #1525
Status of tests #1525
Conversation
Ok, it turns out that there is just way too much data associated with this run, so I will try to split up the results into multiple comments. CI RESULTS
Summary of the problem(s):
|
And now for the files... Associated Uploads
Uploads will be available until Comment created by |
A few more details. The full run took: The following tests took longer than an hour to complete:
Obviously the recurring snapshots test can be improved. Also, the shared network tests seem to take a pretty long time as well. Not sure why it took 2 hours to test stopped vm, that seems a bit odd. All said, we have some areas for improvement here... |
ACS CI BVT RunSumarry: Link to logs Folder (search by build_no): https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0 Failed tests:
Skipped tests: Passed test suits: |
Not relevant anymore. Closing... |
This PR is not meant to be merged, but instead be able to give a point in time status of our current tests (on KVM).
I have just finished a 3 day run of all of our tests in the root directory of
test/integration/smoke
andtest/integration/component
which I will be posting to this PR.The purpose of posting these results is to help everyone understand what tests are having problems and we will hopefully be able to find a relatively comprehensive set of tests that we can run on every PR. I don't think running all the tests on every PR is realistic considering it took 3 days to run all these tests.
Next I will be pulling out all of the failed tests and building in some logic to time each of the tests so I can figure out which tests are taking the longest to run. I will also be looking into ways of parallelizing these tests.
Anyway, here is a start...