Closed vkarak closed 3 months ago
Strange, I can't reproduce it. Back to triage.
I was trying with a stable version; you need a development version.
Although we do change to the installation prefix, the problem arises if this prefix is inside another (unrelated) Git working tree at any level deep as git rev-parse
will still find the working tree.
It's easy to reproduce:
pip
:pip3 install git+https://github.com/reframe-hpc/reframe.git@develop
reframe -V
You will see the hash of the local repo's HEAD being attached to reframe's version.
We should check that the
reframe.INSTALL_PREFIX
is indeed a Git repo before callinggit rev-parse
to get the hash:https://github.com/reframe-hpc/reframe/blob/8395b49dc86c2a57a21ee6a3285950fde089c69b/reframe/utility/osext.py#L709-L714