Skip to content

Conversation

@devversion
Copy link
Member

We should not flaw/skip results due to timeouts caused by e.g. stuck building or stuck serving.

We should not flaw/skip results due to timeouts caused by e.g. stuck building or
stuck serving.
Comment on lines +201 to +204
const maxAttempts = (options.promptTimeoutRetries ?? 0) + 1;
for (let attemptIdx = 0; attemptIdx < maxAttempts; attemptIdx++) {
try {
await env.executor.finalizeEval(evalID);
} catch (e) {
progress.log(rootPromptDef, 'error', 'Failed to finalize eval', `${e}`);
return await evaluate();
Copy link
Collaborator

Choose a reason for hiding this comment

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

nit (potentially for a followup PR): do we want to have a timeout in-between attempts (e.g. exponential backoff)?

Copy link
Member Author

Choose a reason for hiding this comment

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

Potentially, we can expand when we see the need. The exponential backoff is currently used for LLM requests separately (where we try to overcome rate limits)

@devversion devversion merged commit 2fea7cf into angular:main Nov 24, 2025
3 checks passed
@devversion devversion deleted the retries branch November 24, 2025 22:17
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