Skip to content

Conversation

@Skn0tt
Copy link
Member

@Skn0tt Skn0tt commented Dec 23, 2025

If we want to compare shard performance grouped by bot name, we can't have the shard index in the bot name.

@Skn0tt Skn0tt self-assigned this Dec 23, 2025
@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

node-version: ${{matrix.node-version}}
command: npm run ttest -- --shard ${{ matrix.shardIndex }}/${{ matrix.shardTotal }}
bot-name: "${{ matrix.os }}-node${{ matrix.node-version }}-${{ matrix.shardIndex }}"
bot-name: "${{ matrix.os }}-node${{ matrix.node-version }}"
Copy link
Member

Choose a reason for hiding this comment

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

wouldn't it break the merge via adding all the shard zips into the archive with the same name?

Copy link
Contributor

Choose a reason for hiding this comment

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

report.zip includes shard index by default, so downloaded reports should be all distinct.

with:
report_dir: blob-report
job_name: ${{ inputs.bot-name }}
job_name: ${{ inputs.bot-name }}-${{ inputs.shard-index }}
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we can even use some random guid or timestamp here, since we do not really care about the artifact name.

Copy link
Member Author

Choose a reason for hiding this comment

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

getting a random value / timestamp would require one more "script" step here since there's no randomness in github's templating language. i actually like shard-index, I had a couple of instances in the past where I wanted to download a single specific blob to do some experiments.

node-version: ${{matrix.node-version}}
command: npm run ttest -- --shard ${{ matrix.shardIndex }}/${{ matrix.shardTotal }}
bot-name: "${{ matrix.os }}-node${{ matrix.node-version }}-${{ matrix.shardIndex }}"
bot-name: "${{ matrix.os }}-node${{ matrix.node-version }}"
Copy link
Contributor

Choose a reason for hiding this comment

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

report.zip includes shard index by default, so downloaded reports should be all distinct.

@Skn0tt Skn0tt requested a review from dgozman January 5, 2026 12:37
@Skn0tt Skn0tt merged commit 830797c into microsoft:main Jan 6, 2026
28 of 31 checks passed
@github-actions
Copy link
Contributor

github-actions bot commented Jan 6, 2026

Test results for "tests 1"

16 failed
❌ [default] › debug-tests.spec.ts:58 › should debug one test and pause at end @vscode-extension
❌ [default] › debug-tests.spec.ts:172 › should debug one test and pause on error @vscode-extension
❌ [default] › debug-tests.spec.ts:380 › should run global setup before debugging @vscode-extension
❌ [default] › debug-tests.spec.ts:465 › should debug multiple tests and stop on first failure @vscode-extension
❌ [default] › debug-tests.spec.ts:516 › should not pause at the end of a setup test @vscode-extension
❌ [default-reuse] › debug-tests.spec.ts:58 › should debug one test and pause at end @vscode-extension
❌ [default-reuse] › debug-tests.spec.ts:172 › should debug one test and pause on error @vscode-extension
❌ [default-reuse] › debug-tests.spec.ts:380 › should run global setup before debugging @vscode-extension
❌ [default-reuse] › debug-tests.spec.ts:465 › should debug multiple tests and stop on first failure @vscode-extension
❌ [default-reuse] › debug-tests.spec.ts:516 › should not pause at the end of a setup test @vscode-extension
❌ [default-trace] › debug-tests.spec.ts:58 › should debug one test and pause at end @vscode-extension
❌ [default-trace] › debug-tests.spec.ts:172 › should debug one test and pause on error @vscode-extension
❌ [default-trace] › debug-tests.spec.ts:380 › should run global setup before debugging @vscode-extension
❌ [default-trace] › debug-tests.spec.ts:465 › should debug multiple tests and stop on first failure @vscode-extension
❌ [default-trace] › debug-tests.spec.ts:516 › should not pause at the end of a setup test @vscode-extension
❌ [playwright-test] › playwright.trace.spec.ts:345 › should retain traces for interrupted tests @macos-latest-node20

4 flaky ⚠️ [firefox-library] › library/inspector/cli-codegen-1.spec.ts:1082 › cli codegen › should not throw csp directive violation errors `@firefox-ubuntu-22.04-node20`
⚠️ [firefox-page] › page/page-wait-for-function.spec.ts:104 › should work with strict CSP policy `@firefox-ubuntu-22.04-node20`
⚠️ [playwright-test] › runner.spec.ts:124 › should ignore subprocess creation error because of SIGINT `@macos-latest-node20`
⚠️ [playwright-test] › ui-mode-trace.spec.ts:183 › should show snapshots for steps `@macos-latest-node20`

34391 passed, 691 skipped


Merge workflow run.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 6, 2026

Test results for "MCP"

6 failed
❌ [chrome] › mcp/video.spec.ts:43 › should work with { saveVideo } (isolated) @mcp-macos-15
❌ [chromium] › mcp/test-debug.spec.ts:167 › test_debug (pause/snapshot/resume) @mcp-macos-15
❌ [chromium] › mcp/test-debug.spec.ts:234 › test_debug / evaluate x 2 @mcp-macos-15
❌ [firefox] › mcp/http.spec.ts:263 › http transport shared context @mcp-macos-15
❌ [firefox] › mcp/planner.spec.ts:69 › planner_setup_page seed resolution @mcp-macos-15
❌ [firefox] › mcp/planner.spec.ts:131 › planner_setup_page with dependencies @mcp-macos-15

2816 passed, 116 skipped


Merge workflow run.

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.

3 participants