CI: run database tests only #39550

[fangchenli]

• closes CI: have database builds *just* run db tests #39550
• closes CI: remove the current coverage build, run coverage on multiple builds instead #39758

[jreback]

hmm maybe its the db - cov build that is a problem. i guess any way to split up these cov builds? (this might be harder, as now we would have multiple uploads to code-cov, but also maybe unavoidable)

[fangchenli]

hmm maybe its the db - cov build that is a problem. i guess any way to split up these cov builds? (this might be harder, as now we would have multiple uploads to code-cov, but also maybe unavoidable)

https://docs.codecov.io/docs/merging-reports Codecov automatically merges multiple reports. So we don't even need a separate build for coverage. We could select a set of builds that include all tests, run coverage, and upload reports for all of them.

[jreback]

hmm maybe its the db - cov build that is a problem. i guess any way to split up these cov builds? (this might be harder, as now we would have multiple uploads to code-cov, but also maybe unavoidable)

https://docs.codecov.io/docs/merging-reports Codecov automatically merges multiple reports. So we don't even need a separate build for coverage. We could select a set of builds that include all tests, run coverage, and upload reports for all of them.

that would be great! (but should tag the builds as -cov just to indicate that they are part of the coverage build(s))

[fangchenli]

I probably won't have time to work on the coverage stuff in the next couple of days. I opened #39758. So people can take from there.

[MarcoGorelli]

Hi @fangchenli - in #39758 you wrote

and remove the actions-37-cov build if it's no longer required.

but here it looks like you're keeping it - is it still required then?

[fangchenli]

One of the db builds is testing the minimum support versions of SQL-related packages. So I think it's better to keep both of them. But should rename them to reflect their actual purpose.

[jreback]

thanks @fangchenli very nice