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

ci: address karma issues with Chrome v128 #2690

Closed
wants to merge 2 commits into from

Conversation

Blackbaud-SteveBrush
Copy link
Member

No description provided.

Copy link

nx-cloud bot commented Sep 5, 2024

☁️ Nx Cloud Report

CI 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 targets

Sent with 💌 from NxCloud.

@Blackbaud-SteveBrush Blackbaud-SteveBrush added the risk level (author): 1 No additional bugs expected from this change label Sep 5, 2024
@@ -37,6 +37,10 @@ module.exports = () => {
},
],
customLaunchers: {
ChromeDesktop: {
base: 'Chrome',
flags: ['--window-size=1920,1080'],
Copy link
Member Author

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
Copy link
Member Author

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
risk level (author): 1 No additional bugs expected from this change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants