-2451cac6751a] could you please
confirm what the exact issue is described in this ticket? Do I understand
correctly that CI is implicitly including repos into the environment that are
newer than what’s needed?
> Fwd: manual system test runner bro
Sandro Bonazzola created OVIRT-2838:
---
Summary: Fwd: manual system test runner broken
Key: OVIRT-2838
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2838
Project: oVirt - virtualization made easy
On Tue, 19 Nov 2019 at 12:31, Sandro Bonazzola wrote:
>
>
> Il giorno mar 19 nov 2019 alle ore 11:02 Barak Korren
> ha scritto:
>
>> The fallback is defined in the reposync file of the suit - the option in
>> the job that talks about this does nothing AFAIK. If the non-default value
>> is
Il giorno mar 19 nov 2019 alle ore 11:02 Barak Korren
ha scritto:
> The fallback is defined in the reposync file of the suit - the option in
> the job that talks about this does nothing AFAIK. If the non-default value
> is selected it tries to add the non existent `experimental` repo to
>
The fallback is defined in the reposync file of the suit - the option in
the job that talks about this does nothing AFAIK. If the non-default value
is selected it tries to add the non existent `experimental` repo to
extra_sources. We should probably just drop that option from the Job GUI.
On Tue,
Hi,
just executed basic suite for testing 4.3.7 rc4 and instead of falling back
on latest released it was falling back on latest tested which is newer than
4.3.7 rc4 so made the test useless.
Job execution is here:
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6071/
who's maintaining
