You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One other thing I thought of is that ubuntu-slim imposes a hard 15-minute job limit and one CPU on every caller and so I'm wondering if it would be worth it to add a string runner input defaulting to the current default runners (ubuntu-latest/ubuntu-latest), and use runs-on: ${{ inputs.runner }} to change from the default. Just a thought.
Yeah... I noticed that in the docs and don't agree with the disparity (single cpu => 15 minutes, anything else => 6 hours), but rules are rules I suppose.
I'll make it parameterized as requested. Should I add any warnings? I've always been of the mindset that unit tests should only take a few minutes, while integration + e2e tests go for any sane number of hours.
Activity
feat: add runner input to long-running jobs (closes #42)