When running the test-jvm test suite in .github/workflows/actions.yml there seems to be a GitHub workflow inconsistency. Consequently this is not an issue with fastparse, but the GItHub build system it uses. More details are
described in this PR.
The inconsistency is that the generated scalaparse tests The test source is generated so I can't link to it here but you can find it in out/repos/fastparse/scalaparse/jvm/src/test/scala/scalaparse/ProjectTests.scala
These tests use GitHub download URLs to compile the source code of various Scala projects with scalaparse; a valuable test of fastparse. This works correctly for many Scala projects but seems to fail for apache/kafka and JetBrains/intellij-scala, somewhat haphazardly. When they fail it is always an error from GitHub indicating downloading the source code went wrong.
Potential Solutions:
discover the issue and work around it in the test case
report the problem to GitHub and help them fix their issue
See the build statuses and output form PR #297 for more details.
When running the
test-jvmtest suite in.github/workflows/actions.ymlthere seems to be a GitHub workflow inconsistency. Consequently this is not an issue with fastparse, but the GItHub build system it uses. More details are described in this PR.The inconsistency is that the generated scalaparse tests The test source is generated so I can't link to it here but you can find it in
out/repos/fastparse/scalaparse/jvm/src/test/scala/scalaparse/ProjectTests.scalaThese tests use GitHub download URLs to compile the source code of various Scala projects with scalaparse; a valuable test of fastparse. This works correctly for many Scala projects but seems to fail forapache/kafkaandJetBrains/intellij-scala, somewhat haphazardly. When they fail it is always an error from GitHub indicating downloading the source code went wrong.Potential Solutions:
See the build statuses and output form PR #297 for more details.