Stop sassc segmentation faults from breaking test builds #72
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a known issue with sassc (which Geneac inherits from sass-rails), ultimately drilling down to a Sprockets problem, which can cause segfaults which break builds. It has been described across numerous repos:
Looking back through closed PRs, this appears to be an ongoing issue for Geneac test builds. Forcing assets not to export concurrently is a suggested fix for this (the theory is that it's attempting to compile assets twice at the same time, which is causing a deadlock).
The only downside to this is slightly slower compilation because it doesn't do it in parallel, but Geneac would need substantially more assets than it currently has for that to become noticeable - and hopefully by the time Geneac has enough assets for this to be noticeable, newer versions of the gems will be out which will have solved the issue.