On Tue, Sep 03, 2019 at 10:23:08AM -0400, Cole Robinson wrote: > > Traceback (most recent call last): > > File "/home/jenkins/build/libvirt/lib64/python3.7/site-packages/libvirt.py", line 24, in <module> [snip] > Anyone know what's going on here? I don't think this is virt-manager's > fault. > > The console output from the latest libvirt-python build: > https://ci.centos.org/job/libvirt-python-build/685/systems=libvirt-fedora-rawhide/console > > Shows libvirt.py and libvirtmod.py being put into > /home/jenkins/build/libvirt/lib64/python3.8/site-packages , but the > above traceback indicates there's a libvirt.py in > /home/jenkins/build/libvirt/lib64/python3.7/site-packages (3.8 vs 3.7). > Maybe there's stale libvirt.py in the rawhide image? The PYTHONPATH env var (and all other env vars) are set at the OS level which means they are fixed at the time the jenkins slave starts. We periodically upgrade RPMs via dnf, and this time python got upgraded to 3.8. The slave's PYTHONPATH still says 3.7 though. I'll reboot the VM to fix it shortly. Really we should be setting all build related env vars in the job script, so that they are guaranteed accurate when each job runs. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
