-
Notifications
You must be signed in to change notification settings - Fork 24
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
ci: address karma issues with Chrome v128 #2690
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 1385a46. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 2 targetsSent with 💌 from NxCloud. |
@@ -37,6 +37,10 @@ module.exports = () => { | |||
}, | |||
], | |||
customLaunchers: { | |||
ChromeDesktop: { | |||
base: 'Chrome', | |||
flags: ['--window-size=1920,1080'], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is added to address the issues we were seeing with the SkyScrollShadowDirective
tests. If you want to run the debugger (watch mode) locally, run npx nx test core --browsers=ChromeDesktop
.
karma.conf.js
Outdated
@@ -52,7 +56,6 @@ module.exports = () => { | |||
jasmine: { | |||
random: false, | |||
}, | |||
clearContext: false, // leave Jasmine Spec Runner output visible in browser |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing this configuration to address the "Some of your tests did a full page reload!" error introduced in Chrome 128. We don't use Jasmine Spec Runner, so we can safely use the default.
See: angular/angular-cli#28271 (comment)
No description provided.