On 20/09/25 18:14, Fabian Grünbichler wrote:
no, I am open to suggestions here. for example, running the dh_auto_test `cargo build/test` and/or the default features autopkgtest with a custom profile (basically dev/test + optimizations) might be a sensible compromise? that should catch most optimization-related issues, while still keeping (test) compilation times down..
If we did this and furthermore enabled dev + opt tests for application packages (which are libraries' end-users and might enable non-default features) we would be in an even better position.