Loren M. Lang

I was hoping to be able to present a fully-passing report on GitHub CI, but I'm still getting a failure on API 24 that isn't showing up anywhere else. I...

OK, I finally figured out the final issue with the GitHub CI test runner. For whatever reason, API 24 requires that WRITE_EXTERNAL_STORAGE be granted explicitly. I cannot explain why I...

This branch was developed on github-ci and test results produced from it, but it does not depend on anything in that branch and cleanly rebased to master. The test framework...

But yes, #315 should be completely safe because it just adds one new file, .github/workflows/android.yml, and makes a small modification to the README to add the CI results badge generated...

This is the branch that requires more careful review because my very first PR did break things which I only noticed after running the test suite against a wide range...

Developer's welcome to help! We can always more contributors. :-) Right now, I believe the main issue is that support to instantiate multiple backends and also allow them to be...

If you're curious, most of my ideas for that workflow came from this article: https://medium.com/upday-devs/how-to-setup-github-actions-for-android-projects-a94e8e3b0539

OK, this is now rebased onto the latest master with spelling error fixed. I guess I need to turn spell check on more often when editing in Vim.

Once this branch is merged in, you should see pass/fail results embedded into the PR from the GitHub workflow. In the mean time, here are the results from this PR:...

Any further changes you'd like for this PR before merging it? Don't worry, any crypto miners would be on the manual-di branch where it's easier to hide them.