- Infra - oVirt List Archives

[JIRA] (OVIRT-1771) Build fail on fedora 26 - pip not found?
by Barak Korren (oVirt JIRA) 16 Nov '17

16 Nov '17

This is a multi-part message in MIME format... ------------=_1510844742-21379-429 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1771?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1771: ------------------------------------- On 16 November 2017 at 16:20, Nir Soffer <nsoffer(a)redhat.com> wrote: > We require python-pip for fedora 26: > > $ cat automation/check-patch.packages.fc26 > m2crypto > python-devel > python-pip > python-requests > python-six > python-webob > python3-devel > python3-requests > python3-six > python3-systemd > python3-webob > systemd-python > openssl > > > This is our check-patch.sh: > > $ cat automation/check-patch.sh > #!/bin/bash -xe > > # tox too old on EL, so we must install our own > pip install tox > > make > make check > > > But our check-patch.sh script fail on fedora 26: > > 00:01:31.612 ########################################################## > 00:01:31.638 ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv > 00:01:31.638 ##! Last 20 log entries: > ./mock_logs.HpHMYLVV/mocker-fedora-26-x86_64.fc26.check-patch.sh/check-patch.sh.log > 00:01:31.638 ##! > 00:01:31.729 ========== Running the shellscript automation/check-patch.sh > 00:01:31.729 + pip install tox > 00:01:31.729 ./automation/check-patch.sh: line 4: pip: command not found > 00:01:31.729 Took 0 seconds > 00:01:31.729 =================================== > 00:01:31.729 ##! > 00:01:31.729 ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… > > This use to work in last few month, started to break today. > > Any clue what can be the issue? Probably something was changed upstream, perhaps its not called 'python-pip' any more? I'll need to find the specific build where the failed environment was created to know for sure. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > Build fail on fedora 26 - pip not found? > ---------------------------------------- > > Key: OVIRT-1771 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1771 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > We require python-pip for fedora 26: > $ cat automation/check-patch.packages.fc26 > m2crypto > python-devel > python-pip > python-requests > python-six > python-webob > python3-devel > python3-requests > python3-six > python3-systemd > python3-webob > systemd-python > openssl > This is our check-patch.sh: > $ cat automation/check-patch.sh > #!/bin/bash -xe > # tox too old on EL, so we must install our own > pip install tox > make > make check > But our check-patch.sh script fail on fedora 26: > *00:01:31.612* ##########################################################*00:01:31.638* > ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv*00:01:31.638* ##! > Last 20 log entries: > ./mock_logs.HpHMYLVV/mocker-fedora-26-x86_64.fc26.check-patch.sh/check-patch.sh.log*00:01:31.638* > ##!*00:01:31.729* ========== Running the shellscript > automation/check-patch.sh*00:01:31.729* + pip install > tox*00:01:31.729* ./automation/check-patch.sh: line 4: pip: command > not found*00:01:31.729* Took 0 seconds*00:01:31.729* > ===================================*00:01:31.729* ##!*00:01:31.729* > ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… > This use to work in last few month, started to break today. > Any clue what can be the issue? > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071) ------------=_1510844742-21379-429 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1771?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1771:</h3> <p>On 16 November 2017 at 16:20, Nir Soffer <nsoffer(a)redhat.com> wrote:</p> <blockquote><p>We require python-pip for fedora 26:</p> <p>$ cat automation/check-patch.packages.fc26 m2crypto python-devel python-pip python-requests python-six python-webob python3-devel python3-requests python3-six python3-systemd python3-webob systemd-python openssl</p> <p>This is our check-patch.sh:</p> <p>$ cat automation/check-patch.sh #!/bin/bash -xe</p> <p># tox too old on EL, so we must install our own pip install tox</p> <p>make make check</p> <p>But our check-patch.sh script fail on fedora 26:</p> <p>00:01:31.612 ########################################################## 00:01:31.638 ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv 00:01:31.638 ##! Last 20 log entries: ./mock_logs.HpHMYLVV/mocker-fedora-26-x86_64.fc26.check-patch.sh/check-patch.sh.log 00:01:31.638 ##! 00:01:31.729 ========== Running the shellscript automation/check-patch.sh 00:01:31.729 + pip install tox 00:01:31.729 ./automation/check-patch.sh: line 4: pip: command not found 00:01:31.729 Took 0 seconds 00:01:31.729 =================================== 00:01:31.729 ##! 00:01:31.729 ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^</p> <p><a href="http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…">http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…</a></p> <p>This use to work in last few month, started to break today.</p> <p>Any clue what can be the issue?</p></blockquote> <p>Probably something was changed upstream, perhaps its not called ‘python-pip’ any more?</p> <p>I'll need to find the specific build where the failed environment was created to know for sure.</p> <p>— Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted</p> <blockquote><h3>Build fail on fedora 26 – pip not found?</h3> <pre> Key: OVIRT-1771 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1771 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra</pre> <p>We require python-pip for fedora 26: $ cat automation/check-patch.packages.fc26 m2crypto python-devel python-pip python-requests python-six python-webob python3-devel python3-requests python3-six python3-systemd python3-webob systemd-python openssl This is our check-patch.sh: $ cat automation/check-patch.sh #!/bin/bash -xe # tox too old on EL, so we must install our own pip install tox make make check But our check-patch.sh script fail on fedora 26: <strong>00:01:31.612</strong> ##########################################################*00:01:31.638* ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv*00:01:31.638* ##! Last 20 log entries: ./mock_logs.HpHMYLVV/mocker-fedora-26-x86_64.fc26.check-patch.sh/check-patch.sh.log*00:01:31.638* ##!*00:01:31.729* ========== Running the shellscript automation/check-patch.sh*00:01:31.729* + pip install tox*00:01:31.729* ./automation/check-patch.sh: line 4: pip: command not found*00:01:31.729* Took 0 seconds*00:01:31.729* ===================================*00:01:31.729* ##!*00:01:31.729* ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ <a href="http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…">http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…</a> This use to work in last few month, started to break today. Any clue what can be the issue?</p> <pre>Nir</pre></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1510844742-21379-429--

