visit: add v3.5.0 - #6161
Conversation
41d7c4f to
8fc71a6
Compare
|
One challenge is that VisIt 3.5.0 uses Qt6, and the Qt spack packages were refactored into smaller packages starting with Qt6 -- due to the modular changes between Qt5 and Qt6 |
72e122b to
da16186
Compare
|
@cyrush CI passed! 🎉 |
|
Oh wow, how do we see the results of those visit builds? |
Good catch, the changes in the deps made the concretizer to prefer visit 3.4.1 which in turn resulted in no new builds. I am temporarily forcing visit 3.5.0 in the dav-sdk stack to test this new version. |
f1ee584 to
118fc2c
Compare
|
Looks like HDF5 API compatibility issue. VisIt is setting the API version explicitly here, duplicate of the command line we use but that should be ok. |
We should probably do that anyway, older versions of VTK are going to get removed before long and that means most of the versions of VisIt will also have to go. Forcing the latest is not a bad idea, at very least it will keep testing the VTK upper bound for VisIt in CI. |
Thanks for pointing this out, how did you get this errors? in the CI job it says: |
912b41a to
b27f255
Compare
You can get the full logs from the artifacts under Here is the full log of the latest failure. This looks like the signature for |
VVolumePlot is only created when the viewer/GUI components are built, but plots/Volume/CMakeLists.txt unconditionally references it in vtk_module_autoinit, breaking ~gui builds of visit@3.5:.
b27f255 to
e5f5a14
Compare
No description provided.