Conversation
There was a problem hiding this comment.
Looks good in general - I think you'll be racing on the Clean Up Containers and Images however.
I'm also not sure we need to clean up existing containers for most tests, and images for even fewer.
The ps tests definitely assert number of lines in output, but many others don't care. If we support labels we may be able to label the containers with the build number/test name so that filtering can be used when needed.
tests/resources/VCH-Util.robot
Outdated
| [Return] ${output} | ||
|
|
||
| Cleanup Containers And Images | ||
| ${out}= Run docker %{VCH-PARAMS} ps -aq | xargs -n1 docker %{VCH-PARAMS} rm -f |
There was a problem hiding this comment.
you shouldn't need the -n1 but I don't think it'll hurt
|
Can we have each test suite make a "Get VCH" call or similar. Flow would be:
|
80ae2e7 to
e79962f
Compare
e67f606 to
41a8ae2
Compare
41a8ae2 to
406e6c1
Compare
|
Still seeing TLS handshake timeouts with @caglar10ur latest changes. |
|
I think we are getting those cause the ESXi is getting slower and eventually timing out. Can we collect the host statistics during the run to see whether 1) This speculation is correct 2) The slowness is CPU or IO bound 3) we can do something about it? |
ad376d4 to
6250499
Compare
|
@mhagen-vmware This seems to have issue with cleaning up container VMs as observed in this build running on builds-16.vmware.run. There were about 87 VMs left over. |
looks like someone restarted the host ESXi server while the tests are running |
|
I restarted it afterwards, because the system was in a state that we continue to see. In which everything appears up, but the system reports wrong password when trying to login or do anything via govc. A system reboot through OVH is needed and fixes it. |
2b1c481 to
0b314d5
Compare
.drone.local.yml
Outdated
|
|
||
| vic-integration-test-on-pr: | ||
| image: ${TEST_BUILD_IMAGE=gcr.io/eminent-nation-87317/vic-integration-test:1.39} | ||
| image: ${TEST_BUILD_IMAGE=gcr.io/eminent-nation-87317/vic-integration-test:1.37} |
There was a problem hiding this comment.
should be we reverting to 1.37 from 1.39?
tests/integration-test.sh
Outdated
| if [[ $DRONE_BRANCH == "master" || $DRONE_BRANCH == "releases/"* ]] && [[ $DRONE_REPO == "vmware/vic" ]] && [[ $DRONE_BUILD_EVENT == "push" ]]; then | ||
| echo "Running full CI for $DRONE_BUILD_EVENT on $DRONE_BRANCH" | ||
| pybot --removekeywords TAG:secret --exclude skip tests/test-cases | ||
| pabot --processes 2 --removekeywords TAG:secret --exclude skip tests/test-cases |
There was a problem hiding this comment.
parameterize the number of processes or do we want to be able to chose per-scenario values?
d23af43 to
ccb1778
Compare
ccb1778 to
5f4e2ab
Compare
Codecov Report
@@ Coverage Diff @@
## master #5601 +/- ##
=======================================
Coverage 26.07% 26.07%
=======================================
Files 37 37
Lines 5243 5243
=======================================
Hits 1367 1367
Misses 3769 3769
Partials 107 107Continue to review full report at Codecov.
|
(cherry picked from commit 02ba3ad)
(cherry picked from commit 02ba3ad)
[skip unit]
[full ci]