m (→Installation) |
m (→Usage: Wiki link fix) |
||
| (10 intermediate revisions not shown) | |||
| Line 21: | Line 21: | ||
OTS is a highly modular system. Most of the Components are designed to be run as tools in their own right. They have command line interfaces and can be run independently. | OTS is a highly modular system. Most of the Components are designed to be run as tools in their own right. They have command line interfaces and can be run independently. | ||
| - | A basic understanding of the [[Quality/QA-tools/OTS/ | + | A basic understanding of the [[Quality/QA-tools/OTS/About|Architecture]] and the responsibilities of the [[Quality/QA-tools/OTS/Components|Components]] should guide you through it. |
There is generally documentation for each of the Components and illustrations on how the the individual tool is run. It is all Open Source, nothing is hidden! | There is generally documentation for each of the Components and illustrations on how the the individual tool is run. It is all Open Source, nothing is hidden! | ||
| Line 50: | Line 50: | ||
== Usage == | == Usage == | ||
| - | If there is a problem in running your test(s). Then once again the logs are a good place to start of which the http logger is the most user friendly. The Exception and traceback should give an indication of the problem. Check what any [ | + | If there is a problem in running your test(s). Then once again the logs are a good place to start of which the http logger is the most user friendly. The Exception and traceback should give an indication of the problem. Check what any [[Quality/QA-tools/OTS/ErrorCodes|error code]] means that might give you a clue. |
== FAQs == | == FAQs == | ||
| Line 60: | Line 60: | ||
=== Where are the Prerequisits for the Host? === | === Where are the Prerequisits for the Host? === | ||
| - | Instructions for key authentication and dependent packages are all dealt with in this [ | + | Instructions for key authentication and dependent packages are all dealt with in this [[Quality/QA-tools/Autotest-guide#Setting_up_test_automation_environment|wiki]] |
=== Why doesn't my device flash? === | === Why doesn't my device flash? === | ||
| - | Flashing can work intermittently with some Architecture / Image combinations. It can also be a time consuming process so a certain degree of patience is required. There are some [ | + | Flashing can work intermittently with some Architecture / Image combinations. It can also be a time consuming process so a certain degree of patience is required. There are some [[Quality/QA-tools/OTS/UserDocumentation|notes]] on flashing here that should help pinpoint the problem. Unfortunately there is always a chance that even if you have things set up correctly and it won't work first time - so try again. |
=== Why won't my host allow me to connect to the device? === | === Why won't my host allow me to connect to the device? === | ||
| Line 70: | Line 70: | ||
Any hardware control operation that requires USB will require the permissions to be set appropriately. | Any hardware control operation that requires USB will require the permissions to be set appropriately. | ||
| - | e.g. By following [ | + | e.g. By following [[Quality/QA-tools/OTS/UserDocumentation/Conductor#Setting_your_USB_permissions_for_Flashing|these]] instructions for flashing you can avoid root access for the Flasher and all the dependent modules (Conductor and Worker) |
| + | |||
| + | === Why won't OTS trigger work? === | ||
| + | |||
| + | You might have an error such as this: | ||
| + | |||
| + | <code> | ||
| + | ProtocolError: <ProtocolError for localhost/xmlrpc/: 500 Internal Server Error> | ||
| + | </code> | ||
| + | |||
| + | Is your using Apache is it set-up properly? - Check the apache logs, your apache2.conf file and DJANGO_SETTINGS_MODULE. | ||
| + | |||
| + | The [[Quality/QA-tools/OTS/Plugins/HTTP_logger | HTTPLogger]] instructions give instructions on server configurations | ||
| + | |||
| + | Not forgetting to restart Apache if there are any changes. | ||
| + | |||
| + | <code> | ||
| + | sudo /etc/init.d/apache2 restart | ||
| + | </code> | ||
Contents |
This troubleshooting guide aims to help with OTS installation and usage.
Please remember that OTS is at a relatively early stage in its development and evolving rapidly and whilst every effort is made to keep all the documentation up-to-date there will be some inevitable time lag.
This section suggests how you can apply simple fault-finding techniques to OTS...
OTS offers extensive logging options
OTS is a highly modular system. Most of the Components are designed to be run as tools in their own right. They have command line interfaces and can be run independently.
A basic understanding of the Architecture and the responsibilities of the Components should guide you through it.
There is generally documentation for each of the Components and illustrations on how the the individual tool is run. It is all Open Source, nothing is hidden!
Assuming you have installed the OTS component you can check the version as follows:
$python
>>> import ots.worker >>> ots.worker.__VERSION__ '0.8r0.0.1-338-gdbe7dev' >>>
Check the OTS bug tracker
If you have been following the Installation Instructions and still run into problems then you might benefit from the Developer Documentation. The Developer Documentation show how the Unit Tests and Component Tests are run. If the unittests or component tests are failing then the tracebacks should give an indication as to what the problems are.
If there is a problem in running your test(s). Then once again the logs are a good place to start of which the http logger is the most user friendly. The Exception and traceback should give an indication of the problem. Check what any error code means that might give you a clue.
If you are firing runs and they don't appear to be taken by the worker it is worth looking at the Queues. This service is provided by RabbitMQ and the rabbitmqctl tool is a useful aid.
Instructions for key authentication and dependent packages are all dealt with in this wiki
Flashing can work intermittently with some Architecture / Image combinations. It can also be a time consuming process so a certain degree of patience is required. There are some notes on flashing here that should help pinpoint the problem. Unfortunately there is always a chance that even if you have things set up correctly and it won't work first time - so try again.
Any hardware control operation that requires USB will require the permissions to be set appropriately.
e.g. By following these instructions for flashing you can avoid root access for the Flasher and all the dependent modules (Conductor and Worker)
You might have an error such as this:
ProtocolError: <ProtocolError for localhost/xmlrpc/: 500 Internal Server Error>
Is your using Apache is it set-up properly? - Check the apache logs, your apache2.conf file and DJANGO_SETTINGS_MODULE.
The HTTPLogger instructions give instructions on server configurations
Not forgetting to restart Apache if there are any changes.
sudo /etc/init.d/apache2 restart