Skip to content

Conversation

dgozman
Copy link
Contributor

@dgozman dgozman commented Oct 14, 2025

No description provided.

Copy link
Contributor

Test results for "MCP"

2550 passed, 102 skipped


Merge workflow run.

Copy link
Contributor

Test results for "tests 1"

2 failed
❌ [playwright-test] › runner.spec.ts:118 › should ignore subprocess creation error because of SIGINT @macos-latest-node18-1
❌ [playwright-test] › reporter-html.spec.ts:3006 › created › execSync doesnt produce a second stdout attachment @macos-latest-node18-2

2 flaky ⚠️ [firefox-library] › library/inspector/cli-codegen-1.spec.ts:1079 › cli codegen › should not throw csp directive violation errors `@firefox-ubuntu-22.04-node18`
⚠️ [firefox-page] › page/page-event-request.spec.ts:182 › should return response body when Cross-Origin-Opener-Policy is set `@firefox-ubuntu-22.04-node18`

47017 passed, 816 skipped


Merge workflow run.

export default defineConfig({
reporter: [['blob', { outputFile: `./blob-report/report-${os.platform()}.zip` }]],
reporter: 'blob',
tag: process.env.CI_ENVIRONMENT_NAME, // for example "@APIv2"
Copy link
Member

Choose a reason for hiding this comment

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

let's include platform name in the example: ['@apiv2', 'linux']. This is important for the case of running the same project on multiple platforms.

const tags = sanitizeForFilePath(config.tags.map(tag => tag.substring(1)).join('-')).substring(0, 50);
reportName = `${reportName}-${tags}`;
}
if (this._options._commandHash)
Copy link
Member

Choose a reason for hiding this comment

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

Let's include tags into the inputs for the hash - for the case when the tags are long and we may end up with clashing 50 chars prefixes.

version: currentBlobReportVersion,
userAgent: getUserAgent(),
name: process.env.PWTEST_BOT_NAME,
name: process.env.PWTEST_BOT_NAME || config.tags.join(' '),
Copy link
Member

Choose a reason for hiding this comment

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

Can we read the tags from the config event instead of storing them in the name?

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