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>
There were still exceptions not caught - and I have the suspicion
that the memory leaks we see in production are caused by the reconnects
(if you google for python memory leaks you end up with pika and lxml
examples - both we use here, so a restart every couple of hours can't
hurt)
Without this, the relative rarer types of requests seen in projects with
staging and handled by list command will be included in staging proposal.
However, since they are not stageable the select operation will fail. This
change ensures that a filter is always present when stageable is True to
exclude non-stableable requests. The list command sets stageable to false
in order to list out the non-stageable requests of interest.
This was not observed in openSUSE since the main non-stageable request was
change_devel and that was exluded in StrategyNone. That filter could be
replaced with the stageable filter, but having an always on filter seems to
make more sense since generally operating in one of two modes.
Now that the bug related to openSUSE/open-build-service#5571 has been fixed
the inverted behavior of exclude_target_projects no longer works. As such
the argument should be removed and only way to get the desired behavior
is to override include_request_from_project which includes request sourced
from specific project. For the purposes of `devel-projects requests` only
interested in requests targeting a specific project.
See also commit 0b342a5.
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.
