Skip to content

Conversation

@hvaara
Copy link
Contributor

@hvaara hvaara commented Sep 14, 2024

Before this fix, the progress checker would pause for 240 seconds, causing the program to potentially wait that long after all evaluations were complete.

This PR changes the logic so that the progress checker now checks for updates every second, but only displays a warning if no progress has been made in the past 240 seconds. Once all tasks are finished, the thread will terminate.

Fixes #42

@hvaara hvaara changed the title Increase frequency of progress checker Await futures in progress checker Sep 14, 2024
@terryyz terryyz merged commit 195a165 into bigcode-project:main Oct 3, 2024
@hvaara hvaara deleted the progress-checker-fix branch October 4, 2024 07:09
@hvaara
Copy link
Contributor Author

hvaara commented Feb 18, 2025

This PR changes the logic so that the progress checker now checks for updates every second

This sentence from the description is wrong and based on logic from a prior commit. The current implementation awaits the thread instead of checking every second. A warning is displayed every 240 seconds with no progress.

@hvaara
Copy link
Contributor Author

hvaara commented Feb 20, 2025

Looks like this got overwritten in main. I'll open another PR to reintroduce it.

@hvaara hvaara restored the progress-checker-fix branch February 20, 2025 02:45
hvaara added a commit to hvaara/bigcodebench that referenced this pull request Feb 20, 2025
hvaara added a commit to hvaara/bigcodebench that referenced this pull request Feb 20, 2025
terryyz added a commit that referenced this pull request Feb 20, 2025
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.

[bug] Lingering processes after eval run completion

2 participants