You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://anaconda.org/mantid/mantidimaging/files is showing a linux-64/mantidimaging-0.0.0-py38_1.tar.bz2 package built on 2022-03-29 and no other recent unstable builds. So probably the version number is not being set correctly in the builds from main.
After this mornings merge, the previous 0.0.0 package is gone and there is a new one with the date today.
In the older logs the version gets picked up from git describe here (for some reason the output shows before the commands)
2.4.0a1-58-g67d20792
On branch main
Your branch is up to date with 'origin/main'.
nothing to commit, working tree clean
checkout: 'HEAD'
==> /usr/bin/git log -n1 <==
==> /usr/bin/git describe --tags --dirty <==
==> /usr/bin/git status <==
first bad build is:
commit b4e79be6bee1f98eb699a41de2ba1af8c258ab7b
Author: rbauststfc <38210467+rbauststfc@users.noreply.github.com>
Date: Fri Mar 11 12:54:04 2022 +0000
Merge pull request #1368 from mantidproject/1338-actions-docs
Move doc building into its own workflow
On branch main
Your branch is up to date with 'origin/main'.
nothing to commit, working tree clean
checkout: 'HEAD'
==> /usr/bin/git log -n1 <==
==> /usr/bin/git describe --tags --dirty <==
==> /usr/bin/git status <==
I suspect its removing fetch-depth: 0 in #1368 that has caused the issue. Before we checked out the entire git history, not just the HEAD.
actions/checkout#217 devs are sticking with the decision to only checkout HEAD by default. To get the tags we either need extra fetch commands, or to go back to a full checkout fetch-depth: 0
Summary
https://anaconda.org/mantid/mantidimaging/files is showing a linux-64/mantidimaging-0.0.0-py38_1.tar.bz2 package built on 2022-03-29 and no other recent unstable builds. So probably the version number is not being set correctly in the builds from main.
After this mornings merge, the previous 0.0.0 package is gone and there is a new one with the date today.
Steps To Reproduce
Expected Behaviour
Current Behaviour
Context
Failure Logs
From the Actions build log
Screenshot(s)
The text was updated successfully, but these errors were encountered: