build: try GitHub Actions CI for running tests

[cclauss]

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

[targos]

Something cancelled the build, I don't know what.

[cclauss]

Seem like when one branch fails, GitHub CI fails the others.

[targos]

@cclauss I found there is an option to prevent cancelling the matrix if one job fails:
https://help.github.com/en/articles/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast

[cclauss]

Nice! I also found and added continue-on-error at the job level which is analogous to Travis CI's allow_failures. Nice collaboration among Team Switzerland...

[cclauss]

Can someone with Travis CI admin rights please rerun Travis CI - Pull Request?

[Trott]

Can someone with Travis CI admin rights please rerun Travis CI - Pull Request?

There's a Re-Run button but it's not working for me. If all else fails, one thing you can do to get a re-run is force-push to the branch after a basically-no-op rebase.

[Trott]

@cclauss Is this an experiment for now or are you hoping to land this? If the latter, let's ping for some reviews. (And if it should be closed, obviously let's do that.)

[cclauss]

I would be interested to replace Travis CI with GitHub Actions-based CI however GitHub Actions remains in Beta until November. We can close this PR now and create a new one once GitHub Actions goes GA. Thanks to @targos for the investigation.

[richardlau]

Given that Node.js should build with Python 3 is continue-on-error desired?

[gengjiawen]

Since #29474 involved test, I think maybe we can drop this PR ?

[BridgeAR]

This needs a rebase.

[cclauss]

No longer needed sonce #29474 involved similar tests