d trying it again
<zyga-suse> thank you
<jdstrand> mvo: you said this is part of spread. what test?
<pstolowski> zyga-suse, I can make the Mock* method from tests call the one from builtin, so we get rid of duplicated body, a little win..
<mvo> jdstrand: its a new spread test I'm currently working on. we got a report from CE QA about this issue
<jdstrand> I see a test for that file in  tests/main/snap-discard-ns, but that wouldn't be confined since calling snap-discard-ns directly...
<pstolowski> but not the other way around
<zyga-suse> pstolowski: yeah, that's good
<zyga-suse> pstolowski: little by little :)
<mvo> jdstrand: and we have no test yet that checks snap refresh stable->edge and revert back
<pstolowski> ok..
<mvo> jdstrand: fwiw, stable kernel shows the same message
<jdstrand> mvo: how can I reproduce?
<jdstrand> mvo: do you have a branch somewhere?
<jdstrand> mvo: what is it that you are reverting btw?
<mvo> jdstrand: I reverted core
 * jdstrand wonders if it is a timing issue
<mvo> jdstrand: one sec, I'm writing a mail and will CC you
<jdstrand> eg, if the policy gets updated but the snap-confine binary does not...
<jdstrand> (eg, as part of the revert)
<mup> PR snapd#4058 opened: interfaces: reduce duplicated code in interface tests mocks <Created by stolowski> <https://github.com/snapcore/snapd/pull/4058>
<jdstrand> fwiw, I would be surprised if there is a bug in apparmor for file mediation. I am not saying it isn't possible, but I would expect we would see a ton more issues if there was
<pstolowski> zyga-suse, ^
<zyga-suse> jdstrand: yes, it's a bit mysterious why this happens
<zyga-suse> jdstrand: remember when we once saw a case of apparmor profile staying stale after being loaded?
<zyga-suse> mvo: is this reproducible or did you just get it once and didn't try again?
<jdstrand> if it happens as a result of reverting core, I suspect we are loading the policy from the reverted core but using the snap-confine binary from the unreverted core, or something similar
<zyga-suse> pstolowski: +1
<zyga-su