Closed oharboe closed 1 year ago
@jerryz123 FYI
Have you updated your submodules after bumping chipyard? If not, can you rerun scripts/init-submodules-no-riscv-tools.sh
again in the root of your repo?
Have you updated your submodules after bumping chipyard? If not, can you rerun
scripts/init-submodules-no-riscv-tools.sh
again in the root of your repo?
Same result.
Can you run git status
in the root of your repo and paste the output here?
Can you run
git status
in the root of your repo and paste the output here?
Running git status
and git submodule foreach git status
and cleaning out everything and checking out latest origin/main and making sure that scripts/init-submodules-no-riscv-tools.sh
ran without errors fixed it.
Thanks!
Background Work
Chipyard Version and Hash
Release: 1.0.0-2839-g73efea08 Hash: 8b6adb1525625f3b5bc0cfe84b79a99822e1ef85
OS Setup
Ex: Output of
uname -a
+lsb_release -a
+printenv
+conda list
Other Setup
Ex: Prior steps taken / Documentation Followed / etc...
Current Behavior
This used to work, on latest main, it fails.
Bisection result, eb3a0aecf4fe7ad2d382318e5d56da4162c5c2da is the first bad commit
Expected Behavior
No error
Other Information
No response