Skip to content

Integration test script refinement and fixes [skip ci]#8063

Merged
hickeng merged 3 commits intovmware:masterfrom
hickeng:fix-nightlies3
Jun 16, 2018
Merged

Integration test script refinement and fixes [skip ci]#8063
hickeng merged 3 commits intovmware:masterfrom
hickeng:fix-nightlies3

Conversation

@hickeng
Copy link
Contributor

@hickeng hickeng commented Jun 16, 2018

  1. correct link construction for download of log bundles
  2. correct custom test bed specified case in nimbus utils
  3. clean generated log file name

Confirmed in build https://vic-jenkins.eng.vmware.com/job/vic-integration-base/44/console

@hickeng hickeng requested a review from a team as a code owner June 16, 2018 16:38
@hickeng hickeng force-pushed the fix-nightlies3 branch 6 times, most recently from 359c80d to 3b1d40a Compare June 16, 2018 20:21
1. correct link construction for download of log bundles
2. correct custom test bed specified case in nimbus utils
3. clean generated log file name
@hickeng hickeng changed the title Integration test script refinement and fixes Integration test script refinement and fixes [skip ci] Jun 16, 2018
hickeng added 2 commits June 16, 2018 14:04
The spec has been moved to the end to reduce the changes
necessary in calls to the Nimbus Deploy Testbed keyword that
do not specify a custom testbed file.
@hickeng hickeng merged commit 0f68789 into vmware:master Jun 16, 2018
hickeng added a commit to hickeng/vic that referenced this pull request Jun 17, 2018
This builds on vmware#8047 and vmware#8063 to address some outstanding issues left by
that work. In the case of the hetrogeneous and NFS tests, it is test
updates necessitated by the prior Nimbus-Util.robot updates.
In the case of the VSAN tests it is addressing removal of a non-existent
path and switching to use the related testbed spec.
hickeng added a commit to hickeng/vic that referenced this pull request Jun 17, 2018
This builds on vmware#8047 and vmware#8063 to address some outstanding issues left by
that work. In the case of the hetrogeneous and NFS tests, it is test
updates necessitated by the prior Nimbus-Util.robot updates.
In the case of the VSAN tests it is addressing removal of a non-existent
path and switching to use the related testbed spec.
hickeng added a commit that referenced this pull request Jun 19, 2018
This builds on #8047 and #8063 to address some outstanding issues left by
that work. In the case of the hetrogeneous and NFS tests, it is test
updates necessitated by the prior Nimbus-Util.robot updates.

In the case of the VSAN tests it switches to using a testbed descriptor
based off the vic-simple-cluster spec instead of what appeared to be a
library spec, testng/testbeds/vsan.rb.

This disables the complex vSAN testsuite at this time as I could not infer
what the complex case was testing, and it is not in the test doc. It's
possible that it's testing multiple vSAN datastores and our ability to use
either but that's pure speculation.
zjs pushed a commit to zjs/vic that referenced this pull request Jul 19, 2018
1. correct link construction for download of log bundles
2. correct custom test bed specified case in nimbus utils
3. clean generated log file name

The spec arg has been moved to the end to reduce the changes
necessary in calls to the Nimbus Deploy Testbed keyword that do
not specify a custom testbed file.

(cherry picked from commit 0f68789)
zjs pushed a commit to zjs/vic that referenced this pull request Jul 19, 2018
This builds on vmware#8047 and vmware#8063 to address some outstanding issues left by
that work. In the case of the hetrogeneous and NFS tests, it is test
updates necessitated by the prior Nimbus-Util.robot updates.

In the case of the VSAN tests it switches to using a testbed descriptor
based off the vic-simple-cluster spec instead of what appeared to be a
library spec, testng/testbeds/vsan.rb.

This disables the complex vSAN testsuite at this time as I could not infer
what the complex case was testing, and it is not in the test doc. It's
possible that it's testing multiple vSAN datastores and our ability to use
either but that's pure speculation.

(cherry picked from commit d533414)
zjs pushed a commit to zjs/vic that referenced this pull request Jul 27, 2018
1. correct link construction for download of log bundles
2. correct custom test bed specified case in nimbus utils
3. clean generated log file name

The spec arg has been moved to the end to reduce the changes
necessary in calls to the Nimbus Deploy Testbed keyword that do
not specify a custom testbed file.

(cherry picked from commit 0f68789)
zjs pushed a commit to zjs/vic that referenced this pull request Jul 27, 2018
This builds on vmware#8047 and vmware#8063 to address some outstanding issues left by
that work. In the case of the hetrogeneous and NFS tests, it is test
updates necessitated by the prior Nimbus-Util.robot updates.

In the case of the VSAN tests it switches to using a testbed descriptor
based off the vic-simple-cluster spec instead of what appeared to be a
library spec, testng/testbeds/vsan.rb.

This disables the complex vSAN testsuite at this time as I could not infer
what the complex case was testing, and it is not in the test doc. It's
possible that it's testing multiple vSAN datastores and our ability to use
either but that's pure speculation.

(cherry picked from commit d533414)
zjs pushed a commit that referenced this pull request Jul 27, 2018
1. correct link construction for download of log bundles
2. correct custom test bed specified case in nimbus utils
3. clean generated log file name

The spec arg has been moved to the end to reduce the changes
necessary in calls to the Nimbus Deploy Testbed keyword that do
not specify a custom testbed file.

(cherry picked from commit 0f68789)
zjs pushed a commit that referenced this pull request Jul 27, 2018
This builds on #8047 and #8063 to address some outstanding issues left by
that work. In the case of the hetrogeneous and NFS tests, it is test
updates necessitated by the prior Nimbus-Util.robot updates.

In the case of the VSAN tests it switches to using a testbed descriptor
based off the vic-simple-cluster spec instead of what appeared to be a
library spec, testng/testbeds/vsan.rb.

This disables the complex vSAN testsuite at this time as I could not infer
what the complex case was testing, and it is not in the test doc. It's
possible that it's testing multiple vSAN datastores and our ability to use
either but that's pure speculation.

(cherry picked from commit d533414)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants