Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: Bump to latest playwright/test #1611

Open
wants to merge 14 commits into
base: main
Choose a base branch
from
Open

Conversation

jackw
Copy link
Collaborator

@jackw jackw commented Mar 10, 2025

What this PR does / why we need it:
Testing out playwright errors

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

@jackw jackw requested a review from a team as a code owner March 10, 2025 14:06
@jackw jackw requested a review from academo March 10, 2025 14:06
Copy link
Contributor

github-actions bot commented Mar 10, 2025

Hello! 👋 This repository uses Auto for releasing packages using PR labels.

✨ This PR can be merged. It will not be considered when calculating future versions of the npm packages and will not appear in the changelogs.

@jackw jackw added the no-changelog Don't include in changelog and version calculations label Mar 10, 2025
@jackw jackw force-pushed the jackw/bump-playwright-test branch 2 times, most recently from 3a1a757 to 8087b5c Compare March 10, 2025 16:30
Copy link
Contributor

@hugohaggmark hugohaggmark left a comment

Choose a reason for hiding this comment

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

LGTM 🎉

@jackw jackw force-pushed the jackw/bump-playwright-test branch 2 times, most recently from a939276 to e309b85 Compare March 11, 2025 14:56
@jackw jackw changed the title revert(create-plugin): put back playwright/test semver range WIP: Bump to latest playwright/test Mar 11, 2025
@jackw jackw force-pushed the jackw/bump-playwright-test branch 2 times, most recently from 66f52b9 to f9fc9bd Compare March 11, 2025 16:31
@jackw jackw self-assigned this Mar 21, 2025
@jackw jackw force-pushed the jackw/bump-playwright-test branch from f9fc9bd to 367f775 Compare March 21, 2025 12:05
@jackw jackw force-pushed the jackw/bump-playwright-test branch from 7fec36a to eb34139 Compare March 21, 2025 14:33
Copy link
Contributor

Playwright test results

Image Name Version Result Report
grafana-dev 12.0.0-232640 View report
grafana-enterprise 11.5.2
grafana-enterprise 11.2.7
grafana-enterprise 10.1.10
Troubleshooting

404 when clicking on View report

By default, the deploy-report-pages Action deploys reports to the gh-pages branch. However, you need to take an extra step to ensure that GitHub Pages can build and serve the site from this branch. To do so:

  1. Go to the Settings tab of your repository.
  2. In the left-hand sidebar, click on Pages.
  3. Under Source, select Deploy from a branch, then choose the gh-pages branch.

This action needs to be completed manually in order for your GitHub Pages site to be built and accessible from the gh-pages branch. Once configured, GitHub will automatically build and serve the site whenever new reports are deployed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-changelog Don't include in changelog and version calculations
Projects
Status: 🔬 In review
Development

Successfully merging this pull request may close these issues.

None yet

2 participants