Re: [arts-users] 52% of CTEST fails during ARTS compilation

Hi Oliver, Thanks for the link to the arts-xml-data. It certainly made a big difference, let alone its size from 327 Mb (my 5 year old one) to 3.23 Gb (the latest). "make check" results reproduce exactly what you described - only one error from "TestSpectroscopy.arts". Now I can be sure that my

Re: [arts-users] 52% of CTEST fails during ARTS compilation

Hi Richard, As mentioned, I've used Homebrew GCC , not OSX native LLVM/Clang compiler. It's not clear the GCC supports "FASTWIGNER" option, but I went for it b'cause of OpenMP support. I wish my report contains deeper investigations on well-known bug(s).

Re: [arts-users] 52% of CTEST fails during ARTS compilation

Hi Reno, > On 9 Oct 2020, at 09:56, Reno Choi wrote: > > Hi Oliver, > > Many thanks for the prompt response. Sounds like it's CTEST, not a compile > process. > > I followed your 1st test and showed 3 tests failed out of 71, > > 66 - arts.ctlfile.fast.artscomponents.helpers.TestRegridding

Re: [arts-users] 52% of CTEST fails during ARTS compilation

Hi Reno, A quick glance at your building procedure. It seems like you are pointing against a very old version of arts-xml-data. Can you confirm that it is the latest arts-xml-data from the dev-branch that you have got there? Because the files should be there in the development branch. Also, I

Re: [arts-users] 52% of CTEST fails during ARTS compilation

Hi Reno, It looks like all the Python related tests are failing. This is currently a flaw in our build setup when calling 'ctest' manually. It circumvents the dependency tracking of 'make' and doesn't trigger the conversion of the controlfiles to Python. Try to use the provided check targets