Open brian-kephart opened 4 years ago
The build in the above comment was triggered by a pull request. The build of the same commit triggered from my own Github repo passed. Not sure what the difference is.
We're observing something similar to this - we have multiple 'bad docker builds' - reinstalling sassc within the image resolves the problems
This has been observed with both Ruby 2.6 and 2.5 base image(s)
See the build result here.
sassc gem 2.2.1 ruby 2.5.5 rails 5.2.4.1
I see some other issues related to segfaults with sprockets 4, but none that match these specifics: test mode, assets not precompiled, running on CI. Also, there are no CI failures for other versions of ruby/rails, even with the same version of this gem (you can see this in the other jobs on the build linked above).