1 0

[oVirt Jenkins] ovirt-appliance_ovirt-4.1-pre_build-artifacts-el7-x86_64 - Build # 118 - Failure!
by jenkins＠jenkins.phx.ovirt.org 16 Nov '17

16 Nov '17

------=_Part_331_1627625805.1510832569984 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-pre_build-artifacts-… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-pre_build-artifacts-… Build Number: 118 Build Status: Failure Triggered By: Started by user Lev Veyde ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #118 [Daniel Belenky] Added dparth(a)redhat.com to the whitelist [Roy Golan] Add performance suite to the choices of manual job [Barak Korren] Remove node-filter definitions for vdsm jobs [Juan Hernandez] Use oVirt version for names of metamodel jobs [Dafna Ron] Dropping support for FC23 [Yuval Turgeman] automation: view install log in console ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_331_1627625805.1510832569984--

1 1

[CQ]: 83717,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 16 Nov '17

16 Nov '17

Change 83717,3 (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/83717/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3887/

1 0

[JIRA] (OVIRT-1771) Build fail on fedora 26 - pip not found?
by Nir Soffer (oVirt JIRA) 16 Nov '17

16 Nov '17

This is a multi-part message in MIME format... ------------=_1510842149-12055-403 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Nir Soffer created OVIRT-1771: --------------------------------- Summary: Build fail on fedora 26 - pip not found? Key: OVIRT-1771 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1771 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra We require python-pip for fedora 26: $ cat automation/check-patch.packages.fc26 m2crypto python-devel python-pip python-requests python-six python-webob python3-devel python3-requests python3-six python3-systemd python3-webob systemd-python openssl This is our check-patch.sh: $ cat automation/check-patch.sh #!/bin/bash -xe # tox too old on EL, so we must install our own pip install tox make make check But our check-patch.sh script fail on fedora 26: *00:01:31.612* ##########################################################*00:01:31.638* ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv*00:01:31.638* ##! Last 20 log entries: ./mock_logs.HpHMYLVV/mocker-fedora-26-x86_64.fc26.check-patch.sh/check-patch.sh.log*00:01:31.638* ##!*00:01:31.729* ========== Running the shellscript automation/check-patch.sh*00:01:31.729* + pip install tox*00:01:31.729* ./automation/check-patch.sh: line 4: pip: command not found*00:01:31.729* Took 0 seconds*00:01:31.729* ===================================*00:01:31.729* ##!*00:01:31.729* ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… This use to work in last few month, started to break today. Any clue what can be the issue? Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071) ------------=_1510842149-12055-403 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Nir Soffer created OVIRT-1771:</h3> <pre> Summary: Build fail on fedora 26 - pip not found? Key: OVIRT-1771 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1771 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra</pre> <p>We require python-pip for fedora 26:</p> <p>$ cat automation/check-patch.packages.fc26 m2crypto python-devel python-pip python-requests python-six python-webob python3-devel python3-requests python3-six python3-systemd python3-webob systemd-python openssl</p> <p>This is our check-patch.sh:</p> <p>$ cat automation/check-patch.sh #!/bin/bash -xe</p> <p># tox too old on EL, so we must install our own pip install tox</p> <p>make make check</p> <p>But our check-patch.sh script fail on fedora 26:</p> <p><strong>00:01:31.612</strong> ##########################################################*00:01:31.638* ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv*00:01:31.638* ##! Last 20 log entries: ./mock_logs.HpHMYLVV/mocker-fedora-26-x86_64.fc26.check-patch.sh/check-patch.sh.log*00:01:31.638* ##!*00:01:31.729* ========== Running the shellscript automation/check-patch.sh*00:01:31.729* + pip install tox*00:01:31.729* ./automation/check-patch.sh: line 4: pip: command not found*00:01:31.729* Took 0 seconds*00:01:31.729* ===================================*00:01:31.729* ##!*00:01:31.729* ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^</p> <p><a href="http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…">http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…</a></p> <p>This use to work in last few month, started to break today.</p> <p>Any clue what can be the issue?</p> <pre>Nir</pre> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1510842149-12055-403--

1 0

[JIRA] (OVIRT-1770) Build on fedora 26 fails, accessing console log extremely slow
by Nir Soffer (oVirt JIRA) 16 Nov '17

16 Nov '17

This is a multi-part message in MIME format... ------------=_1510841668-15493-416 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Nir Soffer created OVIRT-1770: --------------------------------- Summary: Build on fedora 26 fails, accessing console log extremely slow Key: OVIRT-1770 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1770 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra I wait forever for this url: http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… here example: $ time curl http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… > /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 103k 0 103k 0 0 4814 0 --:--:-- 0:00:22 --:--:-- 23562 real 0m22.107s user 0m0.005s sys 0m0.009s Can we fix to be less then a second? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071) ------------=_1510841668-15493-416 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Nir Soffer created OVIRT-1770:</h3> <pre> Summary: Build on fedora 26 fails, accessing console log extremely slow Key: OVIRT-1770 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1770 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra</pre> <p>I wait forever for this url: <a href="http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…">http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…</a></p> <p>here example:</p> <p>$ time curl <a href="http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…">http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…</a></p> <blockquote><p>/dev/null</p></blockquote> <pre>% Total % Received % Xferd Average Speed Time Time Time</pre> <p>Current</p> <pre>Dload Upload Total Spent Left</pre> <p>Speed 100 103k 0 103k 0 0 4814 0 --:--:-- 0:00:22 --:--:-- 23562</p> <p>real 0m22.107s user 0m0.005s sys 0m0.009s</p> <p>Can we fix to be less then a second?</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1510841668-15493-416--

