CI for indicating that numba master does not break numba-dpex

[PokhodenkoSA]

• GitHub workflow for testing stable numba-dpex with numba master
• Badge on main page
• Possibility to subscribe to the status for Numba team

[sklam]

In numba, we have been doing integration testing in this repo: https://github.com/numba/numba-integration-testing using CircleCI which is triggered on a CRON schedule. @esc made a tool, called texasbbq, to simplify it. For example, the configuration for testing umap looks https://github.com/numba/numba-integration-testing/blob/fd58d5ce97357b0a2e4273fe4b89656370c8a2ed/switchboard.py#L30-L55. Under the hood, it is:

• git clone numba, install dependencies, and build it
• git clone <downstream project>, install dependencies, and build it
• run test in <downstream project>

[PokhodenkoSA]

@sklam @esc
I think the right way is to prepare PR to https://github.com/numba/numba-integration-testing and add numba-dppy in the list. Ok?

[esc]

@PokhodenkoSA yes, indeed. The exitsing configurations will be a good place to start! Let me know if you need any assistence!

[PokhodenkoSA]

@esc
I am searching a way to test it locally before pushing PR.
I will install texasbbq via pip and run TARGET=numba-dppy ./switchboard.py -t $TARGET.

[esc]

@esc I am searching a way to test it locally before pushing PR. I will install texasbbq via pip and run TARGET=numba-dppy ./switchboard.py -t $TARGET.

That sounds right. You will also need the packaging package to make that work. But yes, in principle that is the way to run it locally. It should be documented, I hope?

[PokhodenkoSA]

I have created numba/numba-integration-testing#81 for this.