Merge lp:~fgimenez/snappy/config-for-remote-testbeds into lp:~snappy-dev/snappy/snappy-moved-to-github
| Status: | Merged |
|---|---|
| Approved by: | Federico Gimenez on 2015-07-31 |
| Approved revision: | 626 |
| Merged at revision: | 623 |
| Proposed branch: | lp:~fgimenez/snappy/config-for-remote-testbeds |
| Merge into: | lp:~snappy-dev/snappy/snappy-moved-to-github |
| Prerequisite: | lp:~fgimenez/snappy/generalize-build-tests-across-versions |
| Diff against target: |
120 lines (+44/-5) 4 files modified
_integration-tests/main.go (+4/-2) _integration-tests/tests/info_test.go (+8/-0) _integration-tests/testutils/config/config.go (+3/-2) _integration-tests/testutils/config/config_test.go (+29/-1) |
| To merge this branch: | bzr merge lp:~fgimenez/snappy/config-for-remote-testbeds |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Leo Arias | 2015-07-29 | Approve on 2015-07-31 | |
|
Review via email:
|
|||
Commit Message
Do not run tests that make assertions about release and channel in config when connecting to remote testbed
Description of the Change
Do not run tests that make assertions about release and channel in config when connecting to remote testbed
- 621. By Federico Gimenez on 2015-07-30
-
Skipping info test when executing in remote testbed
| Federico Gimenez (fgimenez) wrote : | # |
I agree, the problem here are the default values of release and channel, if not specified they are not empty strings.
I've opted for your second suggestion, skipping the test when executing in remote testbeds, but using the given testbedIP to check if the testbed is remote, let me know what do you think.
Thanks!
- 622. By Federico Gimenez on 2015-07-30
-
merged prerequisite
- 623. By Federico Gimenez on 2015-07-30
-
merge prerequisite
| Leo Arias (elopio) wrote : | # |
> I agree, the problem here are the default values of release and channel, if
> not specified they are not empty strings.
Right, I understand now.
This is ok, so +1. A couple of alternatives that might be clearer or not would be:
- Instead of passing the test bed ip in the config, pass a boolean value that's "remote", set to true when the --ip flag is used.
- When the --ip flag is used, save "" as the release and channel in the config, instead of the default values.
I really don't know which is better between your current approach and those other two options, so I leave the top-approval to you. If you prefer it as it is, please go ahead and merge.
- 624. By Federico Gimenez on 2015-07-31
-
merged trunk
- 625. By Federico Gimenez on 2015-07-31
-
RemoteTestbed field for config
- 626. By Federico Gimenez on 2015-07-31
-
merged trunk
| Federico Gimenez (fgimenez) wrote : | # |
Ok, I've gone for the first option, having a RemoteTestbed boolean field in the config. Tested in rolling and 15.04, top-approving
Thanks!


One comment for discussion.