I doubt it's an overload Jenkins slave.
We recently increased the number of slaves to over 200 and there is only one job running on a slave at a given time.
If you see evidence of slave misbehaving please open a ticket in jira so Infra team can investigate.
On 10/11/16 15:43 +0200, Nir Soffer wrote:
On Thu, Nov 10, 2016 at 3:39 PM, Piotr Kliczewski
<piotr.kliczewski@gmail.com> wrote:
All,
Few mins ago I saw build [1] failure due to:
13:36:42 ERROR: test_abort_during_copy('block')
(storage_sdm_copy_data_test.TestCopyDataDIV)
13:36:42 ------------------------------------------------------------ ----------
13:36:42 Traceback (most recent call last):
13:36:42 File
"/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/ vdsm/tests/testlib.py",
line 133, in wrapper
13:36:42 return f(self, *args)
13:36:42 File
"/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/ vdsm/tests/storage_sdm_copy_da ta_test.py",
line 279, in test_abort_during_copy
13:36:42 raise RuntimeError("Timeout waiting for thread")
13:36:42 RuntimeError: Timeout waiting for thread
Adam, can you take a look?
Is this happening all of the time or intermittently? If intermittent
then we can increase the timeout or just ignore for the time being
since it's probably caused by an overloaded Jenkins slave.
--
Adam Litke
_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel