Skip to content

Conversation

fmvilas
Copy link
Member

@fmvilas fmvilas commented Aug 11, 2025

Description

I'm back...

Related issue(s)
Fixes #1097

Copy link

changeset-bot bot commented Aug 11, 2025

⚠️ No Changeset found

Latest commit: 7ef305c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

@smoya
Copy link
Member

smoya commented Aug 11, 2025

That's brilliant dude! For some reason no PR is able to be merged. Like THIS ONE #1094

More on #1094 (comment)

@fmvilas
Copy link
Member Author

fmvilas commented Aug 11, 2025

Damn, I haven't landed as a maintainer yet and you're already giving me work to do 😅 Let me check 👀

@aeworxet
Copy link
Contributor

The impossibility to merge PRs is due to the failing Puppeteer test.
I was investigating the issue with @derberg some time ago.

There is no required by Puppeteer software installed by default in GitHub's ubuntu-24.04 runner, and the AppArmor policy has changed since Ubuntu 23.10, so testing of Parser in browser through puppeteer hangs.

All non-merged PRs were going through testing on ubuntu-latest, which is currently ubuntu-24.04.

As a possible solution, this test can be removed from the NPM test script so that it doesn't run as part of the regular tests, and a separate workflow can be created that runs exclusively the Puppeteer test. This workflow can run on just one VM, and it can even be a macOS, as this test is not OS-specific.

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.

Get back as a maintainer
5 participants