A system test invoked by the "ovirt-master" change queue including change
109022,1 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 108909,9 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.
This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 108909,9 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.
For further details about the change see:
https://gerrit.ovirt.org/#/c/109022/1
For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/108909/9
For failed test results see:
https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23689/
A system test invoked by the "ovirt-4.3" change queue including change 109019,2
(ovirt-engine) failed. However, this change seems not to be the root cause for
this failure. Change 109003,1 (ovirt-engine) that this change depends on or is
based on, was detected as the cause of the testing failures.
This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 109003,1 (ovirt-engine) is
fixed and this change is updated to refer to or rebased on the fixed version,
or this change is modified to no longer depend on it.
For further details about the change see:
https://gerrit.ovirt.org/#/c/109019/2
For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/109003/1
For failed test results see:
https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3428/
A system test invoked by the "ovirt-4.3" change queue including change 109002,1
(ovirt-engine) failed. However, this change seems not to be the root cause for
this failure. Change 109003,1 (ovirt-engine) that this change depends on or is
based on, was detected as the cause of the testing failures.
This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 109003,1 (ovirt-engine) is
fixed and this change is updated to refer to or rebased on the fixed version,
or this change is modified to no longer depend on it.
For further details about the change see:
https://gerrit.ovirt.org/#/c/109002/1
For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/109003/1
For failed test results see:
https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3426/
Change 108909,9 (vdsm) is probably the reason behind recent system test
failures in the "ovirt-master" change queue and needs to be fixed.
This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.
For further details about the change see:
https://gerrit.ovirt.org/#/c/108909/9
For failed test results see:
https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23683/
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2940?page=com.atlassian.jir... ]
Ehud Yonasi commented on OVIRT-2940:
------------------------------------
Thanks for reporting Nir,
You are right about the timeout - but that exists only during the actual
code. In this case the slave was
somehow out of storage / memory and it stuck during loading our stdci code.
> Stuck job - running 8 days
> --------------------------
>
> Key: OVIRT-2940
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2940
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Nir Soffer
> Assignee: infra
>
> I found this stuck job in jenkins:
> https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/5660/
> Don't we have a timeout for killing run away jobs?
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100126)
Nir Soffer created OVIRT-2940:
---------------------------------
Summary: Stuck job - running 8 days
Key: OVIRT-2940
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2940
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Nir Soffer
Assignee: infra
I found this stuck job in jenkins:
https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/5660/
Don't we have a timeout for killing run away jobs?
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100126)
Change 109003,1 (ovirt-engine) is probably the reason behind recent system test
failures in the "ovirt-4.3" change queue and needs to be fixed.
This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.
For further details about the change see:
https://gerrit.ovirt.org/#/c/109003/1
For failed test results see:
https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3425/
A system test invoked by the "ovirt-4.3" change queue including change 108995,1
(ovirt-system-tests) failed. However, this change seems not to be the root
cause for this failure. Change 108880,7 (ovirt-system-tests) that this change
depends on or is based on, was detected as the cause of the testing failures.
This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 108880,7 (ovirt-system-tests)
is fixed and this change is updated to refer to or rebased on the fixed
version, or this change is modified to no longer depend on it.
For further details about the change see:
https://gerrit.ovirt.org/#/c/108995/1
For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/108880/7
For failed test results see:
https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3423/