#noisy dagger-runner checks

1 messages · Page 1 of 1 (latest)

cedar crest
#

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

sharp quiver
#

@proven parrot added them. I'll turn them off for now. I'm curious what the fix is. 🙂

cedar crest
#

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

sharp quiver
cedar crest
#

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? thinkies

#

here's the one I'm mainly concerned with, AFAICT this should be test.yml

sharp quiver
#
  engine:
    uses: ./.github/workflows/_hack_make.yml
    with:
      mage-targets: engine:test