On Tue, 9 Apr 2019 at 02:28, Ben Gamari wrote:
> The GHC team is proud to announce the first release candidate of 8.6.5.
> The source distribution, binary distributions, and documentation are
> available at
> https://downloads.haskell.org/~ghc/8.6.5-rc1
I don't see any source tarball...
Jens
Perhaps the current 'my fork is not available' mess is actually the
root cause, then?
On Mon, 8 Apr 2019 at 21:56, Artem Pelenitsyn wrote:
>
> On Mon, 8 Apr 2019 at 14:22 Ben Gamari wrote:
>>
>> Ara Adkins writes:
>>
>> > I don't, which is the curious thing. There's just a gap above the
>> > fi
On Mon, 8 Apr 2019 at 14:22 Ben Gamari wrote:
> Ara Adkins writes:
>
> > I don't, which is the curious thing. There's just a gap above the
> > filter dropdown where it should be.
> >
> Hmm, it's possible this is related to the fact that you had only
> reporter privileges.
Just a datapoint here
The patch I’m validating is actually to fix those memory barrier issues.
It turns out these failures were all due to GHC complaining about the LLVM
version on stderr; sorry for rubber ducking the list!
On Mon, Apr 8, 2019 at 1:26 PM Phyx wrote:
> Just a wild guess, but considering the time it's
Just a wild guess, but considering the time it's taken to run through the
testsuite you're running it on a reasonable AArch64 machine.
You may be hitting the weak memory ordering bugs
https://gitlab.haskell.org/ghc/ghc/issues/15449 , though I haven't followed
the ticket very closely...
On Mon, Apr
What kinds of tests are failing? Have they always failed?
On Mon, Apr 8, 2019 at 8:55 PM Travis Whitaker wrote:
>
> Hello GHC devs,
>
> When attempting to validate a patch on aarch64, it seems there are a large
> number of validation failures:
>
> SUMMARY for test run started at Mon Apr 8 07:19
Hello GHC devs,
When attempting to validate a patch on aarch64, it seems there are a large
number of validation failures:
SUMMARY for test run started at Mon Apr 8 07:19:05 2019 UTC
0:15:35 spent to go through
6890 total tests, which gave rise to
17169 test cases, of which
10018 were
Hi Ben,
On Mon, 8 Apr 2019 at 13:59, Andrés Sicard-Ramírez wrote:
> Using
> https://downloads.haskell.org/ghc/8.6.5-rc1/ghc-8.6.4.20190406-x86_64-deb8-linux.tar.xz
> I running as usual
>
> $ ./configure --prefix=
> $ make install
>
> I got the following error:
>
> ./template-haskell.cabal has be
Thanks so much Ben! That seems to have done the trick.
Unfortunately I seem to have hit another hurdle, as my fork doesn't
seem to be in the list of potential sources at all [0]. Similarly if I
try and start the MR from within my fork, the only target is my fork.
It's like it's lost its parent rel
Hi Ben,
Using
https://downloads.haskell.org/ghc/8.6.5-rc1/ghc-8.6.4.20190406-x86_64-deb8-linux.tar.xz
I running as usual
$ ./configure --prefix=
$ make install
I got the following error:
./template-haskell.cabal has been changed. Re-configuring with most recently
used options. If this fails, p
Hello everyone,
The GHC team is proud to announce the first release candidate of 8.6.5.
The source distribution, binary distributions, and documentation are
available at
https://downloads.haskell.org/~ghc/8.6.5-rc1
This release fixes a handful of issues with 8.6.4:
- Binary distributions o
Ara Adkins writes:
> I don't, which is the curious thing. There's just a gap above the
> filter dropdown where it should be.
>
Hmm, it's possible this is related to the fact that you had only
reporter privileges. I just gave you the developer role; have things
changed at all?
Cheers,
- Ben
s
Yes, this is an consequence of a bug in gitlab which meant that pushes
to branches which were also MRs were built twice.
Oh ok!
If you want your commit to be built you could make a MR?
I don't like the idea of submitting a MR just to test some code. It isn't a
merge request yet, yet I would
Yes, this is an consequence of a bug in gitlab which meant that pushes
to branches which were also MRs were built twice.
I'm not sure there is a way to manually trigger the CI pipeline. If
you really want to you could modify the .gitlab-ci.yml file on your
branch.
If you want your commit to be bu
Hi devs,
It seems that the CI doesn't check branches in GHC forks on Gitlab
anymore. Is is intentional? Is there a way to trigger a CI execution
manually on a specific branch?
Thanks,
Sylvain
___
ghc-devs mailing list
ghc-devs@haskell.org
http://ma
I don't, which is the curious thing. There's just a gap above the
filter dropdown where it should be.
On Mon, 8 Apr 2019 at 13:56, Ben Gamari wrote:
>
> Ara Adkins writes:
>
> > Hey all,
> >
> > I'm trying to submit a minor MR as described on the wiki [0]. I can't
> > seem to find the mentioned
Ara Adkins writes:
> Hey all,
>
> I'm trying to submit a minor MR as described on the wiki [0]. I can't
> seem to find the mentioned 'New Merge Request' button, however. Do I
> need a specific set of permissions to open MRs?
>
> Any pointers would be appreciated.
>
Do you see a "New merge request
Hey all,
I'm trying to submit a minor MR as described on the wiki [0]. I can't
seem to find the mentioned 'New Merge Request' button, however. Do I
need a specific set of permissions to open MRs?
Any pointers would be appreciated.
Best,
_ara
[0] https://gitlab.haskell.org/ghc/ghc/wikis/home#ope
On Sun, 7 Apr 2019 at 16:57, Oleg Grenrus wrote:
>
> On 7.4.2019 17.21, Simon Marlow wrote:
> > As I understand it, the aim is to support workflows like "cabal
> > install $pkg; ghci" (amongst other things). This currently works with
> > 'cabal install' because it installs into the global package
19 matches
Mail list logo
