Closed miroi closed 9 years ago
Concerning the dllimport errors, I tried this hint, https://stackoverflow.com/questions/4644758/using-dllimport-procedure, but did not get it compiled anyhow....
@miroi I managed to compile on AppVeyor, some of the tests are broken. I have been working on the hotfix-appveyor branch and this is the latest (failing) build: https://ci.appveyor.com/project/robertodr/pcmsolver
It seems the --verbose
argument to ctest
is ignored on AppVeyor. I cannot thus gather more information from the CI workers on why the segfaults happen. Can you suggest a strategy to attack these problems?
Aaah...so you managed to make a complete build and run tests on appveyor ? Wau, I see https://ci.appveyor.com/project/robertodr/pcmsolver/build/job/dw7aisg6hhy35ry2
On my branch it failed last time on cmake-boost detection, but you overcome it, right ?
Myself, I can not compile PCMSolver on Windows Server, but appveyor worked did it. Good to know that there is a way to compile it on MS Windows !
Now the strategy: After https://github.com/PCMSolver/pcmsolver/blob/master/.appveyor.yml#L106 try to descend into directories of individual tests (build/test/....) and run execs individually. Maybe ill execs will flush out some traceback info.
Ah, here: https://github.com/PCMSolver/pcmsolver/blob/hotfix-appveyor/.appveyor.yml#L77
ctest -D ExperimentalConfigure -D ExperimentalBuild -D ExperimentalTest -D ExperimentalSubmit
Maybe we will see stderr+traceback on CDash ?
And appveyor.yml can be hidden (and functioning) as .appveyor.yml, right ?
I simplified the module quite a bit. I got rid of the dependency on compiled Boost libraries and removed all platform-dependent commands from the CMake scripts. I will play around with both your suggestions later tonight. Thanks! As a sidenote, the custom exception class is now gone and you might want to have a go again at the pure PGI build.
Yes you can choose whatever name for the YAML file in the project settings on AppVeyor.
Fine, I will try PGI set (pgf90,pgcc, pgCC) and XL (xlf90,xlcc,xlCC) sets.
Closing this and re-opening as "tests segfault"
Hi,
what could be be wrong please ?
The compilatio goes...