when any of the commands fail.

and adapt the tests to pass.
\o/

Closes: #40008.

and scripts to run the integration tests with chutney.
It does not replace yet the way integration tests are run.

After refactoring and making clear when we were using exit(s) that can
exit to all public IPs (and a port) or only some, refactor them
removing the duplicated code and adding the `strict` argument.

When the relay is not an exit, instead of choosing exits that can
exit to all IPs, try with exits that can exit to some IPs, since the
relay will be measured again with a different exit in other loop.

When the relay is an exit, instead of ensuring it can exit all IPs, try
using it as exit if it can exit to some IPs.
If it fails connecting to the Web server, then try a 2nd time using it
as entry to avoid that it will fail in all loops if there is only one
Web server, cause it will be used again as an exit.

Also, the helper exits don't need to be able to exit all IPs. When a
helper exit fails to exit (maybe cause it can not exit to the Web
sever IP), it's not a problem cause in a next loop other exit will be
choosen.

This change of logic also solves the bug where non exits were being
used as exits, because we were trying to measure again a relay that
was used as entry, because it could not exit all IPs, which includes
also the non exits.

Closes: #40041.

see previous commit

as this might cause many circuit errors.
They're already added to the generator.
Also adapt the number in test_init_relays.

Closes: #40037.

Happy solstice! :)

Move initialization via existing socket to this new function and start
tor only when it fails.

Closes: #33150.

because it stores a timestamp for each attempt, which makes state.dat
grow thousand of lines (json).

Closes #40023, #40020

at the beginning of the line and in empty lines. They are not needed.

and measurement attempts from all the results.
Until they get properly updated.

Also change dates in tests, so that timestamps are counted correctly

Closes: #34309.

because they expired.
They will expire again in a year.
Implementing #33150 and using chutney would avoid to update keys.

Closes #34394.

instead of bw before scaling.

Tests have finally correct value.
For 1 result, only when the cap is 1, the value will be equal to the
rounded bw because the cap does not limit it.

Make tests pass because the high limit change the expected values,
but the final value still needs to be fixed.

Make test pass, though the value is not correct since it needs to be
rounded after clipping

Take either the consenus bandwidth or the descriptor bandwidth if
one of them is missing, do not scale when both are missing and
ignore descriptor average and burst when they are missing.

for each relay, calculate the filtered mean for all relays and
calculate the filtered ratio for each relay.

When using `_relays_with_flags()` and similar methods it's possible
that tests start to hang without time freezing. See bug 33748 for more
details. We work around this by providing the necessary `freeze_time()`
calls meanwhile.

and not a list of timestamps.

Added:
- library to check whether the KeyValues make sense
- test an example bandwidth file
- a command to check an arbitrary bandwidth file

Finally, doing something with all these KeyValues!

(Quarantine day 7th)

Test that the results, state and bandwidth file generated by running
the scanner and the generator in the test network are correct.

in ResultDump and incrementing relay's monitoring KeyValues.

monitoring KeyValues.

using timestamps class.

Additionally:

- fix: relayprioritizer: Replace call relay priority

- fix: scanner: Replace call relay measurement attempt

using timestamps class.
Also add one more result to the tests data and change the
test accordingly.

in RelayPrioritizer:
- Rename recent_priority_list_count to recent_priority_list when
  there is no counting
- Rename recent_priority_relay_count to recent_priority_relay
  when there is no counting
- Use the timestamps class to manage/count priority lists/relays

in RelayList:
- Rename recent_measurement_attempt_count to recent_measurement_attempt when
  there is no counting
- Use the timestamps class to manage/count measurement attempts

in RelayList:
- Rename consensus_timestamps to recent_consensus
- Rename recent_consensus_count to recent_consensus when there is
  no counting
- Use the timestamps class to manage/count consensuses
- Remove method not needed anymore

to be able to serialize/deserailize datetime in the state file.

Since state uses json and json will raise an error when it can't
decode/encode some datatype.

Test that two different instances of state don't overwrite each other.
This test don't past in this commit, will pass in the next bugfix.

Bugfix v0.7.0, which claimed 100% test coverage on state.