Change log level from warn1 to debug1 for K8s Job Pod Warnings#6523
Merged
pditommaso merged 1 commit intonextflow-io:masterfrom Nov 4, 2025
Merged
Change log level from warn1 to debug1 for K8s Job Pod Warnings#6523pditommaso merged 1 commit intonextflow-io:masterfrom
pditommaso merged 1 commit intonextflow-io:masterfrom
Conversation
Signed-off-by: Sam W <s.a.j.wilkinson@bham.ac.uk>
✅ Deploy Preview for nextflow-docs-staging canceled.
|
pditommaso
approved these changes
Nov 4, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #6331
Currently the K8S executor spams stdout when jobs don't have a pod yet, this is a perfectly normal state of affairs in most cases and just means you don't have enough CPUs / memory available currently, suggest muting this by default!
One issue I could see this causing would be that it may be more difficult for users to detect when there's a real reason the pod hasn't been created e.g. an invalid container string, may be worth adding specific handling for this.