Skip to content

fix: apply default actor timeout to runs - #134

Merged
Patai5 merged 2 commits into
masterfrom
fix/apply-default-actor-timeout-to-runs
Sep 17, 2026
Merged

Patai5 merged 2 commits into
masterfrom
fix/apply-default-actor-timeout-to-runs

Conversation

@Patai5

@Patai5 Patai5 commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

I was checking some run and noticed that it didn't have any timeout in our tests... So I investigated and found out we were not applying any run timeout to runs in the end.

I've already made a "fix" for this in the past, but it didn't work, because I incorrectly assumed that DEFAULT_TEST_ACTOR_OPTIONS are actually for the actor (they were not 😭).

Tested this change locally, and it actually works and applies the timeout this time 🙏

I've also decided to make the run timeout be one minute less than the actual test timeout, because when the entire test times out, you get messy logs without the run link - so you cannot even match the actor run otherwise...

@ruocco-l ruocco-l left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This would work in most cases (when you let it default with the timeouts), but it kinda breaks when you apply some of them, see the comments 🙏

Comment thread test/unit/lib.test.ts Outdated
Comment thread lib/lib.ts Outdated
@Patai5
Patai5 requested a review from ruocco-l September 14, 2026 18:47
@Patai5
Patai5 merged commit 82f5f7d into master Sep 17, 2026
9 checks passed
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.

5 participants