Github actions workflow issue for long running jobs - Job status marked as cancelled automatically but workflow is running

[katkhem-bh]

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

[gustavovalverde]

We're also experiencing this, as we're running blockchain syncs which take from several hours up to 3 days.

Here's an example (which I had to cancel): https://github.com/ZcashFoundation/zebra/actions/runs/10302315476/job/28527367366

@katkhem-bh did you manage to solve this or were you able to track the underlying issue?

[github-actions[bot]]

This issue is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 15 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 15 days with no activity.