openSUSE Release Process » openSUSE Leap 15.0

does this work meanwhile?

I don't think anyone has done anything here yet. I wanted to talk to coolo personally, then I forgot about it, then I missed the opportunity again, then … sorry :(

Will address in daily jangouts call.

I created openQA job groups openSUSE Leap 15.0 Updates and … Incidents with the test plan taken over from Leap 42.3 for now:

for i in Incidents Updates ; do openqa-dump-templates --host https://openqa.opensuse.org --group "openSUSE Leap 42.3 $i" --full | sed -e 's/42\.3/15.0/g' > leap_15.0_$i && openqa-load-templates --host https://openqa.opensuse.org leap_15.0_$i ; done

And manually using the webui on https://openqa.opensuse.org/admin/groups put the job group in the right position as subgroup to openSUSE Leap behind the other openSUSE Leap 15.0 jobs.

Now, how to ensure the maintenance bot can make use of these? And where can I monitor the bot operating, e.g. tail logfile or screen session to attach to?

what is the status here?

coolo and tacit setup the openqa-maintenance bot to work aligned with the SLE workflow. test-updates are triggered, openQA tests fail due to necessary test adaption. I understood that SUSE QAM confirmed that they would take responsibility for the necessary openQA test adaptions but I have not seen effects of this so far. I would adress the question again about the current state to coolo latest on next RM call, e.g. next Monday or Wednesday.

what is the status here?

Incidents and Updates tests are in place, tests can work in principle, e.g. see textmode passing. tacit wanted to clarify who are the responsibles persons from maintenance/QAM for adapting the openQA tests as well as regular test review. QSF (QA SLE functional) would stand ready for support but only for exceptional handling.

Looks like for install_with_updates the installation/setup_online_repos test needs to be called earlier. Could you just fix that? We really need that setup up ASAP.

other tests fail in gnucash due to low disk space and in applying online updates. Not sure why that happens given that the same test works in the main project.

The kde test fails in applying online updates due to outdated disk images which results in too many updates installed. Could you move the symlink on openqa.o.o forward please?