(Difference between revisions)
|
|
| Line 1: |
Line 1: |
| - | == System tests results ==
| |
| - | === OTS 0.8 (Jan 13, 2011) ===
| |
| - | Failed cases:
| |
| - | test_multiple_devicegroups (log_tests.TestDeviceProperties) ... FAIL
| |
| - | test_one_devicegroup_multiple_devicenames (log_tests.TestDeviceProperties) ... FAIL
| |
| - | test_one_devicegroup_one_devicename_multiple_device_ids (log_tests.TestDeviceProperties) ... FAIL
| |
| - | test_bad_distribution_model (log_tests.TestErrorConditions) ... FAIL
| |
| - | test_perpackage_distribution_no_packages (log_tests.TestErrorConditions) ... FAIL
| |
| - | Passed cases:
| |
| - | test_bad_image_url (log_tests.TestErrorConditions) ... ok
| |
| - | test_bad_testpackage_names (log_tests.TestErrorConditions) ... ok
| |
| - | test_no_image_url (log_tests.TestErrorConditions) ... ok
| |
| - | test_non_existing_devicegroup (log_tests.TestErrorConditions) ... ok
| |
| - | test_non_existing_sw_product (log_tests.TestErrorConditions) ... ok
| |
| - | test_timeout (log_tests.TestErrorConditions) ... ok
| |
| - | test_host_based_testrun_split_into_multiple_tasks (log_tests.TestSuccessfulTestruns) ... ok
| |
| - | test_host_based_testrun_with_multiple_tests (log_tests.TestSuccessfulTestruns) ... ok
| |
| - | test_host_based_testrun_with_test_definition_tests (log_tests.TestSuccessfulTestruns) ... ok
| |
| - | test_hw_and_host_based_testrun_split_into_multiple_tasks (log_tests.TestSuccessfulTestruns) ... ok
| |
| - | test_hw_and_host_based_testrun_with_test_definition_tests (log_tests.TestSuccessfulTestruns) ... ok
| |
| - | test_hw_based_testrun_split_into_multiple_tasks (log_tests.TestSuccessfulTestruns) ... ok
| |
| - | test_hw_based_testrun_with_multiple_tests (log_tests.TestSuccessfulTestruns) ... ok
| |
| - | test_hw_based_testrun_with_test_definition_tests (log_tests.TestSuccessfulTestruns) ... ok
| |
| - | test_testrun_with_filter (log_tests.TestSuccessfulTestruns) ... ok
| |
| - |
| |
| | == Using virtualenv with OTS == | | == Using virtualenv with OTS == |
| | === Setting up virtual environment === | | === Setting up virtual environment === |
Latest revision as of 09:40, 9 August 2011
Using virtualenv with OTS
Setting up virtual environment
Install virtualenv using package manager
sudo [aptitude/yum] install python-virtualenv
Create virtual environment to your OTS root directory with following command. It creates .env directory which will include bin, include and lib directories. When using '--no-site-packages' parameter virtualenv will not inherit any packages from your global site-packages directory.
virtualenv --no-site-packages ENV
Set environment by sourcing activate file from ENV/bin folder.
source ENV/bin/activate
Now 'which python' command should point to your ENV/bin/python file.
Installing packages to virtual environment
Now let's install python packages needed by OTS to virtual environment. Run command
pip install --upgrade minixsv amqplib django configobj
Packages will be installed under ENV/lib/python2.6/site-packages directory.
Installing OTS
Install OTS normal way using 'python setup.py install' command under component directory (no need to do it as root).
Now 'which ots_server' should point to ENV/bin/ots_server file, and you can start is as normal user.
To leave virtual environment give command
deactivate
Starting OTS
OTS will read configuration files under /etc directory, so configuration files must be copied to there. When starting OTS you need to do it as root, or give write permission for a user write log files and do the flashing. Then you can activate virtualenv in two different terminals and start ots_server and ots_worker.