-
Notifications
You must be signed in to change notification settings - Fork 152
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
Post job cleanup
takes a long time.
#158
Comments
@baschny It is for your information. |
Is it mandatory to remove the builder on the post job? Do you have any idea about what would happen if I don't remove the builder? |
@sinwoobang For me the removal takes 2s in my jobs, so something is fishy in your setup, I guess. Does it constantly do that? maybe it was just a temporary problem? |
Yes. it is repeatedly happening.
Yes. it works faster if I do not append it.
Yes.
I do not think so. The remote server is only for this workflow. Thus, it is clean, and no such thing as QEMU works. In my opinion, it may be because of the size of the images. What size does your image have that takes 2s to get rid of? |
So in my case, I'm seeing 4m35s repeatedly to clean up - that sort of kills the joy of reducing 6m from the build step. What does the clean up depend upon? For ref: I'm running on selfhosted runner and it's single platform linux/amd64 only (no QEMU stuff). In my case - the removal takes almost all of the time
|
I'm fine to have an input to disable builder removal. |
Behaviour
Steps to reproduce this issue
Expected behaviour
Actual behaviour
Configuration
Logs
I would like to say sorry that I can't attach the log here due to security reasons. Instead, I put a screenshot. It took 16 minutes.
The text was updated successfully, but these errors were encountered: