Daniel Arndt

> I guess one of the next steps would be to work on the CMake such that our Tpetra interface is happy once Tpetra, Amesos2, Belos, Ifpack2 and MueLu are...

We might just disable the respective since `HPX` throws its own exceptions by using `std::set_new_handler` (or try to catch that exception and throw our own).

> Where can I see the actual runtime error generated by HPX, btw? https://github.com/kokkos/kokkos/actions/runs/10834072931/job/30062369318?pr=7331 has > [ RUN ] hpx.view_bad_alloc terminate called after throwing an instance of 'hpx::detail::exception_with_info' what(): new...

> Ok, this is something else, then. Why is a handler set by `std::set_new_handler` invoked in this case to begin with? It seems https://github.com/llvm/llvm-project/blob/82a36468c74a29b6154639d659550c62457e655b/libcxx/src/new.cpp#L162-L166 is executed but we don't hit...

Note that we already have a HPX build in our CI that I would expect to reproduce the issue if we update the HPX version there, see https://github.com/kokkos/kokkos/blob/b5509ab14f760769446ab0710dca88483eebce22/.github/workflows/continuous-integration-workflow-hpx.yml#L37-L42.

> @masterleinad `github-Linux-hpx` works, but the build with the `hpx-devel` package on Fedora fails. Not sure if it is worth digging, but the fedora build logs are here: Interesting. I...

> @masterleinad @hkaiser any update or patch to try? No, I think we need someone to dedicate some time to understand the root cause why the compiler even calls the...

@diehlpk Can you try to have a look at this?

> Now we are getting: We just forgot to guard this test properly for deprecated code. Disabling deprecation warnings or warnings as errors (or deleting the test) is a easy...

> I am a little confused why the `linux-x64-hpx` test didn't catch that. That build has `-DKokkos_ENABLE_DEPRECATED_CODE_4=OFF`.