Fusion GPU metrics collection#7022
Merged
Merged
Conversation
Signed-off-by: Paolo Di Tommaso <[email protected]>
Signed-off-by: Paolo Di Tommaso <[email protected]>
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> Signed-off-by: Paolo Di Tommaso <[email protected]>
✅ Deploy Preview for nextflow-docs-staging canceled.
|
cristianrcv
approved these changes
Apr 10, 2026
jorgee
approved these changes
Apr 10, 2026
bentsherman
approved these changes
Apr 10, 2026
Member
Author
|
Ok, adding the Plan and tasks (do not merge please) |
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> Signed-off-by: Paolo Di Tommaso <[email protected]>
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> Signed-off-by: Paolo Di Tommaso <[email protected]>
Add support for reading GPU metrics from Fusion .fusion/trace.json file on task completion. The gpu block is carried as a transient gpuMetrics field on TraceRecord (following the resourceAllocation pattern) and included in the task payload sent to Seqera Platform. - Add gpuMetrics transient field with getter/setter to TraceRecord - Add parseFusionTraceFile() to extract gpu block from trace JSON - Read .fusion/trace.json in TaskHandler.getTraceRecord(), gated by executor.isFusionEnabled() - Include gpuMetrics in TowerClient.makeTaskMap0() task payload - Add unit tests for TraceRecord and TowerClient Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> Signed-off-by: Paolo Di Tommaso <[email protected]>
- Use JsonSlurper.parse(Path) via SlurperEx instead of file.text + parseText - Add TaskRun.FUSION_TRACE constant for .fusion/trace.json path - Remove narrating comments, align with existing .command.trace style Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> Signed-off-by: Paolo Di Tommaso <[email protected]>
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> Signed-off-by: Paolo Di Tommaso <[email protected]>
Member
Author
|
Ready. TO BE TESTED END TO END |
Collaborator
Has been Tested End to End |
munishchouhan
approved these changes
Apr 16, 2026
bentsherman
approved these changes
Apr 16, 2026
jorgee
approved these changes
Apr 16, 2026
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
5 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.
Summary
Spec highlights
Test plan