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
Problem:
Before we had a runner binary, we had to do all sorts of things to manipulate the compute node and files on it to run the task's command-line and upload trace and metrics files, including scrubbing the compute nodes before the next task started, all to avert several issues with the way that azure batch handles resource files, container images, and tasks.
Now that we have the runner, which has already taken on the most major of those responsibilities, it is time to give it the rest of them and eliminate the batch script file (and thus the requirement we have on bash) entirely.
Incorporate still-relevant activities from the eliminated code into the runner itself (making use of the task json as appropriate, if needed). That list is TBD, but should include uploading the metrics.txt and the stderr.txt & stdout.txt files from batch before exiting, even when failures have occurred.
The text was updated successfully, but these errors were encountered:
Problem:
Before we had a runner binary, we had to do all sorts of things to manipulate the compute node and files on it to run the task's command-line and upload trace and metrics files, including scrubbing the compute nodes before the next task started, all to avert several issues with the way that azure batch handles resource files, container images, and tasks.
Now that we have the runner, which has already taken on the most major of those responsibilities, it is time to give it the rest of them and eliminate the batch script file (and thus the requirement we have on
bash
) entirely.Solution:
src/TesApi.Web/scripts/clean-executor.sh
,src/TesApi.Web/scripts/task-run.sh
, &src/TesApi.Web/BatchNodeScriptBuilder.cs
.metrics.txt
and thestderr.txt
&stdout.txt
files from batch before exiting, even when failures have occurred.The text was updated successfully, but these errors were encountered: