- Infra - oVirt List Archives

[CQ]: 88292, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88292,5 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 87766,3 (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 87766,3 (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/88292/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87766/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5978/

1 0

[CQ]: 87749, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

A system test invoked by the "ovirt-master" change queue including change 87749,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87902,10 (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 87902,10 (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/87749/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87902/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5974/

1 0

[CQ]: 88318, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88318,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87902,10 (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 87902,10 (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/88318/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87902/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5969/

1 0

[CQ]: 88065, 9 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88065,9 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87902,10 (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 87902,10 (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/88065/9 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87902/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5966/

1 0

[CQ]: 87117,1 (ioprocess) failed "ovirt-4.2" system tests
by oVirt Jenkins 01 Mar '18

01 Mar '18

Change 87117,1 (ioprocess) is probably the reason behind recent system test failures in the "ovirt-4.2" 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/87117/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/987/

1 0

[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Yaniv Kaul (oVirt JIRA) 01 Mar '18

01 Mar '18

This is a multi-part message in MIME format... ------------=_1519916823-27449-246 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plug… ] Yaniv Kaul commented on OST-99: ------------------------------- I think it'd be easier to start with running those tests from the Engine VM, though I really like the containers idea - if it works well, we can probably use container for other areas as well (storage !). I would not start with the container just because it'll offset us from our main goal of getting the UI automation in. > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OST-99 > URL: https://ovirt-jira.atlassian.net/browse/OST-99 > Project: oVirt system tests > Issue Type: Improvement > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1519916823-27449-246 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plug… ]</pre> <h3>Yaniv Kaul commented on OST-99:</h3> <p>I think it'd be easier to start with running those tests from the Engine VM, though I really like the containers idea – if it works well, we can probably use container for other areas as well (storage !).</p> <p>I would not start with the container just because it'll offset us from our main goal of getting the UI automation in.</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OST-99 URL: https://ovirt-jira.atlassian.net/browse/OST-99 Project: oVirt system tests Issue Type: Improvement Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1519916823-27449-246--

1 0

[CQ]: 88330, 1 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

A system test invoked by the "ovirt-4.2" change queue including change 88330,1 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 88299,1 (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 88299,1 (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/88330/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88299/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/980/

1 0

[CQ]: 88104, 7 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88104,7 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 87766,3 (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 87766,3 (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/88104/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87766/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5962/

1 0

[CQ]: 88072, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88072,5 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 87766,3 (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 87766,3 (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/88072/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87766/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5959/

1 0

[CQ]: 88063, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88063,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 87766,3 (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 87766,3 (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/88063/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87766/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5955/

1 0