On Thu, Jun 21, 2012 at 04:36:15AM -0400, Jenkins oVirt Server wrote:
BUILD FAILURE Build URL: http://jenkins.ovirt.org/job/vdsm_unit_tests/222/ Project: vdsm_unit_tests Date of build: Thu, 21 Jun 2012 04:31:35 -0400 Build duration: 4 min 39 sec
CHANGE SET Revision 8d03cb7c11881ba0dedb2b22c7c136c8320611b2 by fsimonce: (Internal volumes must be RW in domain version <a href='http://bugzilla.redhat.com/show_bug.cgi?id=3'>3</a>) change: edit vdsm/storage/fileVolume.py change: edit vdsm/storage/misc.py change: edit vdsm/storage/volume.py change: edit vdsm/storage/hsm.py change: edit vdsm/storage/blockVolume.py Revision 4b1810bd728325aec4f38e406aab7a5fe54518e2 by fsimonce: (Move the SANLock SDM lease to a different offset) change: edit vdsm/storage/blockVolume.py change: edit vdsm/storage/safelease.py Revision d8b33031b4f20538be36f5d11156ea006e6e01e3 by fsimonce: (Add the hasHostId method to the cluster locks) change: edit vdsm/storage/sd.py change: edit vdsm/storage/safelease.py Revision 558edf6f2850ae37050a5ead87606a0e1d608869 by fsimonce: (Remove the traceback from the getVSize warning) change: edit vdsm/storage/blockVolume.py
JUNIT RESULTS
Error Message
No module named sanlock
Should we now even add sanlock-python to vdsm BuildRequires? It's is becoming a joke - we'd need all runtime packages in order to test vdsm during its build.
----- Original Message -----
From: "Dan Kenigsberg" danken@redhat.com To: "Eduardo Warszawski" ewarszaw@redhat.com, "Eyal Edri" eedri@redhat.com Cc: abaron@redhat.com, vdsm-patches@lists.fedorahosted.org, fsimonce@redhat.com Sent: Thursday, June 21, 2012 10:56:39 AM Subject: Re: [oVirt Jenkins] vdsm_unit_tests - Build # 222 - Still Failing!
On Thu, Jun 21, 2012 at 04:36:15AM -0400, Jenkins oVirt Server wrote:
BUILD FAILURE Build URL: http://jenkins.ovirt.org/job/vdsm_unit_tests/222/ Project: vdsm_unit_tests Date of build: Thu, 21 Jun 2012 04:31:35 -0400 Build duration: 4 min 39 sec
CHANGE SET Revision 8d03cb7c11881ba0dedb2b22c7c136c8320611b2 by fsimonce: (Internal volumes must be RW in domain version <a href='http://bugzilla.redhat.com/show_bug.cgi?id=3'>3</a>) change: edit vdsm/storage/fileVolume.py change: edit vdsm/storage/misc.py change: edit vdsm/storage/volume.py change: edit vdsm/storage/hsm.py change: edit vdsm/storage/blockVolume.py Revision 4b1810bd728325aec4f38e406aab7a5fe54518e2 by fsimonce: (Move the SANLock SDM lease to a different offset) change: edit vdsm/storage/blockVolume.py change: edit vdsm/storage/safelease.py Revision d8b33031b4f20538be36f5d11156ea006e6e01e3 by fsimonce: (Add the hasHostId method to the cluster locks) change: edit vdsm/storage/sd.py change: edit vdsm/storage/safelease.py Revision 558edf6f2850ae37050a5ead87606a0e1d608869 by fsimonce: (Remove the traceback from the getVSize warning) change: edit vdsm/storage/blockVolume.py
JUNIT RESULTS
Error Message
No module named sanlock
Should we now even add sanlock-python to vdsm BuildRequires? It's is becoming a joke - we'd need all runtime packages in order to test vdsm during its build.
Well... if you run vdsm (or part of it) during the build process then yes. :-(
I'll add the BuildRequires.
vdsm-patches@lists.fedorahosted.org