Re: Koji ppc64le build failure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jul 18, 2022 at 09:28:42PM +0200, Dan Horák wrote:
> On Mon, 18 Jul 2022 11:39:58 -0700
> Kevin Fenzi <kevin@xxxxxxxxx> wrote:
> 
> > On Mon, Jul 18, 2022 at 11:59:49AM +0100, Richard W.M. Jones wrote:
> > > On Sun, Jul 17, 2022 at 12:50:01PM -0700, Kevin Fenzi wrote:
> > > > On Sun, Jul 17, 2022 at 08:34:30PM +0100, Richard W.M. Jones wrote:
> > > > > 
> > > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=89618509
> > > > > 
> > > > > On ppc64le:
> > > > > FAIL: test-checkwrite.sh
> > > > > 
> > > > > There should be a core dump associated with this failure.  Is it
> > > > > possible someone with Koji access could look to see if this is still
> > > > > around and capture it?  (Even just a full stack trace would be useful)
> > > > > 
> > > > > We've been seeing this error occasionally (same test, only on ppc64le)
> > > > > for a few weeks.  I reserved a ppc64le machine at Red Hat last week
> > > > > and ran this test on basically exactly the same combination of
> > > > > software thousands of times, and it didn't fail even once in that
> > > > > time, so I'm out of ideas how to reproduce it for myself.
> > > > 
> > > > Core at: 
> > > > https://infrastructure.fedoraproject.org/infra/tmp/core.nbdkit.1000.9be14c7983c4418eb6245b3fd5719a79.2744149.1658085889000000.zst
> > > > 
> > > >                 Module libtasn1.so.6 with build-id 460fc6bd3f93e57e7d593080f58952f61cdb344a
> > > >                 Stack trace of thread 2744170:
> > > >                 #0  0x00007fffa9b59b6c n/a (/usr/lib64/libc.so.6 + 0xb9b6c)
> > > >                 ELF object binary architecture: PowerPC64
> > > 
> > > Sorry, I realised that the core dump won't work without the
> > > executable.  Is <builddir>/server/nbdkit still around?  (Note there's
> > > another "nbdkit" binary in the top build directory, which is _not_ the
> > > server.)
> > 
> > To circle back to the list, it sounds like you got it to happen locally?
> 
> I don't think so, I believe Rich needs the binary that produced the
> coredump. I have grabbed it and it's now
> http://fedora.danny.cz/tmp/nbdkit

Thanks for your help!  I did finally manage to reproduce it locally
(although not fix it so far ...).

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux