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

Fix browser tests in CI #4114

Merged
merged 3 commits into from
Dec 16, 2024
Merged

Fix browser tests in CI #4114

merged 3 commits into from
Dec 16, 2024

Conversation

mstoykov
Copy link
Contributor

What?

Why?

Checklist

  • I have performed a self-review of my code.
  • I have added tests for my changes.
  • I have run linter locally (make lint) and all checks pass.
  • I have run tests locally (make tests) and all tests pass.
  • I have commented on my code, particularly in hard-to-understand areas.

Related PR(s)/Issue(s)

ubuntu-latest become ubuntu-24.04 and this breaks browser tests for some
reason.
@mstoykov mstoykov force-pushed the fixBrowserAfterMerge branch from a5b766a to f4b1030 Compare December 16, 2024 09:42
@mstoykov mstoykov marked this pull request as ready for review December 16, 2024 09:44
@mstoykov mstoykov requested a review from a team as a code owner December 16, 2024 09:44
@mstoykov mstoykov requested review from inancgumus and ankur22 and removed request for a team December 16, 2024 09:44
@mstoykov mstoykov changed the title set browser executable and headless in ci Fix browser tests in Ci Dec 16, 2024
@mstoykov mstoykov changed the title Fix browser tests in Ci Fix browser tests in Ci=I Dec 16, 2024
@mstoykov mstoykov changed the title Fix browser tests in Ci=I Fix browser tests in CI Dec 16, 2024
olegbespalov
olegbespalov previously approved these changes Dec 16, 2024
It seems like quite a lot of tests are not passing on windows.

Unfortunately given the volume fixing them right now seems unlikely.
So I opened #4118

This tests have not been ran on windows it seems ever, before the move
of the codebase to core.
@mstoykov mstoykov force-pushed the fixBrowserAfterMerge branch from 35a4403 to d149740 Compare December 16, 2024 14:44
Copy link
Contributor

@olegbespalov olegbespalov left a comment

Choose a reason for hiding this comment

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

👏 for doing this. However, seems like it's 20-30 more minutes 😢 So maybe it's better to disable all browser tests on windows and re-enable them as part of #4118

@mstoykov
Copy link
Contributor Author

I would prefer if we run the tests so that we do no regress more. I doubt that #4118 will automatically make the CI time less, that likely will require someone to work on this and make the tests more efficient. Maybe #4119 will help, maybe won't.

Copy link
Contributor

@ankur22 ankur22 left a comment

Choose a reason for hiding this comment

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

Thanks for working on this! 🚀

@olegbespalov olegbespalov merged commit 13658b4 into master Dec 16, 2024
29 checks passed
@olegbespalov olegbespalov deleted the fixBrowserAfterMerge branch December 16, 2024 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants