-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Temporarily disable broken Webpack JS test suites #35955
Temporarily disable broken Webpack JS test suites #35955
Conversation
Adds a "DieHardPlugin" to the Webpack build. See enclosed code comment for more details.
Should be re-enabled in: openedx#35956
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.
Looks good to me.
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
2U Release Notice: This PR has been deployed to the edX production environment. |
2U Release Notice: This PR has been rolled back from the edX production environment. |
1 similar comment
2U Release Notice: This PR has been rolled back from the edX production environment. |
2U Release Notice: This PR has been deployed to the edX production environment. |
1 similar comment
2U Release Notice: This PR has been deployed to the edX production environment. |
Description
We temporarily disable the three Webpack-based JS test suites. They have been silently broken for a long time. It is not clear yet if only the karma-webpack build config is broken, or if something in the Webpack-built JS itself is broken which is manifesting as the karma-webpack build failing.
The remaining four non-Webpack-based JS test suites are unaffected. These are running as we expect them to.
We add a small "DieHardPlugin" to webpack.common.config.js to ensure that once we re-enable these Webpack JS suites, future breakage to the karma-webpack build will yield a CI failure. I did verify this.
Screenshots
Webpack tests failing silently
(CI screenshot -- notice that it just moves onto
lms javascript
even though the build failed forcms-webpack javascript
)Webpack tests failing loudly due to new DieHardPlugin
(local screenshot)
Context
Discovered as part of #35159