Last active
June 23, 2017 22:38
-
-
Save ganeshmaharaj/6adecde7f854e5448109012dfa66ec43 to your computer and use it in GitHub Desktop.
Use CC to run Ceph's make-check script
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Ceph has a script 'run-make-check.sh' https://github.com/ceph/ceph/blob/master/run-make-check.sh which is used to build & run | |
a tiny ceph cluster in memory and run tests against it. Ceph CI runs this test inside a VM they spawn on a cloud environment. | |
* When doing this within a traditional docker container, the test completes all the time but there are random failures each time | |
leading to a false positive which doesn't help the case where i am testing a change for regressions. I suspect this is cause | |
of a single kernel and there is something interesting happening when the test is being run. There is no data to backup this | |
comment of mine. | |
* Running it inside a traditional VM is extremely slow and becomes a no-go. | |
* I tried testing this within a Clear Container to see if I can get the abstraction from the host kernel and still get it faster | |
than a traditional VM. in my tests the build takes as long as it does on a VM but the test never completes. the whole container | |
hangs once the tests start and there is no way i can interact with it other than killing it completely. Config has been | |
modified to give CC container 8G of RAM and 8 cores. | |
ENV: | |
For both runc and cor | |
docker run -it -d --name ubuntu-xenial-container -e http_proxy=http://proxy-sc.intel.com:911 | |
-e https_proxy=http://proxy-sc.intel.com:912 -e no_proxy=localhost,.intel.com,127.0.0.1 | |
-v /data/workspace/ceph/ceph:/data/workspace/ceph/ceph ubuntu:xenial bash | |
docker exec -it ubuntu-xenial-container | |
cd /data/workspace/ceph/ceph | |
./run-make-check.sh |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment