<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/tests/chutney/integration-e2e, branch arti-v1.2.8</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.8</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.8'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2024-09-18T18:26:07Z</updated>
<entry>
<title>chutney test: rework installation and tracking of chutney itself</title>
<updated>2024-09-18T18:26:07Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2024-09-17T15:51:06Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2ca52e2cc246efd77ab96b85262edc2b3afc23aa'/>
<id>urn:sha1:2ca52e2cc246efd77ab96b85262edc2b3afc23aa</id>
<content type='text'>
Previously `tests/chutney/setup` would locate *or install* chutney and
set `CHUTNEY_PATH` for itself. However that `CHUTNEY_PATH` wasn't
propagated to other steps or "up" to the new `integration-e2e` wrapper
script.

Tracking it in the arti.run along with other dynamic info lets us ensure
we consistently use the same chutney across steps, and in the higher
level `integration-e2e` script.
</content>
</entry>
<entry>
<title>chutney test: move logic from .gitlab-ci.yml to integration-e2e</title>
<updated>2024-09-18T18:26:07Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2024-09-16T17:21:39Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=da244737c11d618983d1c9539258d0255bcf1aca'/>
<id>urn:sha1:da244737c11d618983d1c9539258d0255bcf1aca</id>
<content type='text'>
Having this in a script is a step towards being able to run exactly the
same test under shadow without duplicating this high-level logic.

It's also convenient for running the ci test locally.
</content>
</entry>
</feed>
