ci: fix flaky dns-systemd test by waiting a second before running

[jamilbk]

It appears that occasionally the test runs before DNS sentinel is applied and/or Resources updated.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
firezone	⬜️ Ignored (Inspect)	Visit Preview		May 12, 2024 4:12pm

[github-actions]

Terraform Cloud Plan Output

Plan: 15 to add, 15 to change, 15 to destroy.

Terraform Cloud Plan

[github-actions]

Performance Test Results

TCP

Test Name	Received/s	Sent/s	Retransmits
direct-tcp-client2server	241.0 MiB (+1%)	243.3 MiB (+2%)	189 (+22%)
direct-tcp-server2client	243.5 MiB (+1%)	244.9 MiB (+1%)	270 (+18%)
relayed-tcp-client2server	227.2 MiB (+2%)	228.0 MiB (+2%)	200 (-19%)
relayed-tcp-server2client	238.1 MiB (+1%)	238.7 MiB (+1%)	344 (+7%)

UDP

Test Name	Total/s	Jitter	Lost
direct-udp-client2server	500.0 MiB (-0%)	0.03ms (-28%)	44.08% (+9%)
direct-udp-server2client	500.0 MiB (-0%)	0.02ms (+182%)	22.77% (+5%)
relayed-udp-client2server	500.0 MiB (+0%)	0.04ms (+22%)	57.37% (+3%)
relayed-udp-server2client	500.0 MiB (+0%)	0.04ms (-1%)	41.89% (+1%)

[ReactorScram]

LGTM. I wonder why, though. If we notify systemd after we've set up the interface and everything, you'd think all other threads on the system should see the interface as set up.

[jamilbk]

LGTM. I wonder why, though. If we notify systemd after we've set up the interface and everything, you'd think all other threads on the system should see the interface as set up.

Maybe it's before the Resource is added? Though I thought that happened in the init message.