Conversation
|
@nimgould thank you very much for the fixes, the latest change to the sifdecoder bash script seems to require that absolute paths to SIF files are passed to |
|
Yes, this is intentional, we say that the SIF file should either be in the current directory, or the SIF repository (aka MASTSIF). The test options in the makemaster version change directory to $(SIFDECODE)/sif before running tests, I presume that meson could copy (or link) the SIF files if this is not possible? |
|
I also notice that there were many lines saying tput: No value for $TERM and no -T specified in the actions test output. I have no idea where this comes from |
|
Excellent thank you, yes I can change the CI tests to cd into $(SIFDECODE)/sif, will do that now. Regarding the "no value for $TERM" I have already fixed this by setting TERM=xterm. This is a strange CI issue. |
|
Perfect, let's see if the tests now complete |
|
I should clarify that what seems to have broken is that the sifdecoder bash script is no longer looking for SIF files in |
|
Is $(SIFDECODE) being set? |
|
Yes the CI scripts currently set: which are all the correct paths to where the CI installs things. |
|
Well that is mighty odd, but it also seems to happen to me locally ... % sifdecoder ROSENBR ERROR: file ROSENBR.SIF is not known in directories % ls $MASTSIF/ROSENBR.SIF I will put on my cape and deerstalker, and examine with a large magnifying glass ... |
|
Thank you, also any chance we could add a |
|
OK, fixed, done and pushed |
|
Wonderful thank you, closing this pull request as it is no longer required. |
No description provided.