Skip to content

feat: expose current attempt index on task result - #11680

Closed
hi-ogawa wants to merge 1 commit into
vitest-dev:mainfrom
hi-ogawa:result-attempt-index
Closed

hi-ogawa wants to merge 1 commit into
vitest-dev:mainfrom
hi-ogawa:result-attempt-index

Conversation

@hi-ogawa

@hi-ogawa hi-ogawa commented Oct 21, 2026 •

Copy link
Copy Markdown
Collaborator

WIP 🤖

While a test runs, nothing tells you which attempt it is on. result.retryCount sums retries across all repeats, so it doesn't restart at 0 on the next repeat, and result.repeatCount is the current repeat index despite its name. result.attempts only lists finished attempts. Task results now have retryIndex and repeatIndex, which are set when each attempt starts and use the same names as attempts. repeatCount and retryCount are deprecated in favor of repeatIndex and attempts. The browser trace view now reads the indices from the task instead of keeping its own copy.

With { retry: 1, repeats: 1 }, where the first attempt of each repeat fails:

attempt retryCount repeatCount retryIndex repeatIndex
1st 0 0 0 0
2nd 1 0 1 0
3rd 1 1 0 1
4th 2 1 1 1

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@netlify

netlify Bot commented Oct 21, 2026

Copy link
Copy Markdown

✅ Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit cfa558e
🔍 Latest deploy log https://app.netlify.com/projects/vitest-dev/deploys/6ad8735cd679ba54925c8998
😎 Deploy Preview https://deploy-preview-11680--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@hi-ogawa

Copy link
Copy Markdown
Collaborator Author

maybe someday. closing for now.

@hi-ogawa hi-ogawa closed this Oct 29, 2026
@github-actions github-actions Bot locked and limited conversation to collaborators Nov 13, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant