tests/octopus: convert to new stand-alone test process#38010
tests/octopus: convert to new stand-alone test process#38010tldahlgren wants to merge 3 commits intospack:developfrom
Conversation
|
@tldahlgren - thanks for advancing the testing framework. The new code looks nice. Initial feedback regarding the compilation failure (before the weekend, if that is helpful...): I think I managed to reproduce the compilation error you report above once but didn't record the process accurately, and can now not reproduce it. What I see is that compilation of octopus (without the When using the full command ( So my questions are: (i) does the compilation still fail for you? (ii) is the (implicit?) call of |
Running tests for hours isn't so good.
If I compile without
Yes, it is inherited behavior from You should be able to disable it by adding the self.build_time_test_callbacks = [] as shown for netpbm (as shown at https://github.com/spack/spack/blob/4c2531d5fbc2022dd144d1c59dd6faa7ce2c9607/var/spack/repos/builtin/packages/netpbm/package.py#LL162C15-L162C15).
|
b68b4ee to
a2a49e0
Compare
|
I marked this as Ready for Review though I am still getting the build error reported above. @fangohr @RemiLacroix-IDRIS Do you have recommendations for how I can build the package so I can test it? Or would you care to run the changes in this PR? |
|
Thanks @tldahlgren - sorry for dropping the ball on this. I don't know why the compilation fails for you, and it would be good of course to understand this. I can't look into this myself at the moment, but we have two options: (i) We have a CI like framework at https://github.com/fangohr/spack-ci-octopus where we build Octopus using Spack. We use a Debian-based Docker container. You can either use this as a recipe for succesfull compilation, or use the same environment as is to test your changes of this pull request. For the latter, the relevant target in the Makefile is probably (ii) @iamashwin99 may be able to help out (perhaps also using the above). The primary aim would be to see if this pull request works for Octopus. If, along the way, we can understand why the Octopus build fails on @tldahlgren Red Hat system, that would be nice, too! |
|
Hi @fangohr, |
Yes. I'm trying a newer compiler but running into issues. |
I run into a new problem when I constrain |
|
I see the string |
ad6dd3b to
cabb4c5
Compare
Helps in some respects but doesn't look like it is sufficient for me. (I iterated with initially using |
@tldahlgren can you post the complete stdout for reference spack -v install octopus%[email protected] ^openmpiUpdate: lets test with [email protected] as thats a well tested compiler with octopus |
Sure. spack-build-out.txt |
|
I can see that the complaint is from libtool not getting the path for libgd. -lyaml -L -lgd -lgd -lm -lz /bin/sh ../libtool --tag=CXX --mode=link SPACK_ROOT/lib/spack/env/gcc/g++ ........... -lyaml -L -lgd -lgd -lm -lzThis is passed in the if test "x$GD_LIBS" = x; then
GD_LIBS="-L`$GDLIB_CONFIG --libdir` -lgd `$GDLIB_CONFIG --ldflags` `$GDLIB_CONFIG --libs | awk '{if($NF=="@LIBICONV@"){$NF=""} print}'`"
# Sometimes GD installation strangely leaves this token @LIBICONV@ in --libs, which must be removed
fi
So somehow Nonetheless checking for gdlib-config... /usr/bin/gdlib-config
checking whether gdlib can be linked... yesIn case of a clean install on a debian docker image this dosent happen: checking for gdlib-config... noWe have two options to solve this:
|
|
Closing due to #45143 |
Converted tests to use new stand-alone test process.
Unfortunately, I cannot yet build the package:UPDATE:
According to
configure,gdlibcan be disabled so this PR also adds a variant so I can test the package again.Installing with the new variant:
And testing the above installation: