-
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
Automated Cloudstack bugs 9277 9276 9275 9274 9273 9179 9178 9177 #1949
Conversation
@shwetaag Hi, I'm sorry but I don't get what is this PR for? Are these some internal issues that you're referring to? Each PR should start with an ACS JIRA ticket number and should be followed by a description of what it is about. I've noticed you're committing some tests, can you please give an overview what are they about. |
@@ -121,7 +121,7 @@ | |||
"name": "LargeInstance", | |||
"displaytext": "LargeInstance", | |||
"cpunumber": 1, | |||
"cpuspeed": 500, | |||
"cpuspeed": 1024, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
while appending to this list could be fairly non fragile to tests, editing existing entries can be extremely fragile to other tests that are using it. We need to be sure this does not brake any of the smoketests, since they are our main source of verifying PRs.
@borisstoyanov This PR is about automating these 8 cloudstack bugs.
the details of these bugs can be seen in related bugs |
Thank you @shwetaag can you please edit the PR description |
@blueorangutan package |
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-518 |
@blueorangutan test |
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
Trillian test result (tid-872)
|
@rhtyd any updates on this PR .. it shows Travis build failed ..Does this need any action on my part ? |
@shwetaag I see some new failures in Travis around component tests, can you close and reopen this PR to rekick Travis tests? If Travis fails again, please see the failed tests and fix them. |
Closing and reopening this PR as two travis runs have given two different failures |
@rhtyd : I executed all the travis failures manually on my setup and both test case passed Ran 1 test in 820.009s OK Test Create/Destroy VM and verify usage calculation ... === TestName: test_01_vm_usage | Status : SUCCESS === Ran 1 test in 197.750s OK |
Addressed all review comments. Changed all URL to pubic available url where ever possible . For few tests needing rhel7 template or windows server templates added a comment in test case to provide a valid urls for those templates before executing those test cases