From: ludo@gnu.org (Ludovic Courtès)
To: Brett Gilio <brettg@posteo.net>
Cc: 33478@debbugs.gnu.org
Subject: [bug#33478] [PATCH] gnu: agda: Upgrade to 2.5.4.2
Date: Mon, 26 Nov 2018 11:27:46 +0100 [thread overview]
Message-ID: <87ftvo9lr1.fsf@gnu.org> (raw)
In-Reply-To: <878t1hgnv4.fsf@posteo.net> (Brett Gilio's message of "Sun, 25 Nov 2018 09:47:59 -0600")
Hi Brett,
Brett Gilio <brettg@posteo.net> skribis:
> Ludovic Courtès writes:
>
>> Hello Brett,
>>
>> Brett Gilio <brettg@posteo.net> skribis:
>>
>>> Ludovic Courtès writes:
>>
>> [...]
>>
>>>> --8<---------------cut here---------------start------------->8---
>>>> [ 37 of 339] Compiling Agda.Utils.Memo ( src/full/Agda/Utils/Memo.hs, dist/build/Agda/Utils/Memo.o )
>>>>
>>>> src/full/Agda/Utils/Memo.hs:10:1: error:
>>>> Bad interface file: /gnu/store/fmq6ybv1m3yr9x2y16gv85nv30df9xw8-ghc-hashable-1.2.7.0/lib/ghc-8.4.3/hashable-1.2.7.0/Data/Hashable.hi
>>>> Something is amiss; requested module hashable-1.2.7.0:Data.Hashable differs from name found in the interface file hashable-1.2.7.0:Data.Hashable (if these names look the same, try again with -dppr-debug)
>>>> |
>>>> 10 | import Data.Hashable
>>>> | ^^^^^^^^^^^^^^^^^^^^
>>>> --8<---------------cut here---------------end--------------->8---
>>>>
>>>> Could you take a look?
>>>>
>>>> Thanks,
>>>> Ludo’.
>>>
>>> Hi Ludo,
>>>
>>> I put it through 20 rounds of building, and dumped the gc and
>>> everything. I can not replicate it on my end, can we get a third person
>>> to try it?
>>
>> I’m not sure what you mean by “20 rounds” and “dumped the gc”. I would
>> expect such a failure to be deterministic.
>>
>> Are you testing this on ‘master’? Which commit? I tested it on top of
>> 63fd9f084a5e345d2edaeaf5e8f435a3130f9edc.
>>
>> Thanks,
>> Ludo’.
>
> --rounds=20 to see if it is deterministic. But as I said, I am not
> replicating the error. Yes, I tested it on master, commit and on the
> same commit number as you.
I’ve retried just now: applying the Agda patch alone on top of commit
0c17f72070cbfb04f311b776a080849b369aac25. It’s the same derivation as
the one I tested above.
Are we in the exact same conditions? I’m on x86_64.
Ludo’.
next prev parent reply other threads:[~2018-11-26 10:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 4:24 [bug#33478] [PATCH] gnu: agda: Upgrade to 2.5.4.2 Brett Gilio
2018-11-24 21:30 ` Ludovic Courtès
2018-11-24 21:44 ` Brett Gilio
2018-11-25 2:04 ` Brett Gilio
2018-11-25 14:22 ` Ludovic Courtès
2018-11-25 15:47 ` Brett Gilio
2018-11-26 10:27 ` Ludovic Courtès [this message]
2019-12-05 0:39 ` Brett Gilio
2019-12-05 8:34 ` bug#33478: " Efraim Flashner
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=87ftvo9lr1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33478@debbugs.gnu.org \
--cc=brettg@posteo.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.