On 03/12/2015 23:52, Jonathon A Anderson wrote:
We�ve been using pyslurm[1] in our cluster performance regression testing
suite; but it seems to have broken with our most recent slurm upgrade. (We get
a segmentation fault from pyslurm.node()) This isn�t terribly surprising, as
we were already hacking the build system[2] to build against a higher version
than the developer had tested against.
I�d love to contribute, but I don�t have any experience with cython, or
with the slurm C api. If upstream slurm changes are likely to break pyslurm,
though, we might have to move away from it if we can�t support it ourselves.
That is, unless schedmd might be willing to start contributing to it? Or to
provide a different python api into slurm.
Is anyone else using pyslurm? Or any other python api into slurm that I might
not know about? What�s the chance that schedmd might assist in keeping
pyslurm up-to-date with slurm releases?
~jonathon
[1]: https://github.com/gingergeeks/pyslurm
[2]: setup.py
Jonathon,
I have seen you're ticket and I apologise for the lack of
activity but I've been a tad busy before taking my Christmas break. Now
that I'm on vacation until the new year I will now have time to look at
the issue. I run different versions/builds of Slurm with different
versions of PySlurm in my test VM and have assisted a number of people
recently with similar issues. Some are traced to the OS python
environment/compiler and more recently one was traced to the method a
package had been installed.
I'm very happy if SchedMd or someone else wishes to create a new
Slurm-Python API. The current API was the result of a one hour hack for
something that had to be done very quickly and so is certainly not the
code I would have liked it to be.
Best Regards
Mark
