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

Fix changing directory after 60 seconds if no run folder #323

Merged
merged 3 commits into from
Dec 22, 2023

Conversation

Adoni5
Copy link
Contributor

@Adoni5 Adoni5 commented Dec 21, 2023

Excepts the File Not Found Error if the run folder doesn't appear after 60 seconds - and sets the output directory to the current working directory.

@mattloose
Copy link
Contributor

Do we want to do this or do we want to allow it to run for longer before erroring?

I'm not sure on the best course of action. We don't want to wait for ever of course - but a run can easily take two minutes or more to start?

@mattloose
Copy link
Contributor

Ok. It's not ideal but this solves the icarust issue. I suggest a revisit in the early new year. We've increased it to 120 as this is the typical warm up time for a run observed over the last few months.

Copy link
Contributor

@mattloose mattloose left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This increases the timeout time 120 seconds and provides a fall back to accommodate alternative simulations.

@Adoni5 Adoni5 merged commit e71578b into main Dec 22, 2023
9 checks passed
@Adoni5 Adoni5 deleted the issue314/crash-if-no-run-folder branch February 2, 2024 11:45
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