-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eicrecon-init.sh not correctly configured in Docker on Mac #1115
Comments
|
I'll try to run the inverse qemu emulation to see if I can reproduce, but don't get your hopes up :-) |
The only other issue in ROOT that refers to qemu was reported by me :-\ and it's different. |
Can reproduce on linux, docker, qemu within ROOT uses |
~~For the upstream ROOT bug report, you can probably use the docker image rootproject/root:6.28.04-fedora37 (which is arm64). https://hub.docker.com/r/rootproject/root/tags ~~ Edit: Nevermind, that image is a conda install which doesn't install |
That was a hell of a deep delve. Should I close the PR? While fixing it in root (which can take time) is better, my patch shouldn't hurt. That said, the bug itself probably only, if at all, manifests if you change root installations, be it inside eic-shell or outside AND in a weird shell. The outside part is hardest to predict off-hand, and it's unlikely to be a scenario for eic-recon often in the near future, but it's a consideration for jana2 maybe. |
Keep the PR open; it's the appropriate workaround now that we have identified what the cause it. We can merge it when you have submitted the issue to ROOT, and we'll keep track of that issue in EICrecon so we can back out the workaround again once a ROOT fix is available. |
@kkauder Can you post the link you the ROOT issue please? |
…sh" (#1111) ### Briefly, what does this PR introduce? Small fix to `pushd` and `popd` around `source thisroot.sh` ### What kind of change does this PR introduce? - [x] Bug fix (issue #1115 ) - [ ] New feature (issue #__) - [ ] Documentation update - [ ] Other: __ ### Please check if this PR fulfills the following: - [ ] Tests for the changes have been added - [ ] Documentation has been added / updated - [ ] Changes have been communicated to collaborators ### Does this PR introduce breaking changes? What changes might users need to make to their code? No. ### Does this PR change default behavior? It shouldn't.
Fixed by #1111 |
Environment: (where does this bug occur, have you tried other environments)
main
for latest released): mainHEAD
for the most recent on git): HEADSteps to reproduce: (give a step by step account of how to trigger the bug)
Expected Result: (what do you expect when you execute the steps above)
No output / correct execution
Actual Result: (what do you get when you execute the steps above)
Proposed Fix: #1111 (review)
The text was updated successfully, but these errors were encountered: