Project

General

Profile

Actions

action #132338

closed

Enable BCI-tests for openSUSE Tumbleweed

Added by dirkmueller 12 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
2023-07-05
Due date:
% Done:

0%

Estimated time:
Tags:

Description

With https://github.com/SUSE/BCI-tests/pull/267 being merged the BCI-testing can now be run on Tumbleweed by using OS_VERSION=latest

I have started to submit some containers to openSUSE:Factory and it would be great to have some form of testing for them. I could setup periodic testing on github but it might be better to have openqa added to the container publishing pipeline for tumbleweed?


Files

screenshot-2023-07-19-12_36_56.jpg (44.7 KB) screenshot-2023-07-19-12_36_56.jpg current job status mloviska, 2023-07-19 10:38

Related issues 1 (0 open1 closed)

Related to Containers - action #161741: Enable BCI tests for Factory (Tumbleweed containers) in openqa.opensuse.orgResolvedmloviska2024-06-04

Actions
Actions #1

Updated by jlausuch 12 months ago

  • Tags set to bci
  • Status changed from New to Workable
Actions #2

Updated by mloviska 12 months ago

  • Status changed from Workable to In Progress
  • Assignee set to mloviska
Actions #3

Updated by mloviska 12 months ago

  • Status changed from In Progress to Feedback
Actions #4

Updated by mloviska 12 months ago

A subset of BCI tests can be found in TW's development group e.g

Actions #5

Updated by ph03nix 11 months ago

Actions #6

Updated by dirkmueller 11 months ago

The tests are still far away from passing completely. which tox -e environments are you currently running? we can focus on "all" for example to finish first.

I have a really hard time navigating openqa, can you please point me at the failures that you're looking at?

I have found this:

    @pytest.mark.skipif(
        OS_VERSION != "tumbleweed",
        reason="product flavors only available for openSUSE",
    )
    def test_opensuse_product_flavor(auto_container):
        """Checks that this is an appliance-docker flavored product."""
>       auto_container.connection.run_expect(
            [0], "rpm -q --whatprovides 'flavor(appliance-docker)'"
        )
E       AssertionError: Unexpected exit code 127 for CommandResult(command=b"rpm -q --whatprovides 'flavor(appliance-docker)'", exit_status=127, stdout=None, stderr=b'/bin/sh: line 1: rpm: command not found\n')
E       assert 127 in [0]
E        +  where 127 = CommandResult(command=b"rpm -q --whatprovides 'flavor(appliance-docker)'", exit_status=127, stdout=None, stderr=b'/bin/sh: line 1: rpm: command not found\n').rc

which I'm aware of (this test cannot be run for containers that do not include rpm). I'll see what I can do about it. the other thing that is failign are the sizes, they need updates.

I have a draft PR that I need to get back to to solve the remaining test failures.

Actions #8

Updated by dirkmueller 7 months ago

Test died: command 'pip --quiet install --upgrade pip' failed at /usr/lib/os-autoinst/testapi.pm line 926.

Thats a bug in the testsuite. it shouldn't install pip from the internet. it should use the pip that the distribution provides.

Actions #9

Updated by mloviska 6 months ago ยท Edited

damn, I have noticed that tests have been broken in TW because of missing dependency.

This has been fixed, but the schedule is broken for some reason :/

https://openqa.opensuse.org/tests/3870280#

Actions #10

Updated by mloviska 6 months ago

s/CONTAINER_RUNTIME/CONTAINER_RUNTIMES/

Actions #11

Updated by mloviska 6 months ago

dirkmueller wrote in #note-8:

Test died: command 'pip --quiet install --upgrade pip' failed at /usr/lib/os-autoinst/testapi.pm line 926.

Thats a bug in the testsuite. it shouldn't install pip from the internet. it should use the pip that the distribution provides.

Does this apply to all suse/opensuse hosts or only to TW?

Actions #14

Updated by mloviska 5 months ago

Hey @dirkmueller, can we close this ticket?

Actions #15

Updated by dirkmueller 5 months ago

Hey @dirkmueller, can we close this ticket?

What's the current state? as far as I can see the tests are failing (e.g. https://openqa.opensuse.org/tests/3886274#step/bci_test_podman/39 ) because the invocation of the testsuite is incorrect. should we be fixing that? is it actually gating, e.g. a test failure preventing the container from being published?

Actions #16

Updated by mloviska 5 months ago

dirkmueller wrote in #note-15:

Hey @dirkmueller, can we close this ticket?

What's the current state? as far as I can see the tests are failing (e.g. https://openqa.opensuse.org/tests/3886274#step/bci_test_podman/39 ) because the invocation of the testsuite is incorrect. should we be fixing that? is it actually gating, e.g. a test failure preventing the container from being published?

The tests are running just in the TW dev group, thus it is more of a PoC and we should make them stable prior setting them as gating and moving to the main TW group.

Meanwhile, I have fixed the BCI markers for rust and postgres (thanks for the hint):

However, I am not sure what is wrong with these, could you have a look please?

Actions #17

Updated by mloviska 5 months ago

https://openqa.opensuse.org/tests/3900969#details golang is passing after fixing BCI_TEST_ENVS to go

Actions #18

Updated by mloviska 5 months ago

VR for ruby https://openqa.opensuse.org/tests/3941288

So the tests are passing as of now but they are still in the development TW group

Actions #19

Updated by mloviska 5 months ago

  • Status changed from Feedback to Resolved
Actions #20

Updated by mloviska 26 days ago

  • Related to action #161741: Enable BCI tests for Factory (Tumbleweed containers) in openqa.opensuse.org added
Actions

Also available in: Atom PDF