#3 Add CI tests to run make test-in-docker
Opened a year ago by bcl. Modified 4 months ago
rpms/ bcl/lorax master-tests  into  master

file added
+6

@@ -0,0 +1,6 @@ 

+ --- !Policy

+ product_versions:

+   - fedora-*

+ decision_context: bodhi_update_push_stable

+ rules:

+   - !PassingTestCaseRule {test_case_name: org.centos.prod.ci.pipeline.allpackages-build.package.test.functional.complete}

file modified
+2 -2

@@ -4,7 +4,7 @@ 

  

  Name:           lorax

  Version:        31.10

- Release:        2%{?dist}

+ Release:        2%{?dist}.bcl1

  Summary:        Tool for creating the anaconda install images

  

  License:        GPLv2+

@@ -170,7 +170,7 @@ 

  build images, etc. from the command line.

  

  %prep

- %setup -q -n %{name}-%{version}

+ %autosetup -p1 -n %{name}-%{version}

  

  %build

  

file added
+1

@@ -0,0 +1,1 @@ 

+ 1

file added
+5

@@ -0,0 +1,5 @@ 

+ ---

+ 

+ standard-inventory-qcow2:

+   qemu:

+     m: 4G

@@ -0,0 +1,21 @@ 

+ #!/bin/bash

+ set -eux

+ 

+ : ${1?"Usage: $0 SOURCEDIR"}

+ 

+ SOURCEDIR=$1

+ CWD="$(pwd)"

+ 

+ cd "${SOURCEDIR}" || exit

+ 

+ # Make absolutely sure we are NOT testing the source distribution, just using

+ # the tests from ./tests/ against the installed modules

+ rm -rf ./src/

+ 

+ # Run the tests w/o adjusting PYTHONPATH

+ python3 -m nose ./tests/pylorax/ ./tests/composer/

+ RET=$?

+ 

+ # clean up and exit

+ cd "${CWD}" || exit

+ exit ${RET}

file added
+23

@@ -0,0 +1,23 @@ 

+ ---

+ # Run lorax's test suite using podman

+ - hosts: localhost

+   roles:

+     - role: standard-test-source

+       tags:

+         - always

+ 

+     - role: standard-test-basic

+       tags:

+         - classic

+ 

+       required_packages:

+         - python3

+         - python3-magic

+         - python3-mock

+         - python3-nose

+         - kernel-modules

+ 

+       tests:

+         - simple:

+             dir: scripts

+             run: ./run_tests.sh {{ tenv_workdir }}/source/

Based on tests from pykickstart.

1 new commit added

  • Update tests to use standard-test-source
a year ago

2 new commits added

  • Update tests to use standard-test-source
  • Add CI tests to run make test-in-docker
11 months ago

rebased onto e3ef238

10 months ago

rebased onto bf4be92

6 months ago

1 new commit added

  • Run tests on installed pkg, not via docker/podman
6 months ago

3 new commits added

  • Run tests on installed pkg, not via docker/podman
  • Update tests to use standard-test-source
  • Add CI tests to run make test-in-docker
6 months ago

1 new commit added

  • Test fake url patch
6 months ago

I've reran the test and I see the failure as 'xz: (stdin): Cannot allocate memory'

https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-pr-pipeline/1845/artifact/package-tests/logs/FAIL-str_simple-err.log

I also see the test ran in a VM with 4GB of RAM.

/usr/bin/qemu-kvm -cpu host -enable-kvm -display none -smp 17,sockets=17,cores=1,threads=1 -m 4G

https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-pr-pipeline/1845/artifact/package-tests/logs/console.log

Ok, in that one it looks like xz ran ok. I'm not sure what's going on with single.repo in there but that could be an actual bug. The remaining issue is the lack of the hfsplus kernel module (or auto-loading of it).

rebased onto b191558

4 months ago

1 new commit added

  • Remove included test patch
4 months ago

The CI test failed, because it couldn't apply the patch from this PR, the PR needs to be rebased before running the test again.

The CI test failed, because it couldn't apply the patch from this PR, the PR needs to be rebased before running the test again.

I already did that, note that the latest simple-koji-ci passed, but it still hasn't started the Fedora CI in any of these attempts.

FTR, Pagure still detect the PR as conflicting as well

it it still hasn't started the Fedora CI in any of these attempts.

It did, the last flag for Fedora CI is 3 days old, Fedora CI re-uses the same flag and just updates it while simple-koji-ci adds new flags.

simple-koji-ci has a different logic than Fedora CI as it doesn't try to merge the PR it just checks if the proposed change still builds.

Well that's nice and inconsistently confusing. Let's try it again.

rebased onto a44ea73

4 months ago