Oliver Calder
Oliver Calder
Needs a spread test to check restart behavior. Can't check profile behavior yet because AppArmorPrompting is hard-coded as unsupported for now.
When running the new spread test with ```sh spread -v -repeat 10 qemu:ubuntu-22.04-64:tests/main/apparmor-prompting-flag-restart ``` I seem to consistently get a failure on the third repeat, after the `for value in...
Spread tests should pass at https://github.com/snapcore/snapd/pull/13822/commits/37fcb5d970f5370e499b7b2146636aae6b88bf02, but my attempt to integrate checking `start-limit-hit` when testing for a restart does not appear to be working.
The check for parser features tests $2^{|\text{parserFeatures}|}$, which means adding `prompt` to the checked parser features doubles the test runtime (to ~45s on my rather fast 13700H). I tried refactoring...
Note from last week about the slow test: we should refactor the test to not make $2^N$ checks, especially given this is exercising combinations of independent features on a fake...
Force pushed to rebase on master and clean up commit history. This should be rebased when merging rather than squash merged, as the changes to `sandbox/apparmor` don't just relate to...
Force pushed to rebase on master and squash the feature sorting commit into the main apparmor-related commit.
> @olivercalder Mmm... but why would the time in the server "go backwards" by such a big time? I mean: if you are talking about daylight saving, the timezone is...
This should be moved to the `interfaces/prompting` package, related to #13849 and #13850.