-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
bug(material): ci/cd build failed with wrong imports #26603
Comments
|
We have a similar issue within our project. We have migrated step by step from Angular v12 to v13, then from v13 to v14 and so on, finally arriving at the latest v15. We have used the migration schematics and the official update guide. And now approx. one of five builds fails on our CI server (Jenkins) with similar error messages:
We have tried to use the legacy SASS API by setting the Same setup as @monkeycatdog: Feels very much like a race condition within the SASS processing stack. 🤷♂️ Appreciate any kind of help / tip to mitigate this issue. |
To possibly attract more people with the same issue, here's the error that pops up when inside
Yet there is no line 17 in this component. All it does is @use/@import a file containing variables/mixins as seen in the comments above. Running with Node v. 18.13.x |
I'm also having this issue, cannot figure out the problem, re-running usually fixes it. Not good for our CI |
Also seeing this intermittently in our CI.
|
I'll work this weekend in creating a reproduction repo for this issue. For now, this is a blocker to update to Angular 15 |
@Carniatto did you by any chance succeed with a sort of reproducible blank repo? |
@PhilippMeissner I've not been able to reproduce in a small scale repo. I was able to narrow down a bit the problem in my case. I'm running a big project with many libraries and the errors (example below) seems to always be related to Another interesting piece of information that might be relevant is that if I run a second time the build it passes. Also the libs that cause this error are almost never the same. I will keep growing the sandbox to try reproducing the problem but so far I already have 2 apps with couple libraries usign the same SCSS structure I have in my app and all the same versions of npm packages but it still compiles normally. I can only guess that this only happens when a big amount of apps/libs is built at once. I'm ONLY experiencing this problem when running a build inside a docker container based on Alpine 3.15 |
@PhilippMeissner I've finally succeeded into reproducing the issue. Here is the repo: https://github.com/Carniatto/angular15SaasIssue just run: |
Thanks for the work and heads-up! All of the info given so far leads me to believe that this can only be a race condition of some sorts inside webpack/sass-loader.. |
I have updated the Dockerfile with a publicly available image. I'm hoping to get some attention on this issue, right now this is keeping my team stuck on Angular 14 |
We have the same issue, is there any solution for this? |
Ping to give this a minor spotlight again. Anybody stumbled into a solution other than retrying the builds ever so often? |
Would be good to have some guidance at least. Maybe we need to restructure how we do styles in a multi app environment. Hoping someone will help us |
Chiming in to say that we are running into the same issue on Azure pipelines CI, ~1/10 builds has this issue. We are getting both the CI environment: |
Our team is facing the same issue in our CI environment. Any update on this? |
Still an issue on our side. Invested a good amount of hours to debug this to no avail. Any chance this will be addressed in future releases? |
So we have this issue at the moment as well, and already spent a lot of time on it.. We did find a related issue with maybe some more info in the angular-cli project (closed unfortunately). Maybe that might spark an idea what's going on? |
This is still an issue even with using the latest version of Angular/Material (16.2.4) |
We're also seeing this ✋ in both Angular 15 and 16. |
It amazes me that this issue is still open. @alan-agius4 Since you closed angular/angular-cli#25018 I'm going for the long shot and tag you here, since this issue is the same and does have a reproducable example. |
I can confirm that my team is seeing this issue regularly in Angular 16. I have not seen this issue occur locally though, only in CI. Update: |
Same here. I think it's about the CIs performance. I noticed the CI often runs into the error when it runs the "first time" after waking up. The consecutive runs usually run smoothly. |
Hey, any news about this issue? any new solutions? |
The way we solved the issue in my team was by refactoring the styles to use CSS variables hard-coded for most colors from the team. It is not ideal but since this is open for more than a year we had to proceed |
That how we solved it as well |
also pinging @edolic.
and use it as |
There's extensive discussion happening about this issue at angular/angular-cli#27167. Let's continue tracking it there. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Is this a regression?
The previous version in which this bug was not present was
14
Description
After migration from 14 to 15.1 I have failed time to time builds
I'm still on legacy theming and components.
Reproduction
Steps to reproduce:
Unfortunately, there is no steps.
Expected Behavior
Successful build
Actual Behavior
Failed build
Environment
The text was updated successfully, but these errors were encountered: