[GHC] #13122: Investigate reporting build errors with harbormaster.sendmessage

GHC ghc-devs at haskell.org
Sat Jan 14 18:15:44 UTC 2017


#13122: Investigate reporting build errors with harbormaster.sendmessage
-------------------------------------+-------------------------------------
           Reporter:  mpickering     |             Owner:
               Type:  task           |            Status:  new
           Priority:  normal         |         Milestone:
          Component:  Compiler       |           Version:
           Keywords:                 |  Operating System:  Unknown/Multiple
       Architecture:                 |   Type of failure:  None/Unknown
  Unknown/Multiple                   |
          Test Case:                 |        Blocked By:
           Blocking:                 |   Related Tickets:
Differential Rev(s):                 |         Wiki Page:
-------------------------------------+-------------------------------------
 The phabricator API provides a method `harbormaster.sendmessage` which
 allows builds to report information back so that it is displayed on the
 interface. The goal is to avoid having to delve into the build logs in
 order to investigate failures.

 Information about the API method can be found in
 [https://phabricator.haskell.org/conduit/method/harbormaster.sendmessage/
 conduit].

 The API provides a rich set of options to report different information
 about a build.

 Some ideas:

 * Reporting the precise location of all terminal build errors
 * Reporting the outcome of all tests (this might be quite noisy but the
 only way to see is to try!)

 I don't know whether this is a good idea or how it works precisely but
 integrating harbourmaster with differential would be an efficiency gain.

 This is potentially related to #8809.

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/13122>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler


More information about the ghc-tickets mailing list