Repository navigation
ci: pin EoSim to a tag that exists - #95
Merged
srpatcha merged 2 commits intoSep 1, 2026
Merged
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Contributor
Author
|
Stacked on #66. The red/queued checks were
#66 fixes both. |
Kartikey1306
force-pushed
the
fix/eosim-sanity-real-tag
branch
from
September 1, 2026 07:12
f3c99ff to
224a1a0
Compare
EoSim Sanity has never had a green run in this repository. EOSIM_VERSION is
"0.1.0" and embeddedos-org/EoSim has no such tag -- its tags run v1.0.0 through
v3.0.1 -- so every job dies at the clone:
fatal: Remote branch v0.1.0 not found in upstream origin
and then, predictably, at the install:
ERROR: file:///tmp/EoSim does not appear to be a Python project:
neither 'setup.py' nor 'pyproject.toml' found
The second message is a red herring: the directory is empty because the clone
failed, not because EoSim is not a Python project. It is one -- v1.5.0 carries
a pyproject.toml declaring name = "eosim" with a console entry point.
Pinned to v1.5.0, the release marked Latest. Verified by doing exactly what the
workflow does:
git clone --depth 1 --branch v1.5.0 .../EoSim.git /tmp/EoSim
pip install /tmp/EoSim -> rc=0
eosim --version -> eosim, version 2.0.0
eosim list -> rc=0
eosim doctor -> rc=0
Those four are every EoSim command this workflow invokes.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Kartikey1306
force-pushed
the
fix/eosim-sanity-real-tag
branch
from
September 1, 2026 09:39
224a1a0 to
de9df40
Compare
srpatcha
previously approved these changes
Sep 1, 2026
Kartikey1306
dismissed
srpatcha’s stale review
September 1, 2026 10:13
The merge-base changed after approval.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
EoSim Sanityhas never had a green run in this repository. It is a nightly workflow, so it does not gate pull requests — it is simply red every morning.The cause
EOSIM_VERSIONis"0.1.0", andembeddedos-org/EoSimhas no such tag. Its tags runv1.0.0throughv3.0.1:The second message is a red herring that makes this look like an EoSim packaging problem. The directory is empty because the clone failed — EoSim is a perfectly normal Python project, and
v1.5.0carries apyproject.tomldeclaringname = "eosim"with a console entry point.Pinned to v1.5.0, the release marked Latest.
Verified, not assumed
I ran exactly what the workflow runs:
Those four are every EoSim command this workflow invokes.
One caveat worth recording
eosim listprintsAvailable platforms (0)whilediscover_platforms()on the same directory returns 149 — a display bug inside EoSim, not something this workflow can fix. It exits 0, so the sanity steps pass either way. Flagging it rather than leaving it to surprise the next person.