mirrors/arti.git/tests/shadow, branch arti-v2.4.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.4.02026-04-21T17:51:48ZCI: Disble shadow cpu-pinning2026-04-21T17:51:48ZJim Newsomejnewsome@torproject.org2026-04-21T17:51:48Zurn:sha1:1b3337730e4f87100b46521b211a7a6a2c7cc506
In CI, shadow's default behavior of pinning to CPU cores can result in
multiple instances of shadow fighting over the same CPU cores instead of
using idle ones.
integration-shadow: remove torrc parameter tuning2026-04-08T22:15:49ZJim Newsomejnewsome@torproject.org2026-04-08T22:15:49Zurn:sha1:36ceb7a3e4577683ed1bc680f07c9d2b96691f61
These were originally blindly copied over from shadow's own integration
test.
The relatively low BandwidthRate and BandwidthBurst rates in particular
could cause overload in heavily-used relays given the amount of traffic
we're trying to push through the network simultaneously from different
clients.
I'm not aware of a specific problem the other parameters might cause,
but it seems better not to have them without some concrete reason.
Motivated while debugging arti#2399; we hypothesize that the bandwidth
limits + bad luck of many circuits trying to use one relay at once could
be a contributing factor.
shadow ci: keep going after first failure2026-03-11T15:00:39ZJim Newsomejnewsome@torproject.org2026-03-11T15:00:39Zurn:sha1:523c67eec5e8450cc579e5298775d7958bb63ade
It can be useful to see the outcome of the other tests/analysis.
shadow CI: disable stallouts for onion clients2025-12-08T22:36:41ZJim Newsomejnewsome@torproject.org2025-12-08T22:36:41Zurn:sha1:b7dbc6dbc1b3e1bf918ad4c0cadc989a54fe3195
tgen aborts a stream and starts the next one when the "stallout" timeout
is reached. In some cases the arti (or tor) client just needs a bit more
time to establish a connection to the hidden service.
A potential downside is that if a single stream "stalls" forever without
an explicit error, tgen will never give up on it, and thus never try any
more streams. We can worry about that if and when we see it though; and
it would indicate a likely bug since the known clients and servers in
this test shouldn't stall indefinitely in this way.
shadow CI: *increase* required success rate for c-tor client2025-12-02T15:03:31ZJim Newsomejnewsome@torproject.org2025-12-01T19:12:46Zurn:sha1:a7a8c62f5f48a65f28fc7e561a4e20ecdf855f32
None of the failures currently recorded in
https://gitlab.torproject.org/tpo/core/arti/-/issues/2209 involve the
c-tor client. I think we can safely require all xfers to succeed for the
c-tor client.
shadow CI: reduce arti client HS required successes2025-12-02T15:03:31ZJim Newsomejnewsome@torproject.org2025-12-01T19:05:19Zurn:sha1:33c127cabd399ec49e5504f4f825692c3fc3b50f
From 9/10 to 5/10.
This is to mitigate flakiness.
See
https://gitlab.torproject.org/tpo/core/arti/-/issues/2209#note_3295789
ci: Improve formatting of shadow results.2025-11-25T23:31:04ZWesley Aptekar-Casselsme@wesleyac.com2025-11-25T23:31:04Zurn:sha1:918cbeba2d9fe335af68e6b6cf9006c465c3b10c
Having this all on one line makes it easier to read.
ci: Print host names in shadow run script.2025-11-25T23:25:54ZWesley Aptekar-Casselsme@wesleyac.com2025-11-25T23:25:54Zurn:sha1:59c0ac967c3db3f70902bbd14b12c182d8bc08e7
Now that we no longer echo these, this is useful.
ci: Print seed in shadow run script.2025-11-25T23:24:33ZWesley Aptekar-Casselsme@wesleyac.com2025-11-25T23:24:33Zurn:sha1:4536052c9ed3f70aec16568cee319a3b3de2b7e3
Now that we no longer echo this, it's potentially useful to have it.
ci: Disable echoing in shadow test script.2025-11-25T23:02:16ZWesley Aptekar-Casselsme@wesleyac.com2025-11-25T23:02:16Zurn:sha1:0047d724a75cc97da00489b3c3fb2ef6c7c6a1ea
I find that the echoing here does not really contribute to my
understanding of what's going on, and it makes the output quite
difficult to parse.