Setup travis-ci to automate testing #515

Activity

1. robertleeplummerjr commented on Oct 12, 2019

   

   robertleeplummerjr

   on Oct 12, 2019

   MemberAuthor

   More actions

   @PicoCreator what do you think helping out here?
2. fuzzie360

   closed this as completedin 2127766on Jul 22, 2026
3. fuzzie360 commented on Jul 22, 2026

   

   fuzzie360

   on Jul 22, 2026

   Member

   More actions

   Done — seven years later, but done: GitHub Actions CI now runs on every push and PR (Travis wasn't the survivor of the CI wars). ubuntu-latest + Node 22, headless-gl under xvfb, ~80s per run.

   One design note: the suite has ~93 known platform-dependent failures under Mesa's software renderer (float-packing precision in unsigned precision modes, a flaky Math.random uniqueness test, and Mesa-version-sensitive atan2 behavior) — all verified pre-existing against the pre-#840 dependency tree. CI diffs each run's failures against .github/known-test-failures.txt and fails only on new failures, so the signal is real instead of permanently red. Entries that stop failing get flagged for removal from the baseline.
4. pull

   added a commit that references this issue on Jul 22, 2026

   ci: Add GitHub Actions workflow running the test suite

   ...

   This issue will close once commit 2127766 is merged into the 'develop' branch.

   2127766