The abstractproperty is deprecaterd since Python 3.3.

This tests commonly fails because syslog-ng takes its time to create the
/var/log/messages file even when it is already running. Moving it does
not ensure that it is run later on but at least that is what happens
right now.

The FDLogging uses poll to propagate data from one feed to the other.
This is not limited to only two file descriptors but technically any
number of them. Thus it is way more efficient to simply add new feeds to
existing thread over spawning the new one.

This improves cli handling in a wide variety of ways. Let's point one at
a time.

Change how we match sent command to not have issue with line break
caused limited number of columns. Now it simply expects new line and
return characters while it looks for characters from command. This makes
it possible to remove hack to increase number of columns in Shell.

The initial prompts in Shell were sanitized a little bit and commented.
The "weird" prompt it turns out is caused by TERM variable and remote
shell trying to control local terminal. One solution would be to set
different TERM but that complicates mterm usage while debugging. The
alternative and used option is to simply simplify regular expression to
not have problem with it. With exception of Busybox's default prompt
they are specific enough without having to match also new line.

For the same reason as in previous paragraph the nsfarm prompt was also
simplified. It now matches new lines only optionally. The reason is also
that not every program terminates with new line at the end and so it is
completely possible and valid that prompt is displayed at the end of
line not at the beginning. The "nsfprompt" is also specific enough word
that should not be anywhere else that we can rely only on it when we
look for our prompt.

This also fixes txt_write and bin_write as sendeof does work only on
pexpect instance but not on fdexpect. The more correct and used option
here is our own ctrl_d function that only signals EOF without actually
closing stdin.

The txt_read and bin_read methods gets option to not fail if file does
not exist. The txt_write method also got option to append instead of
overwrite.

The logging was improved by implementing our own code that splits lines.
The splitlines method is little bit too aggressive with splitting as it
expects pretty reasonable new lines consistency usage with standards.
The issue here is that for example '\r' that moves cursor to the left
can be spawned multiple times and has no effect and in some cases that
is what happens. The combination '\r\r\n' should be only one line not
two as detected by splitlines. The code we now use detects combination
of any number of '\r' and single '\n' as a one line split. It also
handles only '\r' as that is commonly used to overwrite existing line so
we consider it as new line as well. There is still a room for
improvements such as support for backspace and other control characters.

This makes this script support Mox as well as it reduces unnecessary
spam it creates in logs.

This sorts all includes in nsfarm project.

We want to make sure that we adhere to black formating and just also
sorted imports are reasonable request.

Jan Miksik authored 3 years ago and Karel Koci committed 3 years ago

Black is now the coding standard for Python projects in Turris. The only
exception over default is 120 columns limit.

nsfarm/lxd/utils: fix PermissionError on container clean

See merge request !37

The user might not have ability to send signal to that process but we
only check if process exists (is running) and not having ability means
that process is running.

Removed LXDConnection and refactored.
Connection replaced wit pylxd.Client()
and variables and logging moved into
lxd.__init__

Karel Koci authored 3 years ago and Jan Miksik committed 3 years ago

Instead of having hardcoded amd64 in image files we now try to detect
architecture instead.

Use simplestream to obtain images now instead old method.

The `lxc exec` expects `--` before the command. It seems to work even
without it but it behaves weirdly in cases when application relies on
its name (that is argv[0] and example of such application is Busybox).

This allows you to specify name for container. This name is used only in
logs and if not specified the image name is used. This should
primarily be used when you spawn multiple containers from same image
side by side. Then specifying name allows easy recognition of different
containers in the logs.

The '-' is invalid so this replaces it with 'x'. For consistency this
also changes it in such a way that it is always appended so the hidden
issue like this won't happen again. It also makes the naming scheme
consistent.

This tests txt_write, txt_read, bin_write and bin_read Shell methods.

There were also few issues with it that were discovered during the
testing. For example calling prompt twice causes match of new prompt.
The output of txt_read was incosistent with text prepresentation in
Python.

The new feature here is ability of txt_write to append instead of
overwrite.

This was causing issue when tests from multiple packages were run in one
session as serial console is not correctly closed on cleanup of board
fixture.

These should be session anyway as they do not cause any conflict with
anything else (compare to boot_serial that boots and reboots the
router). There is no reason why we would want the new instances of these
objects, rather the opposite.

replaced nonexisting debug mark
the test is now skipped due to some incompatibility
that will be investigated.

Jan Betik authored 5 years ago and Karel Koci committed 3 years ago

Added pppoe tests and pppoe container
Be aware that isp-pppoe container requires mounted dev/ppp

Jan Miksik authored 3 years ago and Karel Koci committed 3 years ago

Added tests:
tests/network/test_dhcp.py:
    - ip limit
    - ip range
    - ip duplicity
    - leasetime

This improves cleanup to not only remove old images but also a stale
containers.

There are two types of containers nsfarm spawns. Those are bootstrap
and regular containers. The bootstrap containers are spawned with
intention to create image while regular containers are just spawned to
be later removed. The difference is that while regular containers are
always tied to one specific process (the instance of nsfarm) the
bootstrap is intentionally global to serialize multiple instances on
single image creation.
The cleanup algorithm can remove any regular container that's parent is
no longer running. The bootstrap containers do not contain info about
parent process and thus we use time to remove just old containers.

Warning: This changes the template for regular container name. The
change is needed for reliable PID parsing from template name. The
unclear state is when image would end with dash and number.

This converts argument identification from 'target0' to real name of
target.

This reverts commit 532183a7.

ESR is really old and it seems that issues in Firefox were removed in
the end.

These are simple "click trough" tests of reForis guide.

It only ensures that we can correctly pass through guide. The tests of
dialogues we are passing trough should be implemented.

The scope of session reaches not only tests but also selftests and in
general we want to keep those two separate thus these fixtures should be
limited by package they are defined in.

In some cases this is rather extension because for some reason for
example client_board was defined with module scope. The effect of that
was that client was been reconnected for every module. Making that for
whole package saves a little bit of time. The original idea was to make
sure that we are connected but if ever test plays with local network it
on teardown it has to restore original settings and thus it should make
original connection available again.

This covers some mising types specifiers.

The original use for lazy-fixtures was pretty much just to test if they
help us to solve organization issue but they did not. Now they are
unused and we do not plan to use them right now so they should not be
part of requirements.

This switches to stable Firefox. There are some issues with bleeding
edge Firefox and we should ensure that we work with stable version more
than with newest one.

This is just for better orientation in logs. The idea is that anything
with > or < is text while the rest are just regular messages from NSFarm.

We do not run tests on multiple boards at the same time and it is
technically undesirable in terms of how current tests are setup. That
makes inclusion of target name just a duplicate value as target is
stated in meta-data for tests and thus directly visible at the start
test report.

This makes it much faster and reduces the hack. It also makes this
setting independent on the Internet connection.

The issue here is that we should not use full path to file never to
calculate hash as different location of NSFarm project result in
different hashes and thus we do not share them at all.
This makes one instance where we included full path just relative to
images directory. This way the path should be contant no matter where
the project is located.

This also does small tweak in form of removal of unnecessary
comprehension error. We can convert directly to list without creating
generator.

The previous commit added shell property exactly for this. This now
tweaks code to use it.