-
Notifications
You must be signed in to change notification settings - Fork 360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WX-1168] TES Log Paths #7210
[WX-1168] TES Log Paths #7210
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -30,9 +30,10 @@ | |
val callInputsRoot = callRoot.resolve("inputs") | ||
|
||
/* | ||
* tesTaskRoot: This is the root directory that TES will use for files related to this task. | ||
* TES expects a path relative to the root of the storage container. | ||
* We provide it to TES as a k/v pair where the key is "internal_path_prefix" and the value is the relative path string. | ||
* tesTaskRoot: The Azure TES implementation allows us to specify a working directory that it should use for its own files. | ||
* Once the task finishes, this directory will contain stderr.txt, stdout.txt, and some other misc files. | ||
* Unlike other paths we provide, this one is expected as a path relative to the root of the storage container. | ||
* We provide it as a k/v pair where the key is "internal_path_prefix" and the value is the relative path string. | ||
* This is not a standard TES feature, but rather related to the Azure TES implementation that Terra uses. | ||
* While passing it outside of terra won't do any harm, we could consider making this optional and/or configurable. | ||
*/ | ||
|
@@ -42,6 +43,13 @@ | |
case anyOtherPath: Path => anyOtherPath.pathAsString | ||
} | ||
|
||
// Like above: Nothing should rely on these files existing, since only the Azure TES implementation will actually create them. | ||
// Used to send the Azure TES log paths to the frontend. | ||
val azureLogPathsForMetadata : Map[String, Any] = Map( | ||
"tes_stdout" -> taskFullPath./("stdout.txt").pathAsString, | ||
"tes_stderr" -> taskFullPath./("stderr.txt").pathAsString | ||
Check warning on line 50 in supportedBackends/tes/src/main/scala/cromwell/backend/impl/tes/TesJobPaths.scala Codecov / codecov/patchsupportedBackends/tes/src/main/scala/cromwell/backend/impl/tes/TesJobPaths.scala#L48-L50
|
||
Comment on lines
+49
to
+50
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm wondering if the naming should reflect the purpose (frontend) but could use some context. Maybe let's sync with faces so I can get context quickly and contain the length of the semantics discussion 🙂 Semi-related, we have a bunch of metadata keys in one place here, it's unclear whether this backend-specific one actually belongs in the main list though. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Tangentially related comment: There's a method called With two new keys we'd need to update these types of fetches (or any method that might use |
||
) | ||
|
||
// Given an output path, return a path localized to the storage file system | ||
def storageOutput(path: String): String = { | ||
callExecutionRoot.resolve(path).toString | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love this naming and I'm glad you found the perfect fit to stick some extra stuff