Hi everyone,
Today I have been working on better documenting our conventions under
GitLab. This has resulted in a handful of documents:
* A gitlab/issues wiki page [1], describing our triage and issue
resolution workflow
* A gitlab/merge-requests wiki page [2], describing our patch
Phyx writes:
> Hi Ben,
>
> That's awesome! I'm glad to have something to refer to as on Trac I was
> sometimes hesitant as to where something fell.
>
Indeed; you certainly weren't the only one. As you can tell from the
import mappings I posted earlier, Trac keyword usage wasn't particularly
Hmm this is really weird, I tried to again but it's building fine now. Nothing
changed -- I'm using the same tree, trying after `git clean -xfd`, and without a
build.mk. I guess the bug does not happen deterministically? Was that also the
case with the bug report you mentioned?
In case anyone's
Simon Peyton Jones via ghc-devs writes:
> Are you sure you got all the labels. Eg I don't see "type error messages
> https://gitlab.haskell.org/ghc/ghc/issues?label_name%5B%5D=type+error+messages
>
> Maybe that's because there is only one such ticket, #16439.
>
Indeed, that is reason. I had
Are you sure you got all the labels. Eg I don't see "type error messages
https://gitlab.haskell.org/ghc/ghc/issues?label_name%5B%5D=type+error+messages
Maybe that's because there is only one such ticket, #16439.
Can we have a list of all such orphaned labels, so we can get rid of them? Eg
by
At least on my Ubuntu 16.04, it builds:
% git clone --recursive g...@gitlab.haskell.org:ghc/ghc.git
ghc-gold-error-6f7115dfd4
% cd ghc-gold-error-6f7115dfd4
% ./boot && ./configure --prefix=$HOME/opt/ghc-gold-error-6f7115dfd4
GHC=$HOME/.stack/programs/x86_64-linux/ghc-8.6.3/bin/ghc
% make -j4
Simon Peyton Jones via ghc-devs writes:
> Good!
>
> Colours are a bit mixed up. Blue seems to be for "Scope". Could "Issue
> flags" be another colour, and "Types of bugs" be another. The mixture
> under those headings is hard to grok.
>
Yes they were; I ran out of time before I had a chance to
That sounds good. A few more questions:
What's the exact version of your OS, and of gold?
After getting to the error, can you run the failing ghc invocation directly,
and see if the error remains? The one starting with
"/home/omer/ghc_bins/ghc-8.6.4-bin/bin/ghc" -o
Thanks for the explanation.
I was able to access the URL.
Thank you,
Takenobu
On Mon, Apr 1, 2019 at 2:55 AM Ben Gamari wrote:
> Takenobu Tani writes:
>
> > Thank you for the useful link.
> >
> > It may not be related to this, but the following URL is not displayed
> > correctly.
> >
>
Good!
Colours are a bit mixed up. Blue seems to be for "Scope". Could "Issue flags"
be another colour, and "Types of bugs" be another. The mixture under those
headings is hard to grok.
Simon
| -Original Message-
| From: ghc-devs On Behalf Of Ben Gamari
| Sent: 29 March 2019
I printed out the full [StgTopBinding] list and got:
let {
sat_s27NC [Occ=Once] :: IO Timeout
[LclId] =
[] \u [] fmap $fFunctorIO Timeout newUnique;
} in >>= $fMonadIO sat_s27NC sat_s27NT;
That does look odd. Can you explain how to reproduce this with HEAD? That is,
are we
11 matches
Mail list logo
