Skip to content
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

Improve timeout behavior #169

Merged
merged 1 commit into from
May 5, 2024
Merged

Conversation

thomasmerx
Copy link
Contributor

Instead of putting one timeout of 2 sec at the beginning of the check for the loop devices, use the already existing timeout implementation inside the loop and just increase the maximum timeout to 60 sec. This improves the overall behavior, because as soon as the loop devices are detected, the loop will be exited, but it also increases the maximum possible time to wait for the loop devices. This is helpful when being used on slower systems.

Instead of putting one timeout of 2 sec at the beginning of the check for
the loop devices, use the already existing timeout implementation
inside the loop and just increase the maximum timeout to 60 sec.
This improves the overall behavior, because as soon as the loop
devices are detected, the loop will be exited, but it also increases
the maximum possible time to wait for the loop devices. This is helpful
when being used on slower systems.
@solo-build-bot
Copy link

Waiting for approval from someone in the solo-io org to start testing.

@yuval-k yuval-k merged commit 61676eb into solo-io:master May 5, 2024
1 of 2 checks passed
thomasmerx added a commit to thomasmerx/packer-plugin-arm-image that referenced this pull request Jun 11, 2024
This fixes issue solo-io#162 and solo-io#165. I refactored the timeout handling,
with solo-io#169 by increasing the existing timeout and removing the additional 2 sec
sleep, because the 2 sec sleep was not working in all cases.
Unfortunately, the increase alone is not sufficient, so I'm re-adding
the 2 sec sleep again.
yuval-k pushed a commit that referenced this pull request Jul 25, 2024
This fixes issue #162 and #165. I refactored the timeout handling,
with #169 by increasing the existing timeout and removing the additional 2 sec
sleep, because the 2 sec sleep was not working in all cases.
Unfortunately, the increase alone is not sufficient, so I'm re-adding
the 2 sec sleep again.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants