Browse files

Merge pull request #366 from Bastian-Krause/bst/doc

doc: fixes and improvements
  • Loading branch information...
jluebbe committed Nov 27, 2018
2 parents f248a7b + cbaa749 commit 045323112678514d1927732dd67925eb1a8764be
Showing with 18 additions and 11 deletions.
  1. +1 −11 doc/development.rst
  2. +17 −0 doc/usage.rst
@@ -391,7 +391,7 @@ the file on the remote host with the following pattern:
.. code-block:: bash
Additionally it provides `get_remote_path()` to retrieve the complete file path,
to easily employ it for driver implementations.
@@ -529,16 +529,6 @@ The inactive Driver could then cause a preemption and would be activated.
The current caller of the originally active driver would be notified via an
File Transfer to Exporters
Currently, the exporter and client expect to have a shared filesystem (see for
example how the :any:`AndroidFastbootDriver` works when accessing a
:any:`NetworkAndroidFastboot` resource).
To remove this limitation, we should have a common way to make files available
to the exporter, possibly by generating a hash locally and rsyncing new files to
the exporter.
Remote Target Reservation
@@ -128,6 +128,23 @@ The pytest plugin also supports the verbosity argument of pytest:
This allows debugging during the writing of tests and inspection during test runs.
Other labgrid-related pytest plugin options are:
``--lg-env=LG_ENV`` (was ``--env-config=ENV_CONFIG``)
Specify a labgrid environment config file.
This is equivalent to labgrid-client's ``-c``/``--config``.
Specify labgrid coordinator websocket URL.
Defaults to ``ws://``.
This is equivalent to labgrid-client's ``-x``/``--crossbar``.
``--lg-log=[path to logfiles]``
Path to store console log file.
If option is specified without path the current working directory is used.
``pytest --help`` shows these options in a separate *labgrid* section.
Simple Example

0 comments on commit 0453231

Please sign in to comment.