Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T16:16:26Zhttps://gitlab.torproject.org/legacy/trac/-/issues/33167Test changes in descriptors2020-06-13T16:16:26ZjugaTest changes in descriptorsWorking on #30733 asn pointed out that there're no tests to check the changes in descriptors.
It'll be easier to create these tests when:
- sbws can use chutney (#33150) so that the test network lives longer than the 1st consensus
- `R...Working on #30733 asn pointed out that there're no tests to check the changes in descriptors.
It'll be easier to create these tests when:
- sbws can use chutney (#33150) so that the test network lives longer than the 1st consensus
- `RelayList` can be initialized with different consensus/descriptors and not only a controller (#29717)
- have an external tool that check the generated bandwidth files in the Tor network and detects changes in the descriptors (#33152)
Maybe we should include this ticket as part of #33121sbws: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/33166Test tor dormant mode2020-06-13T16:16:26ZjugaTest tor dormant modeWorking on #30733 asn pointed out to check the dormant mode.
Dormant mode was introduced in tor 0.4.0.4-rc.
As teor suggested, we should check whether sbws stop trying to make circuits, and therefore become dormant, when:
- the network...Working on #30733 asn pointed out to check the dormant mode.
Dormant mode was introduced in tor 0.4.0.4-rc.
As teor suggested, we should check whether sbws stop trying to make circuits, and therefore become dormant, when:
- the network goes down (it probably just stops and prints a traceback, as happened in #32939)
- tor doesn't have a recent consensus or descriptors
We also should check what happen when sbws starts with tor in dormant mode and probably set `DormantCanceledByStartup 1` until we fix bugs.
Maybe we should include this ticket as part of #33121.sbws: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/33150Allow to connect to an external control port2020-06-13T16:16:25ZjugaAllow to connect to an external control portTo be able to run integration tests with chutney.To be able to run integration tests with chutney.sbws: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/30902Stop comparing file_created key in test2020-06-13T16:16:13ZjugaStop comparing file_created key in testIn concrete tests/unit/lib/v3bwfile.py::test_from_results_read.
Because some times it files with the second: https://travis-ci.org/juga0/sbws/jobs/546378459#L1339.In concrete tests/unit/lib/v3bwfile.py::test_from_results_read.
Because some times it files with the second: https://travis-ci.org/juga0/sbws/jobs/546378459#L1339.sbws: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/29727Check output of generate in the integration tests2020-06-13T16:15:41ZjugaCheck output of generate in the integration testsIt was included `sbws scanner` in the tests, but `generate` could also be included and check that the files generated contain expectected Keys and Values.
These files could also replace many of the tests input examples and change them a...It was included `sbws scanner` in the tests, but `generate` could also be included and check that the files generated contain expectected Keys and Values.
These files could also replace many of the tests input examples and change them as part of #28684sbws: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/29358Stop overloading the CPU when the test network is run in the integration tests2020-06-13T16:15:29ZjugaStop overloading the CPU when the test network is run in the integration testsIt might be caused by the test network relays' configuration.
In the case it's not possible to do not possible to overload the CPU, it's still possible to simplify the relays' configuration.It might be caused by the test network relays' configuration.
In the case it's not possible to do not possible to overload the CPU, it's still possible to simplify the relays' configuration.sbws: 1.2.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/28774Stop the integration tests http server when the tests end2020-06-13T16:15:08ZjugaStop the integration tests http server when the tests endThe integration tests launch an HTTP server (tox.ini), but it is not stop after tests finish.
This affect the developer running the integration tests, not the operator.The integration tests launch an HTTP server (tox.ini), but it is not stop after tests finish.
This affect the developer running the integration tests, not the operator.sbws: unspecifiedjugajugahttps://gitlab.torproject.org/legacy/trac/-/issues/27361Tests that launch sbws in a subprocess2020-06-13T16:13:50ZpastlyTests that launch sbws in a subprocessThat way we exercise all the startup code.That way we exercise all the startup code.sbws: unspecified