Testing third party libraries

[jeanlucf22]

We sometimes encounter failures due to problems in third-party libraries (not compiled properly, out of date,...). Tracking down these issues can take a lot of time.

To improve the situation, it would be nice to have some extras tests that test these third party libraries upfront and report issues right away, including performance issues.

[nicolasbock]

Let's start by compiling a list of those third-party libraries. That would make it easier to design and implement tests.

[jeanlucf22]

I would start with MAGMA, which has already caused us some trouble...

[nicolasbock]

Does the test pipeline you run via GitLab have access to GPUs? If it does then we could add tests that are run only there and not on GitHub.

[jeanlucf22]

Yes, it does run GPU.
BTW, we already have one test like that for OpenMP offload:

bml/tests/C-tests/CMakeLists.txt

Line 3 in 0619203

if(BML_OMP_OFFLOAD)

[nicolasbock]

Do you then basically just have to run a test in GitLab with OMP offload enabled?

[jeanlucf22]

All it does it run an extra test when BML_OMP_OFFLOAD=1 (on gitlab or not). This test is checking that compiler is actually offloading to GPU.
In the same way, we could have a test for MAGMA when MAGMA is ON.

[github-actions]

This issue is stale because it has been open for 90 days with no activity. Remove the stale label or comment or this will be closed in 30 days.

[github-actions]

This issue is stale because it has been open for 90 days with no activity. Remove the stale label or comment or this will be closed in 30 days.

[github-actions]

This issue is stale because it has been open for 90 days with no activity. Remove the stale label or comment or this will be closed in 30 days.

[jeanlucf22]

PR #741 is the fist step with magma.