This will allow to improve tests also in beat/beat.cmdline>

Samuel GAIST authored Mar 11, 2020 and Flavio TARSETTI committed Mar 11, 2020

Update all logger.warn calls to logger.warning as warn is obsolete.

Also removes all unused logger instances.

The max length matches the one from the database of beat/beat.web>

The processing nodes are not on Python 3.6 yet
therefore these can not be used.

The other uses are only related to tests and
tasks not done on the processing nodes.

Some execution environments may run CPU as well as GPU
code, this check for Nvidia driver presence will allow
to reuse the same environment on both.

It also updates the GPU option to use the latest version
provided by the nvidia-docker2 documentation.

This avoids accidental writes in the container that
will be lost anyway.

When starting a docker container, use the same user as the one
currently executing the code if nothing else has been put in
the configuration. This allows to have consistent access across
executions.

Samuel GAIST authored Feb 20, 2020 and Samuel GAIST committed Feb 20, 2020

Support giving a custom mount point to use for volume setup.

This will replace the cache path when creating the volumes.

It was not matching the one created by the original discovery
and thus fails to find the environments for the tests.

This will only mount what is needed by the various containers.

Relates to beat.backend.python#30

IF docker is installed or the daemon not accessible, the exception
propagation will not follow the raise on error property. This patch
fixes that and thus keeps the behaviour consistant.

This will show information similar to the describe based
implementation.

Samuel GAIST authored Jan 17, 2020 and Samuel GAIST committed Jan 17, 2020

The next release of BEAT environments will make use of docker
labels to provide the information the current describe command
returns (minus the os entry which is not currently used).

This new implementation of discovery uses these labels and thus
speeds up the process.

The original code is kept as a fallback method in case a node only
has images using the old build process.

The blocks entry covers them as it already covers both
the blocks and analysers. Therefore there's no need for
an additional property here.

Rather than blindingly selecting the first protocol template
found, look for the first valid one.

That will make them re-usable in other tests like
in beat/beat.cmdline>

This test tends to fail on macOS with Python3.7

It is however unclear why as the test passes most
of the time. Especially in the other CI environments.

This patch implements a new parameter that allows to pass
the path to the python executable of the environment one
would like to use to execute an experiment. The various
beat/beat.backend.python from that environment will be
called in place of the current environment as it is
by default.

Fixes #90

Following beat.backend.python!61 the method has
now a third argument containing the output currently
written to on the processor side.

Currently, when an error occurred in one of the scripts, it
could just hang or the error itself wasn't properly processed.

This patch improves exception handling as well as error
message returned.

Like this the test passes but is known to trigger
the issue described in beat.backend.python#26
and fixed by beat.backend.python!59.

This makes the validate part more coherent.