gkellogg
commented
3 years ago Note that the earl.ttl still uses the undefined earl:Report and earl:assertions terms, although in JSON-LD, assertions is a reverse property on earl:test. It's still useful for organizing the Turtle output, even though it is apocryphal.
Formerly, the top-level report also used earl:assertions, not they apocryphal mf:report.
For some reason, we've been getting segmentation faults on some runs relating to running reports. This PR drops the Ruby version from 3.0 to 2.7, uses an updated version of the earl-report gem which pulls in fewer supporting files, and does not clean the reports before building, so it should only be triggered when a new earl submission is received that hasn't been used to run reports.