-
Notifications
You must be signed in to change notification settings - Fork 113
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
Unusually long runtime for Deploy step with self-hosted runner #1070
Comments
Downloading the containerhelper looks fast - the time does after it says running on 5.1 and analyzing releases. |
I am running the runner in an admin session, if that's what you mean. The "Deploy" action is identical to the one in 654dd54, so I don't know what else would be interfering. |
I am just suggesting what you can investigate. |
Is there some way I can see additional logs to determine what's happening between the two log entries? |
You could try to logon to the computer and manually download the BcContainerHelper repo and run BcContainerHelper.ps1 and try to figure out what takes so long. Looking at the code the InitializeModule.ps1 is the first script to run when importing the BcContainerHelper.psm1 module and this script doesn't really do much before printing the BcContainerHelper version number (which appears 4 minutes after importing). |
I am using a self-hosted Windows runner to deploy an app on an OnPrem environment, but am experiencing very long waiting times during the Deploy-step during the "Deploy To" job. From what I can tell, the job takes 6 minutes to resolve the function
DownloadAndImportBcContainerHelper
from the "AL-GoHelper.ps1` script, which isn't something I've encountered with my other runners. Since there isn't really any logging to speak of it's hard to tell what is taking so long, but the runner logs seem to write the same three lines over and over again for the entire duration of the problematic function:The runner is running on a Windows 2019 Server in an admin PS session. The log of the job can be found here:
logs_23480834135.zip
The text was updated successfully, but these errors were encountered: