Replies: 4 comments
-
Do you happen to be building with the docker image? I've never used the build container, but I seem to recall some discussion saying that it can cause problems with the ref - hopefully someone else can chime in with more info. Perhaps try on baremetal / WSL / VM if you haven't already? I've never not had it populated (baremetal Linux build) |
Beta Was this translation helpful? Give feedback.
-
Hmm I'm not building with the docker image, I'm manually |
Beta Was this translation helpful? Give feedback.
-
Actually no that was wrong, the last few builds have been from the Github CI. I can see in the build logs that the ref is already empty when it logs the build configuration, which is also the case for builds on the main InfiniTime branch. I tried to check the logs for the latest release build, but unfortunately those have expired and are no longer available. This is actually consistent with builds on the InfiniTime repo as well. Installing a build from a commit from the main branch also does not have the short ref filled. I think probably because of this:
I might be able to fix that. |
Beta Was this translation helpful? Give feedback.
-
Made a pr: #2282 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey,
I have a fork of InfiniTime with a few changes of my own. For some reason, the ShortRef in the firmware validation screen is empty for these builds.
How do I get this to show the actual commit it was built with? It would be very useful to have this as a reference when creating issues.
Beta Was this translation helpful? Give feedback.
All reactions