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
We are using Github actions to run our jmeter scripts.
We have configured self-hosted runner and scheduling the job on that runners. Job will be generally scheduled to run for 3-4 days depending on the scenarios.
For first 10-12 hours my workflow will print logs properly but after that job status will be changed as cancelled & printing logs will be stopped. But overall job workflow would be running same as in below mentioned image.
we will not able to see the jmeter job logs (error %) or anything as we will not be able to expand and see the jmeter job's step. My question is if the job was canceled how would it be still running & is there any variable / parameter that we can set to increase the log size limit bcz my job will print huge logs as part of the script execution.
If anyone faced this similar kind of issue please guide us to resolve . Thankyou in advance
The text was updated successfully, but these errors were encountered:
katkhem-bh
changed the title
Github actions workflow issue for long running jobs - Logs not expanding at the runtime
Github actions workflow issue for long running jobs - Job status marked as cancelled automatically but workflow is running
Jun 27, 2024
Hi,
We are using Github actions to run our jmeter scripts.
We have configured self-hosted runner and scheduling the job on that runners. Job will be generally scheduled to run for 3-4 days depending on the scenarios.
For first 10-12 hours my workflow will print logs properly but after that job status will be changed as cancelled & printing logs will be stopped. But overall job workflow would be running same as in below mentioned image.
we will not able to see the jmeter job logs (error %) or anything as we will not be able to expand and see the jmeter job's step. My question is if the job was canceled how would it be still running & is there any variable / parameter that we can set to increase the log size limit bcz my job will print huge logs as part of the script execution.
If anyone faced this similar kind of issue please guide us to resolve . Thankyou in advance
The text was updated successfully, but these errors were encountered: