Hi intrigeri, On 25-05-2020 11:18, intrigeri wrote: > Thanks for letting me know — sorry for the delay in answering. No problem. > I don't really have a clue at this stage. Ack. > My approach would be to first figure out which one, among the 2 tests > (compile-policy and test-installed), is causing the breakage. > And if the problem lies in compile-policy, I'd like to check > if the problem comes from a specific Depends of that test. > > Ideally I would do that without doing uploads to sid merely for > bisection purposes. I'm willing to do test uploads to experimental. Right. > In the debci self-service interface, it seems I could force debci to > install all packages built from src:apparmor from experimental, > which looks like what I need. > > Now, to run those tests, I would need apparmor to be temporarily > removed from the blacklist, and some coordination so that a ci.d.n > maintainer can clean up whatever mess the tests create while the > package is temporarily un-blacklisted. With the coordination already required, you can just upload to experimental and I/we can schedule the test if you ping us. > I would be happy to book some time to work on this in > a coordinated manner. Great. > Does this approach make sense to you? The most obvious alternative is that your run it locally, but I guess you tried and couldn't reproduce? > Is there a better way for me to investigate? We have given DD's temporarily access to one of our workers before. If you're interested we could do that again for this case. That way you could even skip the upload to experimental, assuming it reproduces if run from a local tree. And you can check what's going on in the test bed. Paul
Attachment:
signature.asc
Description: OpenPGP digital signature