public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benjamin A. Beasley <code@musicinmybrain.net>
To: git-commits@fedoraproject.org
Subject: [rpms/google-benchmark] rawhide: Link an unreleased fix associated with skipped tests
Date: Thu, 04 Jun 2026 11:53:17 GMT	[thread overview]
Message-ID: <178057399736.1.5144636173232122214.rpms-google-benchmark-636dbc33761c@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/google-benchmark
            Branch : rawhide
            Commit : 636dbc33761cdf0064366966b0dc4414910ae628
            Author : Benjamin A. Beasley <code@musicinmybrain.net>
            Date   : 2026-06-04T12:52:31+01:00
            Stats  : +4/-0 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/google-benchmark/c/636dbc33761cdf0064366966b0dc4414910ae628?branch=rawhide

            Log:
            Link an unreleased fix associated with skipped tests

[skip changelog]

---
diff --git a/google-benchmark.spec b/google-benchmark.spec
index 68f04c7..19e36c2 100644
--- a/google-benchmark.spec
+++ b/google-benchmark.spec
@@ -64,6 +64,10 @@ BuildOption(conf): %{shrink:
 # We don’t bother attempting to run the four tests that do succeed in
 # perf_counters_gtest; it’s much more straightforward to just skip these two
 # executables at the ctest level entirely, and little is lost by doing so.
+#
+# This is fixed upstream by https://github.com/google/benchmark/pull/2204, but
+# it is not trivial to backport, so we keep this workaround until the next
+# upstream release.
 BuildOption(check): --exclude-regex '^perf_counters_g?test$'
 %endif
 

                 reply	other threads:[~2026-06-04 11:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178057399736.1.5144636173232122214.rpms-google-benchmark-636dbc33761c@fedoraproject.org \
    --to=code@musicinmybrain.net \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox