Master is not validating

Thomas Miedema thomasmiedema at gmail.com
Thu Aug 6 11:00:53 UTC 2015


Simon,

your two most recent commits are not passing validate, see
https://phabricator.haskell.org/diffusion/GHC/history

The first commit fails with a type error, though it seems you fixed this in
the second commit.

The second commit fails with:

*** unexpected pass for T8968-3(normal)
*** unexpected pass for T8968-1(normal)

When master is not passing validate, patch submissions to Phabricator will
not pass validate either.

When master is passing validate again, click 'Restart build' on the
Phabricator Build you were investigating, and the results should be much
clearer.

Thomas



On Thu, Aug 6, 2015 at 12:22 PM, Simon Peyton Jones <simonpj at microsoft.com>
wrote:

> |  Indeed it appears that there is trouble on the `master` branch at the
> |  moment. I'll be looking into this.
>
> I find it difficult to interpret Phab results.  Eg
>         https://phabricator.haskell.org/B5172
> says both "failed" and "passed".
>
> Also the build logs displayed eg here
>         https://phabricator.haskell.org/harbormaster/build/5394/?l=0
> are truncated so you can't see what the exact failure was.
>
> But from the latter I'm guessing that the problem is:
> - I added a new warning
> - And I think validate uses -Wall and fails if any warning happens
>   (which seems a bit brutal)
>
> The warnings are, I think legitimate.  But I certainly don't want them to
> break the build. How to fix?
>   * Remove -fwarn-all-missed-specialisations from -Wall.
>   * Or add -fno-warn-all-missed-specialisations to validate
>
> I don't have a strong opinion.  Can you do one or t'other?
>
> -fwarn-all-missed-specialisations says that there are overloaded functions
> being called without being specialised.  That's quite interesting, and it's
> the kind of thing you'd like to see with "all warnings".  But it's also
> perfectly reasonable to say "that's fine, I don't care that overloaded
> functions are being called".
>
> Are there any other warnings that -Wall does not include? That is, do we
> expect -Wall to mean "all" or just "nearly all"?
>
> I have no strong opinion.
>
> Apologies for causing this fuss.
>
> Simon
>
> |  -----Original Message-----
> |  From: noreply at phabricator.haskell.org
> |  [mailto:noreply at phabricator.haskell.org]
> |  Sent: 06 August 2015 10:56
> |  To: Simon Peyton Jones
> |  Subject: [Differential] [Requested Changes To] D1133: Make derived
> |  names deterministic
> |
> |  bgamari requested changes to this revision.
> |  bgamari added a comment.
> |  This revision now requires changes to proceed.
> |
> |  Indeed it appears that there is trouble on the `master` branch at the
> |  moment. I'll be looking into this.
> |
> |  The idea here looks reasonable, but what effect does this have on the
> |  size of the build artifacts (e.g. object and interface files). It
> |  seems like the names may grow substantially with this change. Could
> |  you characterize this?
> |
> |  Also, I would really like to see some haddocks on the top-level
> |  bindings that are introduced here.
> |
> |
> |  REPOSITORY
> |    rGHC Glasgow Haskell Compiler
> |
> |  REVISION DETAIL
> |    https://phabricator.haskell.org/D1133
> |
> |  EMAIL PREFERENCES
> |    https://phabricator.haskell.org/settings/panel/emailpreferences/
> |
> |  To: niteria, simonmar, simonpj, austin, bgamari
> |  Cc: thomie
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20150806/fee05766/attachment.html>


More information about the ghc-devs mailing list