projectatomic / adb-tests Goto Github PK

View Code? Open in Web Editor NEW

7.0 7.0 19.0 1.68 MB

placeholder for tests for the adb while its long term place to live is sorted out

License: GNU General Public License v2.0

Ruby 4.81% Shell 59.72% Makefile 1.24% Python 34.23%

adb-tests's People

Contributors

Stargazers

Watchers

Forkers

cdrage praveenkumar lalatendumohanty dustymabe dharmit rtnpro concaf anushshetty lovejavaee naina-verma amitkrout pavanbhat21 optak thatdocslady ashetty1 agajdosi yuechengzhishang bluemutedwisdom

adb-tests's Issues

vagrant_sanity.py throwing ERROR|child.sendline (self.sudo_PASSWORD)

vagrant_sanity.py", line 72, in test_vagrant_up_register 2016-10-06 11:29:55,379 stacktrace L0042 RROR| child.sendline (self.sudo_PASSWORD)

Update Readme

Currently readme looks outdated and it need to be updated also we can add some sample test case to get involvement from contributors.

Vagrant up needs a library

Currently vagrant up is included in the vagrant sanity test, it would better to have this functionality in the library so that other test can easily use it

tar error if tests are an NFS mount

Steps to reproduce:

Mount the adb-tests directory to the machine running the tests over NFSv3.
In adb-tests/cdrage-atomicapp-ci run make clean-all install docker.
It might run the first time, but from the next time the test it run, it starts failing like the following, even with sudo make ...

...
  ##########
  INSTALLING ATOMIC CLI
  ##########

--2016-02-26 09:20:45--  https://github.com/projectatomic/atomic/archive/v1.8.tar.gz
Resolving github.com (github.com)... 192.30.252.131
Connecting to github.com (github.com)|192.30.252.131|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/projectatomic/atomic/tar.gz/v1.8 [following]
--2016-02-26 09:20:46--  https://codeload.github.com/projectatomic/atomic/tar.gz/v1.8
Resolving codeload.github.com (codeload.github.com)... 192.30.252.160
Connecting to codeload.github.com (codeload.github.com)|192.30.252.160|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 800198 (781K) [application/x-gzip]
Saving to: ‘atomic.tar.gz’

100%[===================================================================================================================================>] 800,198      543KB/s   in 1.4s   

2016-02-26 09:20:49 (543 KB/s) - ‘atomic.tar.gz’ saved [800198/800198]

atomic-1.8/
atomic-1.8/.gitignore
tar: atomic-1.8/.gitignore: Cannot change ownership to uid 0, gid 0: Operation not permitted
atomic-1.8/Atomic/
atomic-1.8/Atomic/Export.py
tar: atomic-1.8/Atomic/Export.py: Cannot change ownership to uid 0, gid 0: Operation not permitted
atomic-1.8/Atomic/Import.py
tar: atomic-1.8/Atomic/Import.py: Cannot change ownership to uid 0, gid 0: Operation not permitted
atomic-1.8/Atomic/__init__.py
tar: atomic-1.8/Atomic/__init__.py: Cannot change ownership to uid 0, gid 0: Operation not permitted
atomic-1.8/Atomic/atomic.py
tar: atomic-1.8/Atomic/atomic.py: Cannot change ownership to uid 0, gid 0: Operation not permitted
atomic-1.8/Atomic/diff.py
...
...

Vagrant up fails with error

This line ``self.log.info(child.after)` is throwing error. Need to debug it more

Add mesos testing too for cdrage-atomicapp-ci tests

Let's try to figure out how to get mesos / marathon into a container :) and test against atomicapp.

Returning wrong vagrant up status

This statement ``self.assertEqual(0, rc, "Vagrant up returned non-zero exit code")` returns 0 even if openshift service failed to start.

Throwing NameError: global name 'pexpect' is not defined

vagrant_sshfs.py throws NameError: global name 'pexpect' is not defined

-z no longer in nc, kubernetes tests fail

sudo make clean-all install kubernetes fails like this:

...
...
2ffe575e81f34a672d10cb1d1f9b096cf842e2bc823def2dcf0039d37acaf00d
Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
nc: invalid option -- 'z'
Ncat: Try `--help' or man(1) ncat for more information, usage options and help. QUITTING.
...
nc: invalid option -- 'z'
Ncat: Try `--help' or man(1) ncat for more information, usage options and help. QUITTING.
...
nc: invalid option -- 'z'
Ncat: Try `--help' or man(1) ncat for more information, usage options and help. QUITTING.
...
nc: invalid option -- 'z'
Ncat: Try `--help' or man(1) ncat for more information, usage options and help. QUITTING.
...
...