-
Notifications
You must be signed in to change notification settings - Fork 2
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
Notebooks env patch #149
Notebooks env patch #149
Conversation
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferencesYou may notice some variations in coverage metrics with the latest Coverage engine update. For more details, visit the documentation |
Pull Request Test Coverage Report for Build 7426831220
💛 - Coveralls |
At least one Lammps job in the deepdive is crashing. Here's the tail of the errors:
|
Same error. It's in this cell, the first one where wf.register("pyiron_atomistics", "pyiron_workflow.node_library.pyiron_atomistics")
wf.register("plotting", "pyiron_workflow.node_library.plotting")
wf = Workflow("with_prebuilt")
wf.structure = wf.create.pyiron_atomistics.Bulk(cubic=True, name="Al")
wf.engine = wf.create.pyiron_atomistics.Lammps(structure=wf.structure)
wf.calc = wf.create.pyiron_atomistics.CalcMd(job=wf.engine)
wf.plot = wf.create.plotting.Scatter(
x=wf.calc.outputs.steps,
y=wf.calc.outputs.temperature
)
out = wf.run()
out.plot__fig It runs totally fine on my machine, and a quick human comparison shows no difference in the env (doesn't mean it's not there, just not in the packages I peeked at). |
I took a closer look and my graphviz (certainly not an issue since the visualization cells are fine) and numpy (potentially an issue but seems unlikely) packages are out of date on my local env. My more thorough search showed everything else lining up fine -- in particular my local env has the same |
Nope, updated those two and it's still fine locally. The head of the error stack is in
So it really looks like a lammps executable crash but why? |
127 is that the command could not be found. Indeed, in my local env's directory |
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferencesYou may notice some variations in coverage metrics with the latest Coverage engine update. For more details, visit the documentation |
Even pyiron-data 0.0.24, which was the first one I used has run_lammps_2020.03.03.sh, so I'm super confused why the executable is being not found |
I wondered if somehow the resource path is broken, but I modified the notebook to show me the resource paths before crashing and they look totally fine:
|
I couldn't even get things working over in #150 where I specified old versions of stuff. I updated everything in my local env and find I can still run the deepdive notebook without trouble. Forget spot-checking suspect packages, I copied the entire environment being installed here, and the entire environment on my local machine, and used some python to compare all the packages that are installed in both locations but don't have the same version. It is few: PACKAGE LOCAL REMOTE
widgetsnbextension 3.6.1 4.0.9
jupyterlab 3.5.3 4.0.10
graphviz 9.0.0 8.1.0
ipywidgets 7.7.1 8.1.1
pyiron-data 0.0.27 0.0.26
notebook 6.5.4 7.0.6
jupyterlab_widgets 1.1.2 3.0.9 For completeness I'm going to bump |
Well, that is good but extremely frustrating. I have no idea why pyiron-data works with both 0.0.26 and 0.0.27 locally, but requires 0.0.27 on the CI. |
And updating the atomistics notebook to use the new API.
Basically a manual version of what should be automated, as discussed in #148