Re: Failing Test Cases in HEAD

`devel2` compiles GHC with extra assertions and `./validate` doesn't do that. There's `./validate --slow` that enables extra assertions. AFAIK harbormaster (and most ghc-devs) only does `./validate` which explains how failures like this can sneak in. We used to have a travis build that did

RE: failing

Simon Peyton Jones writes: > Can you? With comment etc. > Of course. Cheers, - Ben signature.asc Description: PGP signature ___ ghc-devs mailing list ghc-devs@haskell.org

RE: failing

yped.com> | Cc: ghc-devs@haskell.org | Subject: Re: failing | | On October 12, 2016 8:27:24 AM EDT, Simon Peyton Jones via ghc-devs | <ghc-devs@haskell.org> wrote: | >Ben: all builds are failing | >https://phabricator.haskell.org/harbormaster/ | >What’s up? I see a perf

Re: failing

On October 12, 2016 8:27:24 AM EDT, Simon Peyton Jones via ghc-devs wrote: >Ben: all builds are failing >https://phabricator.haskell.org/harbormaster/ >What’s up? I see a perf failure on T1969. Does not happen for me; and >is only in residency, so just bump it? > >Simon >

Re: Failing tests: literals T5681 annotations

On Tue, Dec 2, 2014 at 5:58 PM, Joachim Breitner m...@joachim-breitner.de wrote: Hi, Am Sonntag, den 30.11.2014, 20:01 +0100 schrieb Joachim Breitner: I’m still seeing this failure: Compile failed (status 256) errors were: /tmp/ghc16123_0/ghc16123_5.s: Assembler messages:

Re: Failing tests: literals T5681 annotations

Hi, Am Sonntag, den 30.11.2014, 20:01 +0100 schrieb Joachim Breitner: I’m still seeing this failure: Compile failed (status 256) errors were: /tmp/ghc16123_0/ghc16123_5.s: Assembler messages: /tmp/ghc16123_0/ghc16123_5.s:26:0: Error: can't resolve `.rodata' {.rodata section} -

Re: Failing tests: literals T5681 annotations

Hi, I’m still seeing this failure: Compile failed (status 256) errors were: /tmp/ghc16123_0/ghc16123_5.s: Assembler messages: /tmp/ghc16123_0/ghc16123_5.s:26:0: Error: can't resolve `.rodata' {.rodata section} - `Main_zdwwork_info$def' {.text section} /tmp/ghc16123_0/ghc16123_5.s:46:0:

Re: Failing tests: literals T5681 annotations

Hi, Am Samstag, den 22.11.2014, 11:35 +0100 schrieb Joachim Breitner: I currently observe Unexpected results from: TEST=literals T5681 annotations this has improved to just TEST=T5681 annotations but still this needs some investigation. Maybe a problem with parallel test runs and

RE: Failing ASSERT in ghci044 and ghci047

Thanks. These are tests that over-ride one instance declaration with another, something that really wasn't working before. I have no idea what is going on in Linker.hs It's the weekend so I'm not going to have a chance to look at this for a bit -- and oddly it seems to work anyway. But