<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/tests/chutney/network.py, branch main</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=main</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=main'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2026-06-16T04:06:03Z</updated>
<entry>
<title>chutney test network: add 4 suitable middle/guard/vg relays</title>
<updated>2026-06-16T04:06:03Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2026-06-16T03:25:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a76a41b5b5ac822b818c763104015306542fabfc'/>
<id>urn:sha1:a76a41b5b5ac822b818c763104015306542fabfc</id>
<content type='text'>
With the chutney bump in the previous commit alone, we hit arti#2463
consistently.

According to the spec, a hidden service using vanguards-lite needs 2
guards and 4 vanguards
&lt;https://spec.torproject.org/vanguards-spec/index.html&gt;.

All 6 of those relays need to be Fast and Stable.

At least the 2 guards also need to be Measured. (Probably the 4
vanguards too, but I haven't verified).

authority relays are never considered Measured. Prior to the chutney
bump, none of the relays were, but since chutney!142, we create a
bandwidth file to ensure the non-authorities *are* Measured, and will
get the Fast flag. (IIUC, tor doesn't apply the bandwidth measurements
to authorities). Maybe the presence of *some* measured relays gets us
out of some fallback path that was getting used before to allow
unmeasured relays?

Adding the additional relays seems to fix the issue.
</content>
</entry>
<entry>
<title>chutney CI: add hidden services</title>
<updated>2026-04-02T20:30:46Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2026-03-23T22:34:17Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=03cb8fc97db7caa5e181a6f7bcce612b87cb94aa'/>
<id>urn:sha1:03cb8fc97db7caa5e181a6f7bcce612b87cb94aa</id>
<content type='text'>
</content>
</entry>
<entry>
<title>chutney test: include arti-extra bin</title>
<updated>2026-03-11T19:33:42Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2026-03-11T15:05:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=83f1d188a229b74ea7fc79b24afeaf38b225aa54'/>
<id>urn:sha1:83f1d188a229b74ea7fc79b24afeaf38b225aa54</id>
<content type='text'>
Test the arti-extra bin, which includes most of `full` and
`experimental` features, too.
</content>
</entry>
<entry>
<title>network.py: break up construction of configs list</title>
<updated>2026-03-11T19:29:26Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2026-03-11T18:52:17Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d2ac8061937600d470b02f932d0e9af96d004e58'/>
<id>urn:sha1:d2ac8061937600d470b02f932d0e9af96d004e58</id>
<content type='text'>
</content>
</entry>
<entry>
<title>chutney ci: convert chutney-script to a normal python module</title>
<updated>2026-03-11T19:29:22Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2026-03-11T18:39:22Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=482f8451b749620ed4d92bac61dacc9bfd624b05'/>
<id>urn:sha1:482f8451b749620ed4d92bac61dacc9bfd624b05</id>
<content type='text'>
This will give us a bit more flexibility, e.g. to pass additional
arguments.

Now that the python linters understand it, we fix some linting issues.

We preserve the ability to run the test on other networks by making the
Config.network optional. The new default of `None` means to use the
built-in module to create the network.

The functionality of the test itself is the same.
</content>
</entry>
</feed>
