WIP POC MicroShift e2e using robot framework#1635
WIP POC MicroShift e2e using robot framework#1635pmtk wants to merge 39 commits intoopenshift:mainfrom
Conversation
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pmtk The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
e2e-robot/Makefile
Outdated
There was a problem hiding this comment.
You can run .venv/bin/python3 -m pip without activating the environment.
e2e-robot/Makefile
Outdated
There was a problem hiding this comment.
Same here, if you run .venv/bin/robot it should work without activating the environment.
e2e-robot/Makefile
Outdated
There was a problem hiding this comment.
The IP could come from running ./scripts/devenv-builder/manage-vm.sh ip
There was a problem hiding this comment.
Yeah, it could also be passed via ENV vars or other means. I just hardcoded it to reduce typing when PoCing this :)
Not tying it to other scripts can result in scalability - run whatever test suite you want against any VM in parallel.
In regards to ostree upgrade/rollback I have this idea (not sure how it'll pan out):
if we go with "nested virt" approach, then we could setup a job (sanity periodic most likely) that would spawn multiple nested VMs and do some testing in parallel.
Like this mad idea: build 4.14.0 base image (as in qemu backing image, so new VMs can be spawned quickly) and do upgrades (rather by installing new RPMs than preparing whole new image)
.0 ----
| \ \
.1 .2 .3
| |
.2 .3
|
.3
e2e-robot/tests/microshift.robot
Outdated
There was a problem hiding this comment.
Are these paths relative to the directory where someone runs robot, or to the location of the .robot file?
There was a problem hiding this comment.
I think it's relative to current working dir which, when running make inside e2e-robot, is e2e-robot/
|
@pmtk: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
2 participants
See most recent commit