public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/28708] run-debuginfod-webapi-concurrency.sh seems to be flaky
Date: Mon, 20 Dec 2021 17:17:00 +0000	[thread overview]
Message-ID: <bug-28708-10460-edi6DdrB3i@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28708-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28708

--- Comment #9 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Evgeny Vereshchagin from comment #7)
> > Note that packit doesn't use real hardware for various architectures but
> > "container emulation" which causes various testcases to fail.
> > 
> I think I ran into issues like that in
> https://github.com/evverx/elfutils/issues/32 and
> https://github.com/evverx/elfutils/issues/31. I ignore them for the most
> part. Though it would be great if they could be skipped there. Some of them
> seem to be easy to skip because they seem to trigger seccomp filters of some
> kind but I'm not sure about the rest.

Easiest is to run containers with --security-opt seccomp=unconfined to make
sure seccomp doesn't arbitrarily blocks syscalls (or worse returns ENOPERM
instead on ENOSYS).

> > We do have somewhat better buildbot workers for various architectures here:
> > https://builder.wildebeest.org/buildbot/#/builders?tags=elfutils
>  
> As far as I understand the tests are run there on commits to the elfutils
> repository but I'm not sure how to test "PRs" there. If it was possible to
> use it before commits are merged into the master branch I wouldn't have
> started using Packit on GitHub probably.

There is a vacation and a nationwide lockdown coming up so I can see what I can
do. I hope to connect the buildbot with patchworks so that you can easily test
any submitted patch before committing.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-12-20 17:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17  1:02 [Bug debuginfod/28708] New: " evvers at ya dot ru
2021-12-17  1:25 ` [Bug debuginfod/28708] " evvers at ya dot ru
2021-12-17  1:53 ` fche at redhat dot com
2021-12-17  2:30 ` evvers at ya dot ru
2021-12-17  8:31 ` mark at klomp dot org
2021-12-17 18:48 ` fche at redhat dot com
2021-12-17 18:48 ` fche at redhat dot com
2021-12-17 18:49 ` fche at redhat dot com
2021-12-19 22:06 ` evvers at ya dot ru
2021-12-19 22:47 ` fche at redhat dot com
2021-12-20 17:17 ` mark at klomp dot org [this message]
2021-12-20 23:21 ` evvers at ya dot ru
2022-04-03  0:43 ` fche at redhat dot com
2022-04-04  2:27 ` evvers at ya dot ru
2022-04-05 14:09 ` mark at klomp dot org
2022-04-24 10:23 ` mark at klomp dot org

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=bug-28708-10460-edi6DdrB3i@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).