-
Notifications
You must be signed in to change notification settings - Fork 300
test: added test scripts for the functional tests #1430
Conversation
I don't understand the use case for this. can you help me understand what it provides over just a bash script that runs this? Since we still need etcd, systemd etc running on the host. |
It is still WIP. And this script will be executed on coreos. |
5a8b858
to
27b9686
Compare
You may also check if etcd is up. |
What is the point of doing this in docker at all? Look how much stuff you necessarily need to bring in from the host.. |
@jonboulle this will allow you to run tests directly on coreos. which already has etcd. |
Why do you need docker for that? The functional tests run fine on coreos kayrus [email protected] schrieb am Fr., 12. Feb. 2016 11:50:
|
@jonboulle there is no go binary inside coreos. |
To elaborate a bit: according to |
@antrik thanks for the context, very helpful. I discussed out of band with @mirkoboehm and we'll circulate notes shortly |
2d4ba84
to
b67bfb8
Compare
ce6756c
to
9f9078f
Compare
@jonboulle tests passed. should we squash and merge? |
83c56da
to
112c46d
Compare
@@ -302,14 +302,18 @@ func (nc *nspawnCluster) createMember(id string) (m Member, err error) { | |||
|
|||
// minimum requirements for running systemd/coreos in a container | |||
fmt.Sprintf("mkdir -p %s/usr", fsdir), | |||
//fmt.Sprintf("mkdir -p %s/lib", fsdir), //ubuntu |
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.
can you explain all these?
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.
I tried to run these tests in ubuntu without cloud-config. Decided to keep this. If you don't like - i'll remove.
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.
We definitely shouldn't leave commented lines in here. Are the lines totally superfluous now? The tests all work fine without?
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.
Yes, they do. Will remove ubuntu stuff. But will keep .. 500 ...
for future support.
@@ -1,29 +1,31 @@ | |||
#!/bin/bash -e | |||
|
|||
CDIR=$(cd `dirname $0` && pwd) |
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.
is this working around some problem you encountered?
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.
Yes, when you run scripts from home directory for example. cd ~ ; ./fleet/build
Then run the functional tests: | ||
|
||
```sh | ||
$ git clone https://github.com/coreos/fleet |
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.
haven't we already cloned?
97daef8
to
79a60c7
Compare
eval $(ssh-agent) | ||
fi | ||
|
||
chmod 600 functional/fixtures/id_rsa |
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.
Please document why we need this one.
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.
Done
For the sake of moving forward: |
7ece6d7
to
180b7e7
Compare
test: added test scripts for the functional tests
subj