Hi -
> If you think it helps diagnose these spurious failure please do.
(Shall I try to get a wildebeest buildbot admin login to try to
rebuild repeatedly, till it hits these heisenbugs?)
> It might also help to split this test into smaller ones to make sure
> the tests just test one specific
Hi Frank,
On Tue, Jun 15, 2021 at 05:53:18PM -0400, Frank Ch. Eigler wrote:
> > [...] But run-find-debuginfo.sh failed for (I think) unrelated reasons.
>
> Any objection to me firing in some speculative tests/run-debuginfod*
> patches into the buildbot to evoke more usefully verbose failures?
Hi -
> [...] But run-find-debuginfo.sh failed for (I think) unrelated reasons.
Any objection to me firing in some speculative tests/run-debuginfod*
patches into the buildbot to evoke more usefully verbose failures?
- FChE
On Tue, Jun 15, 2021 at 09:29:46PM +, build...@builder.wildebeest.org wrote:
> The Buildbot has detected a new failure on builder elfutils-fedora-x86_64
> while building elfutils.
> Full details are available at:
> https://builder.wildebeest.org/buildbot/#builders/3/builds/770
>
>
The Buildbot has detected a new failure on builder elfutils-fedora-x86_64 while
building elfutils.
Full details are available at:
https://builder.wildebeest.org/buildbot/#builders/3/builds/770
Buildbot URL: https://builder.wildebeest.org/buildbot/
Worker for this Build: fedora-x86_64
Build
https://sourceware.org/bugzilla/show_bug.cgi?id=27982
--- Comment #1 from Frank Ch. Eigler ---
possible representation in the apis:
-> $DEBUGINFOD_MAXSIZE (in bytes)
-> outgoing request header X-DEBUGINFOD-MAXSIZE: (number)
<- http response code 406 (Not Acceptable) if rejected
<- posix API rc
