devops(bidi): stop publishing csv reports to the bidi-reports branch

[Yury Semikhatsky (yury-s)]

Summary

• Remove the publish_reports job added in devops(bidi): publish BiDi reports to a git branch instead of Azure #42760, which pushed the csv reports to the bidi-reports branch. The BiDi dashboard reads the GitHub artifacts, which chore(ci): reenable json reports for BiDi tests #42825 publishes again, so nothing uses the branch.
• Upload test-results/report.csv as the artifact again, like before devops(bidi): publish BiDi reports to a git branch instead of Azure #42760.
• Drop the markdown report from the job summary, also added in devops(bidi): publish BiDi reports to a git branch instead of Azure #42760.

[Holger Benl (hbenl)]

We actually use both the json report (for our dashboard) and the csv report (for a spreadsheet).
Henrik Skupin (@whimboo) could we let the spreadsheet download the csv report from GitHub artifacts?

[Henrik Skupin (whimboo)]

Yury Semikhatsky (@yury-s) we currently have a simple import via CSV in the spreadsheet - nothing scripted. What will be the new location of the .csv file? Is that a non-changing URL or does it vary per day?

[Yury Semikhatsky (yury-s)]

Yury Semikhatsky (Yury Semikhatsky (@yury-s)) we currently have a simple import via CSV in the spreadsheet - nothing scripted. What will be the new location of the .csv file? Is that a non-changing URL or does it vary per day?

It would be changing every day as it would be a github artifact link, similar to what you use to download json report. If that is an issue, I am fine with keeping the things as is (the .csv file has a fixed url in github). I just wanted to make sure you don't just download GHA artifact and still need the link.

[Henrik Skupin (whimboo)]

It would be changing every day as it would be a github artifact link, similar to what you use to download json report. If that is an issue, I am fine with keeping the things as is (the .csv file has a fixed url in github). I just wanted to make sure you don't just download GHA artifact and still need the link.

That would be great. Thanks a lot!

[Holger Benl (hbenl)]

Yury Semikhatsky (@yury-s) We've added the csv report to our dashboard pages (so it's downloaded together with the json reports), so we don't need the bidi-reports branch anymore.

[github-actions]

Test results for "tests 1"

3 flaky

⚠️ [chromium-library] › library/popup.spec.ts:260 › should not throw when click closes popup `@chromium-ubuntu-22.04-node24`
⚠️ [firefox-library] › library/browsercontext-cookies-third-party.spec.ts:257 › third party 'Partitioned;' cookies `@firefox-ubuntu-22.04-node20`
⚠️ [firefox-library] › library/browsercontext-cookies-third-party.spec.ts:470 › top level 'Partitioned;' cookie and same origin iframe `@firefox-ubuntu-22.04-node20`

52540 passed, 1270 skipped

---

Merge workflow run.

[github-actions]

Test results for "MCP"

1 failed
❌ [firefox] › mcp/annotate.spec.ts:251 › should route annotate to a running port dashboard @mcp-windows-latest-firefox

8936 passed, 1489 skipped

---

Merge workflow run.

[github-actions]

Hi, I'm the Playwright bot and I took a first look at the CI failures.

🟡 The failures look unrelated to this PR, but I could not confirm them as pre-existing flakes

This PR only changes BiDi report generation and artifact publishing. It does not reach the failing MCP dashboard flow or the Firefox Nightly behaviors under test. However, the test-results snapshot was unavailable and its refresh failed, so I found no qualifying failure on an unrelated SHA; the guide therefore requires an uncertain verdict.

Details

Uncertain

• [firefox] › mcp/annotate.spec.ts:251 › should route annotate to a running port dashboard — timed out waiting for the dashboard's first session. This PR does not change MCP or dashboard code, but I could not confirm the same test failing on an unrelated SHA.
• [moz-firefox-nightly] BiDi failures in emulation-focus.spec.ts:201, page-keyboard.spec.ts:334, page-keyboard.spec.ts:346, browsercontext-network-event.spec.ts:107, permissions.spec.ts:296, page-add-init-script-callback.spec.ts:50, and page-screenshot.spec.ts:941 — these fail during test execution, before the changed CSV artifact upload, and none exercises the CSV reporter changes. They look like Firefox Nightly regressions or flakes, but without cross-SHA history I cannot classify them as pre-existing.

The three tests reported as flaky by the merged library run passed on retry and are not real failures.

_{Triaged by the Playwright bot - agent run}

[Yury Semikhatsky (yury-s)]

Yury Semikhatsky (Yury Semikhatsky (@yury-s)) We've added the csv report to our dashboard pages (so it's downloaded together with the json reports), so we don't need the bidi-reports branch anymore.

Thanks. I'll go ahead and merge this change then.