On Fri, Mar 27, 2020 at 05:55:42PM -0600, Jerry James wrote:
> On Fri, Mar 27, 2020 at 4:42 PM Jerry James wrote:
> > Good idea. Thank you!
>
> I got a segfault on s390x on the second build attempt. I'd like to
> investigate the ephemeron angle a bit, I think.
No crashes here overnight, but
Jerry James writes:
> I think Richard addressed most of the points you raised.
Yes, and no new questions, either. So I think I'm done here (well,
I'll spectate, but the internals of the OCaml compiler are well beyond
my skillset :-).
Good luck!
Steve
--
Associate Professor
On Fri, Mar 27, 2020 at 4:42 PM Jerry James wrote:
> Good idea. Thank you!
I got a segfault on s390x on the second build attempt. I'd like to
investigate the ephemeron angle a bit, I think.
--
Jerry James
http://www.jamezone.org/
___
devel mailing
On Fri, Mar 27, 2020 at 4:41 PM Richard W.M. Jones wrote:
> I'll run it in a loop overnight and see if I can make it crash.
Good idea. Thank you!
--
Jerry James
http://www.jamezone.org/
___
devel mailing list -- devel@lists.fedoraproject.org
To
On Fri, Mar 27, 2020 at 04:20:16PM -0600, Jerry James wrote:
> On Fri, Mar 27, 2020 at 2:41 PM Richard W.M. Jones wrote:
> > Yup, and the stack trace shows the failure happening when creating an
> > ephemeron.
>
> On the other hand, a scratch build with coq upstream's final patch for
> ocaml
On Fri, Mar 27, 2020 at 2:41 PM Richard W.M. Jones wrote:
> Yup, and the stack trace shows the failure happening when creating an
> ephemeron.
On the other hand, a scratch build with coq upstream's final patch for
ocaml 4.10.0 succeeded on the first try:
On Fri, Mar 27, 2020 at 11:54:44AM -0600, Jerry James wrote:
> On Thu, Mar 26, 2020 at 10:28 AM Richard W.M. Jones wrote:
> > Jerry, I suggest this bug is real, but is also likely to be a bug in
> > Coq (most likely) or the OCaml runtime, possibly in the Weak module.
> > You might have more luck
On Fri, Mar 27, 2020 at 11:15:01AM -0600, Jerry James wrote:
> On Fri, Mar 27, 2020 at 11:03 AM Jerry James wrote:
> > Okay, I will give that a try.
>
> Except I can't. We're already not using %_smp_mflags. Ugh.
I realized that my build machine has MAKEFLAGS=-j24 which is why it's
building
On Fri, Mar 27, 2020 at 11:36:38AM -0600, Jerry James wrote:
> On Fri, Mar 27, 2020 at 11:30 AM Zbigniew Jędrzejewski-Szmek
> wrote:
> > We are. Did you trying putting '%global _smp_mflags -j1' somewhere
> > near the top of the spec file?
>
> We are? Where?
That is what the packaging
On Thu, Mar 26, 2020 at 10:28 AM Richard W.M. Jones wrote:
> Jerry, I suggest this bug is real, but is also likely to be a bug in
> Coq (most likely) or the OCaml runtime, possibly in the Weak module.
> You might have more luck asking the upstream developers for help.
Coq issue:
On Fri, Mar 27, 2020 at 11:30 AM Zbigniew Jędrzejewski-Szmek
wrote:
> We are. Did you trying putting '%global _smp_mflags -j1' somewhere
> near the top of the spec file?
We are? Where? The spec file does this to build:
make world VERBOSE=1
--
Jerry James
http://www.jamezone.org/
On Fri, Mar 27, 2020 at 11:15:01AM -0600, Jerry James wrote:
> On Fri, Mar 27, 2020 at 11:03 AM Jerry James wrote:
> > Okay, I will give that a try.
>
> Except I can't. We're already not using %_smp_mflags. Ugh.
We are. Did you trying putting '%global _smp_mflags -j1' somewhere
near the top
On Fri, Mar 27, 2020 at 11:03 AM Jerry James wrote:
> Okay, I will give that a try.
Except I can't. We're already not using %_smp_mflags. Ugh.
--
Jerry James
http://www.jamezone.org/
___
devel mailing list -- devel@lists.fedoraproject.org
To
On Wed, Mar 25, 2020 at 10:21 PM Stephen J. Turnbull wrote:
> Hi Jerry! Long time no see.
Hi Stephen! It's good to hear from yet another person I've worked
with via network for years.
I think Richard addressed most of the points you raised.
> Where is the segfault? Is it in coqc or is it in
On Thu, Mar 26, 2020 at 10:28 AM Richard W.M. Jones wrote:
> I don't know, now I can't even get the ‘fedpkg local’ to reproduce it :-(
>
> Jerry, I suggest this bug is real, but is also likely to be a bug in
> Coq (most likely) or the OCaml runtime, possibly in the Weak module.
> You might have
I don't know, now I can't even get the ‘fedpkg local’ to reproduce it :-(
Jerry, I suggest this bug is real, but is also likely to be a bug in
Coq (most likely) or the OCaml runtime, possibly in the Weak module.
You might have more luck asking the upstream developers for help.
As for what to do
On Thu, Mar 26, 2020 at 12:00:14PM +, Richard W.M. Jones wrote:
> This bug is VERY annoying! Although not very reproducible, I can
> usually hit it after about 4-6 hours of looping ‘fedpkg build’.
I mean ‘fedpkg local’. Local builds, not building in Koji.
Rich.
--
Richard Jones,
This bug is VERY annoying! Although not very reproducible, I can
usually hit it after about 4-6 hours of looping ‘fedpkg build’.
Considering the whole Coq build is quite lengthy you'd think that one
of these commands would hit it much more quickly:
$ while true ; do gdb -ex 'set args -coqlib
On Thu, Mar 26, 2020 at 01:20:58PM +0900, Stephen J. Turnbull wrote:
> Where is the segfault? Is it in coqc or is it in the generated code
> or is it in the OCaml compiler or is it somewhere else?
I managed to reproduce this on my mostly Rawhide x86-64 development
machine by running fedpkg build
Hi Jerry! Long time no see.
Jerry James writes:
> I built the whole stack for Rawhide with no issues.
Zero compiler warnings? No fiddling to suppress compiler warnings
*anywhere* in the build chain (whether options or pragmas)?
Not suggesting you go looking for pragmas (probably have 10
On Wed, Mar 25, 2020 at 9:24 PM Jerry James wrote:
> You'll want to view this with a fixed-width font.
Thank you, gmail, for completely destroying my formatting work. Oh
well, you can probably tell what I was trying to do.
--
Jerry James
http://www.jamezone.org/
On Wed, Mar 25, 2020 at 4:58 PM Jerry James wrote:
> Either I got lucky when I launched the Rawhide build, or something is
> fundamentally different between F32 and Rawhide. Clearly something
> nondeterministic is at work. I have been unable to reproduce this
> failure in mock so far, but will
On Wed, Mar 25, 2020 at 8:57 PM Paul Dufresne via devel
wrote:
> ... yeah, I know, might have no link at all with your Coq build... I
> don't know.
Maybe ... but that sure is suspicious. I recall hearing that OpenJDK
is also suffering from weird segfaults. H.
Thanks for the input,
Le Wed, 25 Mar 2020 16:58:33 -0600,
Jerry James a écrit :
> Either I got lucky when I launched the Rawhide build, or something is
> fundamentally different between F32 and Rawhide. Clearly something
> nondeterministic is at work. I have been unable to reproduce this
> failure in mock so far,
I've been talking to Richard Jones about this privately, and he
suggested that a message to fedora-devel could be helpful.
I've been talking for weeks about updating the entire coq stack,
badgering people into swapping reviews with me, etc. Today I finally
had all the bits in place to do the
25 matches
Mail list logo