1 0

Build on fedora 26 fails, accessing console log extremely slow
by Nir Soffer 16 Nov '17

16 Nov '17

I wait forever for this url: http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… here example: $ time curl http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… > /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 103k 0 103k 0 0 4814 0 --:--:-- 0:00:22 --:--:-- 23562 real 0m22.107s user 0m0.005s sys 0m0.009s Can we fix to be less then a second?

1 0

[JIRA] (OVIRT-1769) run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility
by Barak Korren (oVirt JIRA) 16 Nov '17

16 Nov '17

This is a multi-part message in MIME format... ------------=_1510838318-17486-395 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1769 at 11/16/17 1:18 PM: --------------------------------------------------------------- You can`t run a '*-4.1' suit on 'master' code, the final part of the suit name determines which code it tests... Instead, a new suit should be composed of the necessary parts in other suits. Since suites are mostly just sets of symlinks into a pool of shared files, this is not hard to do. I suppose the new suit could be called something like 'compat-suit-master' was (Author: bkorren(a)redhat.com) You can`t run a '*-4.1' suit on 'master' code, the final part of the suit name determines which code it tests... instead I new suit should be composed of the necessary parts in other suits. Since suites are mostly just sets of symlinks into a pool of shared files, this is not hard to do. I suppose the new suit could be called something like 'compat-suit-master' > run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility > ----------------------------------------------------------------------------------- > > Key: OVIRT-1769 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1769 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > starting with basic-suite-4.2, we port test cases to sdk4. That's good, since that's the future of the project. > However, as long as we promise backward compatibility for sdk3, we need to make sure it does not break. This can be done by running basic-suite-4.1 tests on code of ovirt-master. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071) ------------=_1510838318-17486-395 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren edited comment on OVIRT-1769 at 11/16/17 1:18 PM:</h3> <p>You can`t run a ‘*-4.1’ suit on ‘master’ code, the final part of the suit name determines which code it tests… Instead, a new suit should be composed of the necessary parts in other suits. Since suites are mostly just sets of symlinks into a pool of shared files, this is not hard to do. I suppose the new suit could be called something like ‘compat-suit-master’</p> <p>was (Author: bkorren(a)redhat.com) You can`t run a ‘*-4.1’ suit on ‘master’ code, the final part of the suit name determines which code it tests… instead I new suit should be composed of the necessary parts in other suits. Since suites are mostly just sets of symlinks into a pool of shared files, this is not hard to do. I suppose the new suit could be called something like ‘compat-suit-master’</p> <blockquote><h3>run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility</h3> <pre> Key: OVIRT-1769 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1769 Project: oVirt - virtualization made easy Issue Type: New Feature Components: OST Reporter: danken Assignee: infra Priority: High</pre> <p>starting with basic-suite-4.2, we port test cases to sdk4. That's good, since that's the future of the project. However, as long as we promise backward compatibility for sdk3, we need to make sure it does not break. This can be done by running basic-suite-4.1 tests on code of ovirt-master.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1510838318-17486-395--

