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

workflows: Drop i386 clang check-memory #19228

Merged
merged 2 commits into from
Aug 24, 2023
Merged

workflows: Drop i386 clang check-memory #19228

merged 2 commits into from
Aug 24, 2023

Commits on Aug 24, 2023

  1. containers/unit-tests: Don't break verbatim command 

    This is completely unimportant, it should only trigger a container
refresh in the PR.
    @martinpitt
    martinpitt committed Aug 24, 2023
    Configuration menu
    Copy the full SHA
    332ee3b View commit details
    Browse the repository at this point in the history

  2. workflows: Drop i386 clang check-memory 

    In recent Debian testing, valgrind now shows a gazillion
Memcheck:{Cond,Value4} errors all over the place: in GMP, GnuTLS, glib
hashtables, and even strcmp(). Give up at last, and run valgrind on 64
bit only. This also becomes less important with us moving more and more
code away from C.

Add a comment about the explicit "check" run. It was introduced in
commit 1ef0001 to run static code checks, which don't work against a
tarball in "distcheck".

Change the order in unit-tests-refresh.yml to match the order in
unit-tests.yml to reduce confusion.
    @martinpitt
    martinpitt committed Aug 24, 2023
    Configuration menu
    Copy the full SHA
    e482209 View commit details
    Browse the repository at this point in the history