<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/tests/chutney/test, branch arti-v1.8.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.8.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.8.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-10-09T16:17:59Z</updated>
<entry>
<title>chutney ci: make arti-bench bin configurable</title>
<updated>2025-10-09T16:17:59Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2025-10-08T21:26:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ff6c714846b987e6e6409880eb665c0093deb54a'/>
<id>urn:sha1:ff6c714846b987e6e6409880eb665c0093deb54a</id>
<content type='text'>
Also search several candidate paths.
</content>
</entry>
<entry>
<title>chutney CI: store and use jq path</title>
<updated>2025-09-29T16:22:19Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2025-09-10T20:02:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=df531a543d240e1a765c65651b7cabf1a082b04b'/>
<id>urn:sha1:df531a543d240e1a765c65651b7cabf1a082b04b</id>
<content type='text'>
Since we're validating the presence of jq, we might as well handle it
consistently with the other dependencies and provide a way to specify
where it is.
</content>
</entry>
<entry>
<title>chutney ci: remove CHUTNEY_BIN env variable</title>
<updated>2025-09-29T16:22:19Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2025-09-09T18:12:11Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=353e79c5d65547135a8de71edfe50954f6f6b4b0'/>
<id>urn:sha1:353e79c5d65547135a8de71edfe50954f6f6b4b0</id>
<content type='text'>
This wasn't a pre-existing environment variable, and now it can be set
via command-line if it needs to be overridden. I don't see much reason
to use an environment variable here.
</content>
</entry>
<entry>
<title>chutney CI: move benchmark from e2e script to `test` script</title>
<updated>2025-09-29T16:22:19Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2025-09-08T19:43:53Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b33e821c8771ac3ef4cf4378f9af04c259fc3e2a'/>
<id>urn:sha1:b33e821c8771ac3ef4cf4378f9af04c259fc3e2a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>chutney ci: move "chutney verify" test from `setup` to `test`</title>
<updated>2025-09-29T16:22:19Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2025-09-04T23:58:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=85328d9baf8fabf7a3c12ead0e92190098962285'/>
<id>urn:sha1:85328d9baf8fabf7a3c12ead0e92190098962285</id>
<content type='text'>
It made sense to have this as part of the setup when the chutney network
itself didn't include arti; i.e. this used to be just validating the
non-chutney tor network before adding chutney nodes.

Now that the chutney network natively includes arti nodes, `chutney
verify` is testing those nodes; i.e., testing arti.
</content>
</entry>
<entry>
<title>chutney ci test: use chutney net's arti client</title>
<updated>2025-06-05T16:14:12Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2025-05-21T19:11:05Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0a8f804e114bec524ecf9a0f79c6868e000e7118'/>
<id>urn:sha1:0a8f804e114bec524ecf9a0f79c6868e000e7118</id>
<content type='text'>
</content>
</entry>
<entry>
<title>chutney dns test: handle multiple addresses</title>
<updated>2025-06-05T16:14:12Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2025-05-21T22:46:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b2a8cc6773eb4f347e9ffc55d47d0f1f523ea431'/>
<id>urn:sha1:b2a8cc6773eb4f347e9ffc55d47d0f1f523ea431</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add `tests/chutney/integration-e2e-shadow`</title>
<updated>2024-09-18T18:26:07Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2024-09-17T15:59:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bedff22e46a34031a5c25088f1fbecd8554d117b'/>
<id>urn:sha1:bedff22e46a34031a5c25088f1fbecd8554d117b</id>
<content type='text'>
This is a wrapper script for running `tests/chutney/integration-e2e`
under shadow.
</content>
</entry>
<entry>
<title>chutney test: add option to skip tests incompatible with shadow</title>
<updated>2024-09-18T18:26:07Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2024-09-16T18:12:10Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=33e92d6d2300219117b2ccc205ebfa1c50327ac8'/>
<id>urn:sha1:33e92d6d2300219117b2ccc205ebfa1c50327ac8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>chutney: don't hard-code expected IP address for example.com</title>
<updated>2024-09-18T18:26:07Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2024-09-16T17:23:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=745cb3054b188ff752e3dd2a7a94914148f303ac'/>
<id>urn:sha1:745cb3054b188ff752e3dd2a7a94914148f303ac</id>
<content type='text'>
It looks like it changed at some point. Rather than hard-coding,
just do the lookup locally and compare the tor-lookup result against
that.
</content>
</entry>
</feed>
