#267 Do not run multiprocessing on multiple processes

  * the combo of py.test threading and multiprocessing with our own
    tests of threading and multiprocessing is likely too much and
    adding some monkey wrench in the test setup. We now run the scancode
    CLI tests sequentially.

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>

Author: pombredanne

.travis.yml

@@ -5,7 +5,8 @@ os:
   - linux 
 
 env:
-  - TEST_SUITE: bin/py.test -n 2 -s
+  - TEST_SUITE: bin/py.test -n 2 -s --ignore=tests/scancode/
+  - TEST_SUITE: bin/py.test -vvs tests/scancode/
   - TEST_SUITE: ./etc/release/release.sh
 
 

appveyor.yml

@@ -7,7 +7,8 @@ build: off
 
 test_script:
     - python -c "import sys;print sys.getdefaultencoding()"
-    - py.test -n 2 -s
+    - py.test -n 2 -s --ignore=tests/scancode/
+    - py.test -vvs tests/scancode/
 
 on_success:
   - "python etc/scripts/irc-notify.py aboutcode [{project_name}:{branch}] {short_commit}: \"{message}\" ({author}) {color_green}Succeeded,Details: {build_url},Commit: {commit_url}"