#noisy dagger-runner checks
1 messages · Page 1 of 1 (latest)
FWIW I think I know how to fix the failing test, but until there's time to fix that, I'd prefer that we find a way to have experimental checks be a bit less disruptive going forward
@proven parrot added them. I'll turn them off for now. I'm curious what the fix is. 🙂
A ha, thanks!
The fix is pretty hokey, it's because of the 256-char limit on search ... in /etc/resolv.conf. That particular infra starts with a larger set of search domains, so the test isn't able to nest as deeply as it could in other environments
I think the proper fix might be to just see what's initially in /etc/resolv.conf, see how long each additional domain is when nesting, and do 🪄 math 🪄 to figure out the effective nesting limit
Ah, gotcha. That makes sense.
@cedar crest https://github.com/dagger/dagger/pull/5692
What's confusing for me is this looks like a totally separate workflow, does this somehow modify the other ones to use these 3 workers? 
here's the one I'm mainly concerned with, AFAICT this should be test.yml
engine:test runs _hack_make.yml: https://github.com/dagger/dagger/blob/main/.github/workflows/test.yml#L21-L24
which has the three different jobs within it.
engine:
uses: ./.github/workflows/_hack_make.yml
with:
mage-targets: engine:test