exp show: output executor info for successful exps when available #10239
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.
β I have followed the Contributing to DVC checklist.
π If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here.
Thank you for the contribution - we'll try to review it as soon as possible. π
Should close #9425
related: #9442
For sucessfully run queued experiments,
dvc exp show --json
will now include executor info if it's still available (i.e. logs haven't been removed withdvc queue remove
)note that:
pid
is listed but will no longer be valid since the run finishedroot
is unavailable since the tempdir used for execution is removed on exp completion (but the logs are available and stored in a separate location)executor
will still be null for successful workspace and--temp
runs since we do not preserve any executor state or logs in those cases (handling logs for these cases will be done separately, but once those are available they will work the same as the dvc-task queued exps here)