[WireGuard] continuous integration/testing across multiple kernels

Daniel Kahn Gillmor dkg at fifthhorseman.net
Sat Jul 2 20:55:43 CEST 2016

hey all--

debian has a continuous integration testing infrastructure that runs
"autopkgtest" instructions from the unstable distribution on at least
two different architectures (amd64 and arm64 today, maybe more in the


I think it's possible for these tests to make use of full network
access, kernel modifications, and superuser privileges, which means we
should be able to test wireguard against public test servers on
different kernels and from different networks, if that's OK with
whoever's running the test servers.

I'd be happy to write a simple test and include it with the debian
packaging, so that if/when we put the package in unstable it should get
run on ci.debian.net automatically.

Is it ok to create such a test script that invokes, say,
contrib/client-server-example/client.sh from an automated platform?  Are
there other automated tests that would be useful?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 948 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/wireguard/attachments/20160702/68cb5b16/attachment.asc>

More information about the WireGuard mailing list