1 0

[JIRA] (OVIRT-1769) run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility
by Barak Korren (oVirt JIRA) 16 Nov '17

16 Nov '17

This is a multi-part message in MIME format... ------------=_1510838253-23453-415 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1769: -------------------------------- Epic Link: OVIRT-400 > run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility > ----------------------------------------------------------------------------------- > > Key: OVIRT-1769 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1769 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > starting with basic-suite-4.2, we port test cases to sdk4. That's good, since that's the future of the project. > However, as long as we promise backward compatibility for sdk3, we need to make sure it does not break. This can be done by running basic-suite-4.1 tests on code of ovirt-master. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071) ------------=_1510838253-23453-415 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1769:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility</h3> <pre> Key: OVIRT-1769 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1769 Project: oVirt - virtualization made easy Issue Type: New Feature Components: OST Reporter: danken Assignee: infra Priority: High</pre> <p>starting with basic-suite-4.2, we port test cases to sdk4. That's good, since that's the future of the project. However, as long as we promise backward compatibility for sdk3, we need to make sure it does not break. This can be done by running basic-suite-4.1 tests on code of ovirt-master.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1510838253-23453-415--

1 0

[JIRA] (OVIRT-1769) run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility
by Barak Korren (oVirt JIRA) 16 Nov '17

16 Nov '17

This is a multi-part message in MIME format... ------------=_1510838252-25756-414 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1769: -------------------------------- Epic Link: OVIRT-400 > run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility > ----------------------------------------------------------------------------------- > > Key: OVIRT-1769 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1769 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > starting with basic-suite-4.2, we port test cases to sdk4. That's good, since that's the future of the project. > However, as long as we promise backward compatibility for sdk3, we need to make sure it does not break. This can be done by running basic-suite-4.1 tests on code of ovirt-master. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071) ------------=_1510838252-25756-414 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1769:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility</h3> <pre> Key: OVIRT-1769 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1769 Project: oVirt - virtualization made easy Issue Type: New Feature Components: OST Reporter: danken Assignee: infra Priority: High</pre> <p>starting with basic-suite-4.2, we port test cases to sdk4. That's good, since that's the future of the project. However, as long as we promise backward compatibility for sdk3, we need to make sure it does not break. This can be done by running basic-suite-4.1 tests on code of ovirt-master.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1510838252-25756-414--

1 0

[JIRA] (OVIRT-1769) run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility
by Barak Korren (oVirt JIRA) 16 Nov '17

16 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1769: ------------------------------------- You can`t run a '*-4.1' suit on 'master' code, the final part of the suit name determines which code it tests... instead I new suit should be composed of the necessary parts in other suits. Since suites are mostly just sets of symlinks into a pool of shared files, this is not hard to do. I suppose the new suit could be called something like 'compat-suit-master' > run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility > ----------------------------------------------------------------------------------- > > Key: OVIRT-1769 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1769 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > starting with basic-suite-4.2, we port test cases to sdk4. That's good, since that's the future of the project. > However, as long as we promise backward compatibility for sdk3, we need to make sure it does not break. This can be done by running basic-suite-4.1 tests on code of ovirt-master. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)

1 0