chore(repo): re-enable e2e tests disabled by api-extractor issue#34519
chore(repo): re-enable e2e tests disabled by api-extractor issue#34519FrozenPandaz merged 2 commits intomasterfrom
Conversation
|
View your CI Pipeline Execution ↗ for commit cc4a91c
☁️ Nx Cloud last updated this comment at |
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for nx-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
Our PR re-enabled 14 e2e test suites that were previously disabled due to an upstream @microsoft/api-extractor@7.57.0 ESM import issue. Unfortunately, the upstream issue has not been resolved, and all re-enabled tests are failing with the same module resolution error. We need to either wait for the upstream fix, update/pin the dependency version, or keep these tests disabled until the environment issue is resolved.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
) ## Current Behavior 14 e2e test suites were disabled (`xdescribe`) due to an ESM import issue in `@microsoft/api-extractor@7.57.0` (see qmhc/unplugin-dts#461). ## Expected Behavior With the upstream issue resolved, all 14 e2e test suites are re-enabled (`describe`) and should pass normally. ## Related Issue(s) Reverts #34516 (cherry picked from commit 391d23c)
Current Behavior
14 e2e test suites were disabled (
xdescribe) due to an ESM import issue in@microsoft/api-extractor@7.57.0(see qmhc/unplugin-dts#461).Expected Behavior
With the upstream issue resolved, all 14 e2e test suites are re-enabled (
describe) and should pass normally.Related Issue(s)
Reverts #34516