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

[Bug]: CI is building inconsistently #404

Closed
kimadactyl opened this issue Jun 28, 2024 — with Huly for GitHub · 7 comments
Closed

[Bug]: CI is building inconsistently #404

kimadactyl opened this issue Jun 28, 2024 — with Huly for GitHub · 7 comments
Labels
bug Something isn't working eee Enormous Extra Effort (I have no idea how or needs breaking down) verified vvv Very Very Valuable

Comments

Copy link
Member

kimadactyl commented Jun 28, 2024

Description

Site is failing about half the time due to an Elm compilation error. This is significantly reducing our quality of life as our notifications are throwing a lot of false positives, and information updates are inconsistent.

Currently it is as below, but I think the package name has shifted a few times.

Some idea of what might be causing it and a suggested fix is here: https://discourse.elm-lang.org/t/problem-building-dependencies-error-in-pipeline-solved/8755

09:10:12.800 | -- PROBLEM BUILDING DEPENDENCIES -----------------------------------------------
-- | --
09:10:12.800 |  
09:10:12.801 | I ran into a compilation error when trying to build the following package:
09:10:12.801 |  
09:10:12.801 | elm/regex 1.0.0
09:10:12.801 |  
09:10:12.801 | This probably means it has package constraints that are too wide. It may be
09:10:12.802 | possible to tweak your elm.json to avoid the root problem as a stopgap. Head
09:10:12.802 | over to https://elm-lang.org/community to get help figuring out how to take this
09:10:12.802 | path!
09:10:12.802 |  
09:10:12.802 | Note: To help with the root problem, please report this to the package author
09:10:12.802 | along with the following information:
09:10:12.802 |  
09:10:12.802 | elm/core 1.0.5
09:10:12.802 |  
09:10:12.802 | If you want to help out even more, try building the package locally. That should
09:10:12.803 | give you much more specific information about why this package is failing to
09:10:12.803 | build, which will in turn make it easier for the package author to fix it!
09:10:12.803 |  
09:10:12.803 | Compilation failed.
09:10:12.803 |  
09:10:12.818 | Failed: build command exited with code: 1
09:10:13.724 | Failed: error occurred while running build command

Steps to reproduce

View Cloudflare build logs on fail

@kimadactyl kimadactyl added the bug Something isn't working label Jun 28, 2024
@kimadactyl
Copy link
Member Author

@katjam - link in issue ticket suggests a solution but it's out of my depth

@katjam
Copy link
Member

katjam commented Jun 28, 2024

Thanks. I did used to use that Netlify cache thing to solve the problem there, but it did stop working a couple times / changed server spec.

For this I am wondering if we pull back to building twice a day. At the moment it's every 3 hours which shouldn't be overlapping - but maybe it overlaps with someone else on same machine? I have no idea how cloudflare allocates these build servers but the problem does seem a lot more frequent than it was on netlify.

@kimadactyl
Copy link
Member Author

kimadactyl commented Jun 28, 2024

I think it's just that there's 3 projects in elm-stuff that are clashing, no? thats what the link seemed to suggest to me, anyway, that they are all fighting each other

@katjam
Copy link
Member

katjam commented Jun 29, 2024

I think it's just that there's 3 projects in elm-stuff that are clashing, no? that's what the link seemed to suggest to me, anyway, that they are all fighting each other

Ah yes, I see. It's because :

The elm-pages build command is running two parallel compilation tasks for the client and worker apps creating a race condition.

Dillon says it's been fixed but not sure if that means in v2 or v3. We also need to cut back on event window because there was a recent timeout fail on the whole build.

@katjam
Copy link
Member

katjam commented Jun 29, 2024

Looks like that update happened in v3.0 - so for now I'll fix the event window import #391 and we should do an experiment with upgrading to v3.0 when we integrate Manchester because it seems like it'll address a couple things for us.

@katjam katjam added vvv Very Very Valuable eee Enormous Extra Effort (I have no idea how or needs breaking down) labels Aug 12, 2024
@katjam
Copy link
Member

katjam commented Aug 12, 2024

closing as superseded by: #412

@katjam
Copy link
Member

katjam commented Oct 28, 2024

Verified. Have raised a bug to deal with Time #449 - but otherwise build seems to be working well. Time will tell once merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working eee Enormous Extra Effort (I have no idea how or needs breaking down) verified vvv Very Very Valuable
Projects
None yet
Development

No branches or pull requests

2 participants