Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

packit: try out TFT #11

Closed
wants to merge 6 commits into from
Closed

packit: try out TFT #11

wants to merge 6 commits into from

Commits on Nov 20, 2023

  1. debug-only: drop all GH workflows

    @mrc0mmand
    mrc0mmand committed Nov 20, 2023
    Configuration menu
    Copy the full SHA
    f1fb348 View commit details
    Browse the repository at this point in the history

  2. test: make the LOOKS_LIKE_* variables proper booleans

    @mrc0mmand
    mrc0mmand committed Nov 20, 2023
    Configuration menu
    Copy the full SHA
    a3ef1f7 View commit details
    Browse the repository at this point in the history

  3. test: support NO_BUILD=yes on Fedora

    @mrc0mmand
    mrc0mmand committed Nov 20, 2023
    Configuration menu
    Copy the full SHA
    581bfa5 View commit details
    Browse the repository at this point in the history

  4. test: move a couple of binaries to the BASICTOOLS array 

    As they're not optional.
    @mrc0mmand
    mrc0mmand committed Nov 20, 2023
    Configuration menu
    Copy the full SHA
    b011b1f View commit details
    Browse the repository at this point in the history

  5. test: don't use ddebug() before it's defined 

    I'm pretty sure this is not the only case, but it's the one I recently
noticed. Even though we call ddebug() from a function, that function is
called before ddebug() is defined, resulting in the same issue as if we
called just ddebug() in its place, i.e.:

..//test-functions: line 276: ddebug: command not found
    @mrc0mmand
    mrc0mmand committed Nov 20, 2023
    Configuration menu
    Copy the full SHA
    8276911 View commit details
    Browse the repository at this point in the history

  6. packit: run tests on Fedora Rawhide via Testing Farm 

    Let's utilize the full power of Packit and run some tests with the just
built RPMs. This makes use of the Fedora infrastructure provided by
the Testing Farm project [0][1].

With the current configuration, the `tests` job runs tests from the
Fedora tests repository [2] in a very similar fashion like Ubuntu CI
does, just with different metadata all around it. ATTOW there are only
two tests, which are wrappers around unit tests and integration tests;
the latter one currently runs only nspawn-based tests, since there's no
KVM on the test VMs, and, for now, I'd like to see how well the infra is
going to manage our upstream traffic.

[0] https://docs.testing-farm.io/Testing%20Farm/0.1/index.html
[1] https://packit.dev/docs/configuration/upstream/tests
[2] https://src.fedoraproject.org/tests/systemd
    @mrc0mmand
    mrc0mmand committed Nov 20, 2023
    Configuration menu
    Copy the full SHA
    01fe558 View commit details
    Browse the repository at this point in the history