<feed xmlns='http://www.w3.org/2005/Atom'>
<title>archsetup/tests/network-diagnostics, branch main</title>
<subtitle>Builds a full dev workstation from a bare Arch Linux install.
</subtitle>
<id>https://git.cjennings.net/archsetup/atom?h=main</id>
<link rel='self' href='https://git.cjennings.net/archsetup/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/archsetup/'/>
<updated>2026-07-04T21:23:57+00:00</updated>
<entry>
<title>test(vm): collect network evidence before failing in pre-flight diagnostics</title>
<updated>2026-07-04T21:23:57+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-07-04T21:23:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/archsetup/commit/?id=f8cb4cd1562aceef39f45e33951143c1c1a95b16'/>
<id>urn:sha1:f8cb4cd1562aceef39f45e33951143c1c1a95b16</id>
<content type='text'>
run_network_diagnostics tested HTTP before DNS and returned on the first failure, so a DNS failure surfaced as a generic "no internet" and the IP/route/resolver evidence was never reached. It now collects read-only facts first (ip -brief addr, default route, resolv.conf) and prints them regardless of outcome, runs every check, and reports all failures together in a summary. Generic checks (DNS, egress, TLS) are split from Arch-specific ones (mirror, AUR) so a DNS failure is named as DNS, not a mirror problem. Raw fact output is saved to the results dir when one is set.
</content>
</entry>
</feed>
