exemple of output after change:
```
$./totest-manager.py --dry --debug run Factory:PowerPC 2>&1
2018-11-05 09:59:23,874 - totest-manager:299 INFO job
opensuse-Tumbleweed-DVD-ppc64-Build-RAID5@ppc64 failed, but was ignored
2018-11-05 09:59:24,069 - totest-manager:299 INFO job
opensuse-Tumbleweed-DVD-ppc64-Build-RAID10@ppc64 failed, but was ignored
2018-11-05 09:59:24,259 - totest-manager:299 INFO job
opensuse-Tumbleweed-DVD-ppc64le-Build-extra_tests_in_textmode@ppc64le
failed, but was ignored
2018-11-05 09:59:24,480 - totest-manager:299 INFO job
opensuse-Tumbleweed-DVD-ppc64le-Build-gnome@ppc64le failed, but was
ignored
2018-11-05 09:59:24,679 - totest-manager:311 INFO job
opensuse-Tumbleweed-DVD-ppc64le-Build-extra_tests_on_gnome@ppc64le
failed, see https://openqa.opensuse.org/tests/781048
2018-11-05 09:59:25,104 - totest-manager:524 INFO current_snapshot
20181022: failed
2018-11-05 09:59:25,104 - totest-manager:525 DEBUG new_snapshot 20181101
2018-11-05 09:59:25,104 - totest-manager:526 DEBUG current_qa_version
20181022
2018-11-05 09:59:28,686 - totest-manager:529 DEBUG snapshotable: True
2018-11-05 09:59:28,927 - totest-manager:580 DEBUG No ttm_amqp_url
configured in oscrc - skipping amqp event emission
2018-11-05 09:59:29,210 - totest-manager:549 DEBUG totest already
publishing
2018-11-05 09:59:29,210 - totest-manager:482 INFO Updating snapshot
20181101
2018-11-05 09:59:29,210 - totest-manager:465 INFO release
openSUSE:Factory:PowerPC/000product:openSUSE-ftp-ftp-ppc64_ppc64le
(None)
2018-11-05 09:59:29,210 - totest-manager:465 INFO release
openSUSE:Factory:PowerPC/000product:openSUSE-dvd5-dvd-ppc64le
(Snapshot20181101)
2018-11-05 09:59:29,210 - totest-manager:465 INFO release
openSUSE:Factory:PowerPC/000product:openSUSE-cd-mini-ppc64le
(Snapshot20181101)
```
TODO: is is sufficient to have ppc64 (BE) iso build failure
to be ignored by OBS as per bug 1112920
https://bugzilla.suse.com/show_bug.cgi?id=1112920
and continue to submit ppc64le isos to be submitted to openQA and
released independently from ppc64 ?
Signed-off-by: Michel Normand <normand@linux.vnet.ibm.com>
The LiveCD products (JeOS) for ARM will never follow
the same iso build numbers (and don't produce iso's to begin with)
than the main project. In lack of a "ignore mismatch for livecd
products only" option we just skip the syncing globally. that should
be fine as hopefully the main products always produce the same build.
As the remote config is no longer optional for SLE and is utilized by
openSUSE to the point were it is dangerous not to load the remote config
it should be required. Currently only certain users call apply_remote()
while this will make it built-in during construction and thus makes the
usage consistent and no longer require StagingAPI.
In order to release the live images for Factory:ARM we need
to check if they finished building. Currently JeOS is multibuild
for armv7l and aarch64 but the main package is just building for armv7l,
so thats what we check for now. Without this change it was checking
for the default architectures (i586, x86_64) which did never pass.
Right now we require a Staging subproject to use staging plugin, which
is suboptimal especially for maintenance requests. The OBS attributes allow
to store the things right attached to the project - and the permissions
can be controlled in parallel to the maintainers right, which gives us
enough freedom
for openqa_group def in ToTest150Ports class
Required to avoid bad makeurl generated string.
TODO: Next action will be to determine how to handle
ppc64le in same project but different repo (images_ppc)
main_products = [
'000product:openSUSE-cd-mini-aarch64',
'000product:openSUSE-dvd5-dvd-aarch64',
+ '000product:openSUSE-cd-mini-ppc64le',
+ '000product:openSUSE-dvd5-dvd-ppc64le',
]
ftp_products = ['000product:openSUSE-ftp-ftp-aarch64',
+ '000product:openSUSE-ftp-ftp-ppc64le',
]
Signed-off-by: Michel Normand <normand@linux.vnet.ibm.com>
This is supposed to be used for temporary failures that do not deserve
a carry over as they are sporadic but should not stop a snapshot release
nor are they worth it to wait a job duplicate
We want to handle armv7 and armv6 trees alongside aarch64 (even
though they don't get tested separately right now its better
to have them released when aarch64 releases as not aligned
at all).
For Leap 15.0 Ports we need to be able to support two image
repos, one for arm and one for ppc because they get published
to two different locations. for now as we have only images_arm
add support for that while ppc is still making its way through
an initial build.
