[JIRA] (OVIRT-2566) make network suite blocking
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jir... ]
Barak Korren edited comment on OVIRT-2566 at 9/1/19 7:52 AM:
-------------------------------------------------------------
Not for specific patches - but we can easily enable it for ALL patches.
If we only want it for specific patches - we can consider allowing some customization of the Zull configuration at project level to allow running specific suits for specific patches, but this will require some code changes in several places. We can plan this once we're in production with the current set of suits.
was (Author: bkorren(a)redhat.com):
Not for specific patches - but we can enable it for ALL patches.
We can consider allowing some customization of the Zull configuration at project level to allow running specific suits for specific patches, but this will require some code changes in several places. We can plan this once we're in production with the current set of suits.
> make network suite blocking
> ---------------------------
>
> Key: OVIRT-2566
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: OST
> Reporter: danken
> Assignee: infra
> Priority: High
>
> The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives.
> Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug.
> https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te...
> I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested".
> [~gbenhaim(a)redhat.com], what should be done to make this happen?
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100108)
5 years, 2 months
[JIRA] (OVIRT-2566) make network suite blocking
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-2566:
-------------------------------------
Not for specific patches - but we can enable it for ALL patches.
We can consider allowing some customization of the Zull configuration at project level to allow running specific suits for specific patches, but this will require some code changes in several places. We can plan this once we're in production with the current set of suits.
> make network suite blocking
> ---------------------------
>
> Key: OVIRT-2566
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: OST
> Reporter: danken
> Assignee: infra
> Priority: High
>
> The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives.
> Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug.
> https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te...
> I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested".
> [~gbenhaim(a)redhat.com], what should be done to make this happen?
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100108)
5 years, 2 months
Fwd: Zuul posts non hiddable Gerrit comments
by Barak Korren
What is out current plan for upgrading to Gerrit 2.15+ ?
As you can see below one of the nice features it provides, is the ability
to hide auto-generated comments from the UI. This will allow use to
de-clutter the comment lists on patches making them easier to track and
read.
---------- Forwarded message ---------
From: Vitaliy Lotorev <lotorev(a)gmail.com>
Date: Fri, 30 Aug 2019 at 01:01
Subject: Zuul posts non hiddable Gerrit comments
To: <zuul-discuss(a)lists.zuul-ci.org>
Hi,
Starting with at least v2.15 Gerrit is able to differentiate bot comments
and hide them using 'Show comments' trigger on web UI. This is achived
either using tagged comments or robot comments.
A while ago I filed an issue about Zuul not using these technics [1]
(ticket has links for Gerrit docs with tagged and robot comments). This
results that Zuul comments are not hiddable in Gerrit.
AFAIK, sending tagged comments via SSH to Gerrit is easy (one-line of code
at [2]).
I could try providing a patch for tagged comments.
What Zuul maintainers think about adding support for bot comments?
Should not be sending tagged comments done only if Gerrit version >= 2.15?
[1] https://storyboard.openstack.org/#!/story/2005661
[2]
https://opendev.org/zuul/zuul/src/branch/master/zuul/driver/gerrit/gerrit...
_______________________________________________
Zuul-discuss mailing list
Zuul-discuss(a)lists.zuul-ci.org
http://lists.zuul-ci.org/cgi-bin/mailman/listinfo/zuul-discuss
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
5 years, 2 months
[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build
# 179 - Failure!
by jenkins＠jenkins.phx.ovirt.org
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/179/
Build Number: 179
Build Status: Failure
Triggered By: Started by timer
-------------------------------------
Changes Since Last Success:
-------------------------------------
Changes for Build #179
[edwardh(a)redhat.com] network, ovirtlib: Expose the root system through sdkentity
-----------------
Failed Tests:
-----------------
1 tests failed.
FAILED: 004_basic_sanity.ha_recovery_43
Error Message:
False != True after 600 seconds
-------------------- >> begin captured logging << --------------------
lago.ssh: DEBUG: start task:8157f6f9-b4f5-4fab-a887-59883a5e5d7c:Get ssh client for lago-compat-4-3-suite-master-host-0:
lago.ssh: DEBUG: end task:8157f6f9-b4f5-4fab-a887-59883a5e5d7c:Get ssh client for lago-compat-4-3-suite-master-host-0:
lago.ssh: DEBUG: Running 875bc492 on lago-compat-4-3-suite-master-host-0: pgrep -f qemu.*guest=vm2
lago.ssh: DEBUG: Command 875bc492 on lago-compat-4-3-suite-master-host-0 returned with 0
lago.ssh: DEBUG: Command 875bc492 on lago-compat-4-3-suite-master-host-0 output:
7527
lago.ssh: DEBUG: start task:2e248e1c-b036-4229-815a-596bfb0cf343:Get ssh client for lago-compat-4-3-suite-master-host-0:
lago.ssh: DEBUG: end task:2e248e1c-b036-4229-815a-596bfb0cf343:Get ssh client for lago-compat-4-3-suite-master-host-0:
lago.ssh: DEBUG: Running 87fafbc0 on lago-compat-4-3-suite-master-host-0: kill -KILL 7527
lago.ssh: DEBUG: Command 87fafbc0 on lago-compat-4-3-suite-master-host-0 returned with 0
--------------------- >> end captured logging << ---------------------
Stack Trace:
File "/usr/lib64/python2.7/unittest/case.py", line 369, in run
testMethod()
File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test
test()
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper
return func(get_test_prefix(), *args, **kwargs)
File "/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/004_basic_sanity.py", line 725, in ha_recovery
lambda:
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 286, in assert_true_within_long
assert_equals_within_long(func, True, allowed_exceptions)
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 273, in assert_equals_within_long
func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 252, in assert_equals_within
'%s != %s after %s seconds' % (res, value, timeout)
'False != True after 600 seconds\n-------------------- >> begin captured logging << --------------------\nlago.ssh: DEBUG: start task:8157f6f9-b4f5-4fab-a887-59883a5e5d7c:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: end task:8157f6f9-b4f5-4fab-a887-59883a5e5d7c:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: Running 875bc492 on lago-compat-4-3-suite-master-host-0: pgrep -f qemu.*guest=vm2\nlago.ssh: DEBUG: Command 875bc492 on lago-compat-4-3-suite-master-host-0 returned with 0\nlago.ssh: DEBUG: Command 875bc492 on lago-compat-4-3-suite-master-host-0 output:\n 7527\n\nlago.ssh: DEBUG: start task:2e248e1c-b036-4229-815a-596bfb0cf343:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: end task:2e248e1c-b036-4229-815a-596bfb0cf343:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: Running 87fafbc0 on lago-compat-4-3-suite-master-host-0: kill -KILL 7527\n\nlago.ssh: DEBUG: Command 87fafbc0 on lago-compat-4-3-suite-master-host-0 returned with 0\n--------------------- >> end captured logging << ---------------------'
5 years, 2 months
