Closed rbberger closed 1 year ago
@Yurlungur Unlike ports-of-call
, this repo has a GitLab pipeline that pulls in its doc dependencies via Spack. But I might still remove the +doc
variant in the public facing Spack package in upstream.
Assume this is for the header-only version of ports-of-call with portability strategy removed?
@Yurlungur Unlike ports-of-call, this repo has a GitLab pipeline that pulls in its doc dependencies via Spack. But I might still remove the +doc variant in the public facing Spack package in upstream.
I'm in favor of this. Let's just remove the doc build from the gitlab workflow, since github is building for us
@Yurlungur Yes, please see my comment in the re-git
instance. It does come with a cost, not sure how important that other pages instance is.
@Yurlungur the GitHub action failure seems to be caused by a newer ubuntu image that now uses GCC 11.3 instead of 9.4.0
@Yurlungur Updating the Catch2 dependency fixed the issue. Also cleaned up the broken submodule state (.gitmodules
entry was ignored, since the folder wasn't commited anymore)
PR Summary
ports-of-call
spackagepy-sphinx-multiversion
spackage, which is no longer needed since the testing upstream is now v0.18ports-of-call
that select aportability_strategy
+cuda_constexpr
for+kokkos+cuda
PR Checklist