Please read and adhere to the contribution guidelines.
Please tick the following:
https://github.com/SyneRBI/SIRF-SuperBuild/pull/989
(1 file)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@paskino pushed 2 commits.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@paskino pushed 1 commit.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@paskino pushed 2 commits.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@paskino pushed 1 commit.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
The residual error in the DEVEL_BUILD is TORCH_TEST_PYTHON
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
It's strange that we don't get any output that says what the failure. we just have
CoverageWarning: Module sirf.torch was never imported. (module-not-imported);
but that could be irrelevant, as the coverage stuff is broken since a few years.
On the other hand, this is the DEVEL_BUILD=OFF build (with g++11), while all others are fine. So, I wonder if we shouldn't be updating the SIRF_TAG.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
No, that's the DEVEL_BUILD=ON
So currently
DEVEL_BUILD |
TAG |
|---|---|
OFF |
SyneRBI/SIRF@11a6a50 |
ON |
master |
This means that only the DEVEL_BUILD=ON runs unit tests with PyTorch.
It also means that we need to change the SIRF_TAG to nearly master, or whatever commit we want to tag as v3.10.0.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@paskino pushed 1 commit.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
That's what I meant... Good luck!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@paskino pushed 3 commits.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@casperdcl commented on this pull request.
> + # TODO fix PyTorch unittest + # set (DEFAULT_SIRF_TAG origin/master)⬇️ Suggested change
- # TODO fix PyTorch unittest - # set (DEFAULT_SIRF_TAG origin/master) + set (DEFAULT_SIRF_TAG origin/master)
> @@ -162,6 +162,7 @@ set(DEFAULT_JSON_URL https://github.com/nlohmann/json) set(DEFAULT_JSON_TAG v3.11.3) # CCPi CIL +# test different branch of CIL to test fix⬇️ Suggested change
-# test different branch of CIL to test fix
In CHANGES.md:
> @@ -1,8 +1,11 @@ # ChangeLog ## v3.X.x +- CMake: + - Patch ISMRMRD CMakeLists.txt to set(CMAKE_INSTALL_RPATH_USE_LINK_PATH TRUE) (#)⬇️ Suggested change
- - Patch ISMRMRD CMakeLists.txt to set(CMAKE_INSTALL_RPATH_USE_LINK_PATH TRUE) (#) + - Patch ISMRMRD `CMAKE_INSTALL_RPATH_USE_LINK_PATH` (#991)
In CHANGES.md:
> - Updated versions: - SIRF-Contribs: v3.9.1 + - SIRF: 4198e7f17ef17ff8b1913e20d1db3e7c9383d4da both for default and devel #2026-03-12⬇️ Suggested change
- - SIRF: 4198e7f17ef17ff8b1913e20d1db3e7c9383d4da both for default and devel #2026-03-12 + - SIRF: 4198e7f17ef17ff8b1913e20d1db3e7c9383d4da (2026-03-12)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@paskino pushed 1 commit.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@casperdcl commented on this pull request.
> + # TODO fix PyTorch unittest + # set (DEFAULT_SIRF_TAG origin/master)
@paskino this causes a unittest fail though. I suppose we should merge anyway and tackle #992 separately?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@casperdcl approved this pull request.
we'll tackle #992 separately
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()