# Issues with Catalyst 2.0 Installation & Failing Tests (ctest)
**URL:** https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107
**Category:** In Situ Support
**Tags:** catalyst
**Created:** [February 4, 2025, 9:01pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107 "2025-02-04T21:01:41Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@Bhavesh](https://discourse.paraview.org/u/Bhavesh)
#### Post date: [February 4, 2025, 9:01pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/1 "2025-02-04T21:01:41Z")
Hi everyone,
I am trying to install **Catalyst 2.0** and run `ctest`, but I am encountering **multiple test failures**. I have followed the official documentation:
đź”— [Catalyst 2.0 Build & Install Guide](https://catalyst-in-situ.readthedocs.io/en/latest/build_and_install.html)
#### **System Information:**
- **OS:** Windows 11
- **ParaView Version:** 5.12.1
- **Python Version:** 3.13.1
- **CMake Version:** 3.31.4
- **Ninja Version:** Latest via `winget install Ninja-build.Ninja`
- **Compilers:** GCC 14.2.0 (from MSYS2)
* * *
### **Installation Process I Followed:**
1. **Created 3 directories:**
2. **Ran CMake (Inside `catalyst-build/`):**
3. **Ran Ninja Build & Install:**
4. **Ran Tests Using CTest:**
* * *
I got the following output when I ran `ctest`.
```auto
The following tests FAILED:
4 - example-build-about (Failed)
6 - example-install-about (Failed)
8 - example-build-adaptor0 (Failed)
10 - example-install-adaptor0 (Failed)
12 - example-build-replay (Failed)
14 - example-install-replay (Failed)
17 - catalyst-abi-nm (Failed)
18 - catalyst-impl-double (Failed)
19 - catalyst-results (Failed)
21 - catalyst-impl-external-conduit (Failed)
22 - catalyst-impl-internal-conduit (Failed)
23 - test_conduit_import_python (Failed) Python
24 - test_catalyst_import_python (Failed) Python
25 - test_double_impl_python (Failed) Python
26 - t_conduit_node (Failed)
35 - test-build-replay_high_num_execute_invc (Failed)
37 - test-install-replay_high_num_execute_invc (Failed)
43 - test-build-replay_missing_initialize_data (Failed)
45 - test-install-replay_missing_initialize_data (Failed)
47 - test-build-replay_missing_execute_invc (Failed)
49 - test-install-replay_missing_execute_invc (Failed)
51 - test-build-replay_high_num_execute_invc_python (Failed)
53 - test-install-replay_high_num_execute_invc_python (Failed)
55 - test-build-replay_no_data_dump_dir_python (Failed)
57 - test-install-replay_no_data_dump_dir_python (Failed)
59 - test-build-replay_missing_initialize_data_python (Failed)
61 - test-install-replay_missing_initialize_data_python (Failed)
63 - test-build-replay_missing_execute_invc_python (Failed)
65 - test-install-replay_missing_execute_invc_python (Failed)
Errors while running CTest
Output from these tests are in: C:/Users/bhave/OneDrive/Documents/Catalyst/catalyst-build/Testing/Temporary/LastTest.log
```
I have added `catalyst-build/bin` to `PATH`.
Attached is the `LastTest.log` file which contains the verbose of all the test cases.
[LastTest.log](https://discourse.paraview.org/uploads/short-url/tbdKTkgVp4ibGjMc0x2Wu0BlBJd.log) (3.2 MB)
I would really appreciate any insights from the community on how to fix all these errors. Let me know if you need more information!
Thanks,
Bhavesh
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [February 26, 2025, 3:44pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/2 "2025-02-26T15:44:50Z")
It looks like this is a debug build. I see `d` suffixes on the DLLs that probably need accounted for.
---
### Author:  [@Bhavesh](https://discourse.paraview.org/u/Bhavesh)
#### Post date: [February 26, 2025, 7:37pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/3 "2025-02-26T19:37:30Z")
Yes indeed. The default `CMAKE_BUILD_TYPE` is `Debug`. I didn’t specify anything unique, so the default value was used.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [February 26, 2025, 8:23pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/4 "2025-02-26T20:23:41Z")
Looks like we should add a CI test for that.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [February 26, 2025, 8:36pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/5 "2025-02-26T20:36:47Z")
Adding it here: [https://gitlab.kitware.com/paraview/catalyst/-/merge\_requests/126](https://gitlab.kitware.com/paraview/catalyst/-/merge_requests/126)
---
### Author:  [@Bhavesh](https://discourse.paraview.org/u/Bhavesh)
#### Post date: [February 26, 2025, 8:50pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/6 "2025-02-26T20:50:08Z")
So what should I do now to fix my problems? Even with the `ctest` errors, I tried to proceed and run the `CxxFullExampleV2` example from [Getting Started — ParaView Documentation 5.12.0 documentation](https://docs.paraview.org/en/latest/Catalyst/getting_started.html#prerequisites).
I even followed the suggestions from these forum posts:
- [how to run CatalystV2 examples on Windows](https://discourse.paraview.org/t/how-to-run-catalystv2-examples-on-windows/9519)
- [Paraview Catalyst on Windows](https://discourse.paraview.org/t/paraview-catalyst-on-windows/15450)
I have set the following environment variables:
- `CATALYST_IMPLEMENTATION_PATHS` to `C:\Program Files\ParaView 5.13.25022\bin\catalyst-paraview.dll`
- `CATALYST_IMPLEMENTATION_NAME` to `paraview`
Despite this, I’m still seeing the `Failed to initialize Catalyst: 3` error.
---
### Author:  [@Bhavesh](https://discourse.paraview.org/u/Bhavesh)
#### Post date: [February 26, 2025, 8:51pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/7 "2025-02-26T20:51:05Z")
I even changed my `CMAKE_BUILD_TYPE` to `Release` (while building and installing catalyst), but still encountering the same errors and problems.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [February 26, 2025, 9:04pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/8 "2025-02-26T21:04:36Z")
A Windows Debug build is certainly not going to work until that MR lands. As for using Release…make sure things actually got rebuilt? “3” means that the implementation was not found. There is the `CATALYST_DEBUG=1` environment variable you can set that can help inform what `libcatalyst` is doing.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [February 26, 2025, 10:01pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/9 "2025-02-26T22:01:06Z")
Hmm. It looks like I already fixed it a while ago. Python support is still untested as our Python lacks the `_d` versions of libraries. What version of `libcatalyst` are you using?
---
### Author:  [@gsabhishek](https://discourse.paraview.org/u/gsabhishek)
#### Post date: [February 27, 2025, 10:04am UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/10 "2025-02-27T10:04:21Z")
CATALYST\_IMPLEMENTATION\_PATHS should be just `C:\Program Files\ParaView 5.13.25022\bin\`
Also you may need to prepend the path `C:\Program Files\ParaView 5.13.25022\bin\` to the system PATH.
---
### Author:  [@Bhavesh](https://discourse.paraview.org/u/Bhavesh)
#### Post date: [February 27, 2025, 7:39pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/11 "2025-02-27T19:39:02Z")
I am using the latest version of `libcatalyst`, which is available [here](https://catalyst-in-situ.readthedocs.io/en/latest/build_and_install.html).
---
### Author:  [@Bhavesh](https://discourse.paraview.org/u/Bhavesh)
#### Post date: [February 27, 2025, 7:39pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/12 "2025-02-27T19:39:32Z")
I updated `CATALYST_IMPLEMENTATION_PATHS` like you said and got the following output:
```catalyst
catalyst debug: implementation name from `catalyst_load/implementation`: paraview
catalyst debug: search path from `catalyst_load/search_paths`: ``
catalyst debug: search paths from `CATALYST_IMPLEMENTATION_PATHS`
WRN - The configuration file has not been found, using default parameters.
catalyst debug: trying to load `C:\Program Files\ParaView 5.13.25022\bin\/catalyst-paraview.dll`: valid
catalyst debug: loaded implementation: 00007ffd1b9c8000
```
So clearly, the errors about `Failed to initialize Catalyst: 3` are gone, but nothing happens after this command. I don’t see anything new popping up or any simulation running.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [March 3, 2025, 9:17pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/13 "2025-03-03T21:17:17Z")
Ok, so it is finding the DLL now at least. I’m not sure where that `WRN` line comes from; I don’t see the text in VTK or ParaView.
@Christos_Tsolakis Thoughts here?
---
### Author:  [@Christos\_Tsolakis](https://discourse.paraview.org/u/Christos_Tsolakis)
#### Post date: [March 3, 2025, 10:33pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/14 "2025-03-03T22:33:03Z")
The `WRN` error is indeed strange.
Is this the output of `CxxFullExampleV2` ?
Are you passing the default script to `CxxFullExampleV2` ?
---
### Author:  [@Bhavesh](https://discourse.paraview.org/u/Bhavesh)
#### Post date: [March 3, 2025, 10:35pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/15 "2025-03-03T22:35:13Z")
I don’t think that the `WRN` is an error, so to say.
This is the output of running `.\bin\CxxFullExampleV2 catalyst_pipeline.py`.
---
### Author:  [@Christos\_Tsolakis](https://discourse.paraview.org/u/Christos_Tsolakis)
#### Post date: [March 3, 2025, 10:43pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/16 "2025-03-03T22:43:09Z")
> [@Bhavesh](#):
>
> I don’t think that the `WRN` is an error, so to say.
That’s correct, but this warning does not come from ParaView or catalyst from what I can see. So it is strange that it is there.
> This is the output of running `.\bin\CxxFullExampleV2 catalyst_pipeline.py`.
This looks right. Does the issue happen will other examples as well ?
Can you try this `https://gitlab.kitware.com/paraview/paraview/-/tree/master/Examples/Catalyst2/CxxImageDataExample`
The setup should be the similar.
---
### Author:  [@Christos\_Tsolakis](https://discourse.paraview.org/u/Christos_Tsolakis)
#### Post date: [March 3, 2025, 10:45pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/17 "2025-03-03T22:45:57Z")
> That’s correct, but this warning does not come from ParaView or catalyst from what I can see. So it is strange that it is there.
Not directly related to the problem. But it looks like using paraview can indeed cause this warning. [https://open.cdash.org/tests/1904815534](https://open.cdash.org/tests/1904815534)
---
### Author:  [@Bhavesh](https://discourse.paraview.org/u/Bhavesh)
#### Post date: [March 4, 2025, 8:56pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/18 "2025-03-04T20:56:55Z")
I tried the example you mentioned but got the same output. Do you think it has something to do with `stub` implementation or something? I was just looking up other forum posts, so thought so.
---
### Author:  [@Christos\_Tsolakis](https://discourse.paraview.org/u/Christos_Tsolakis)
#### Post date: [March 4, 2025, 10:23pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/19 "2025-03-04T22:23:38Z")
The stub implementation is the default one that indeed produces no results.
But these lines :
```auto
catalyst debug: implementation name from `catalyst_load/implementation`: paraview
...
catalyst debug: trying to load `C:\Program Files\ParaView 5.13.25022\bin\/catalyst-paraview.dll`: valid
```
show that you are using the ParaView implementation. So you should see the script executed.
Not sure what is going wrong here…
---
### Author:  [@Christos\_Tsolakis](https://discourse.paraview.org/u/Christos_Tsolakis)
#### Post date: [March 4, 2025, 10:29pm UTC](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107/20 "2025-03-04T22:29:06Z")
I just looked back in the ctest errors you get. It looks like `PYTHONPATH` is not properly set up.
Can you trying building catalyst with `-DCATALYST_WRAP_PYTHON=OFF`. Do the catalyst tests succeed in this case ?
[Next page](https://discourse.paraview.org/t/issues-with-catalyst-2-0-installation-failing-tests-ctest/16107.md?page=2)