GitHub workflow for running unit tests for MKL backend on CPU

[rscohn2]

Description

GitHub Actions workflow to run unit tests for MKL/CPU.

I disabled tests that require GPU by excluding tests where the name ends in gpu. RNG and DFT domains finish in 10 minutes. I am still waiting for BLAS/LAPACK to finish. We could have nightly testing that runs everything and PR testing that runs a smaller set. Any thoughts on how to reduce the testing for PR's?

@mkrainiuk

[rscohn2]

lapack finishes in 30 minutes and blas takes 1.5 hours. All the time is building the tests. Combining multiple tests into a single binary might make testing faster without reducing coverage.

[rscohn2]

@hjabird: Added CPU to job name to address: #482 (comment)

[mkrainiuk]

Any thoughts on how to reduce the testing for PR's?

I guess we can also skip building GPU part with -DENABLE_MKLGPU_BACKEND=False for now since it's not tested anyway, so it will save some build time, and we can run only runtime dispatching tests and ignore compiler time dispatching tests with -E /CT/, it should give us significant testing time reduction.

[rscohn2]

Any thoughts on how to reduce the testing for PR's?

I guess we can also skip building GPU part with -DENABLE_MKLGPU_BACKEND=False for now since it's not tested anyway, so it will save some build time, and we can run only runtime dispatching tests and ignore compiler time dispatching tests with -E /CT/, it should give us significant testing time reduction.

I made the change. It runs about 25% faster, which makes up for the intel hosted runners being 25% slower than github hosted runners. When you move to onemkl-project org, we can use github hosted runners without contending with other projects.

[dnhsieh-intel]

Thanks for the PR! I have one suggestion.