-
Notifications
You must be signed in to change notification settings - Fork 228
Conversation
kindly ping @stealthybox if this e2e looks make sense to you, I'll continue adding more tests. |
Please merge #413 before this one. |
be41bd0
to
c5da073
Compare
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.
After I rebased on master
, building a fresh binary results in a passing e2e test.
We should probably incorporate this into the Makefile
at some point with a dependency on the ignite binary so that a dev can just make e2e
and not worry about the state of their build.
make ignite > /dev/null && echo built ignite
built ignite
sudo IGNITE_E2E_HOME=$PWD $(which go) test ./e2e/. -count 1
ok github.com/weaveworks/ignite/e2e 2.271s
sudo dmsetup ls
cryptswap (253:0)
sudo ctr -n firecracker c ls
CONTAINER IMAGE RUNTIME
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
I suggested a quick edit.
If you accept it, I think this a great starting point and we can merge it.
P.S: can you run make tidy-in-docker
and see if you get the same vendor output?
c5da073
to
cbfa553
Compare
For the To run e2e tests, a dev would go with |
Signed-off-by: Chanwit Kaewkasi <chanwit@gmail.com>
cbfa553
to
b4eea11
Compare
Added a simple e2e test for
ignite run
command. This one is to test under docker / docker-bridge environment. Tests for containerd / cni will be added after #411 get merged.e2e tests will be used locally at the moment for devs, and later should be with the CI when we could test them in a remote KVM environment.
This PR fixes #391