CI request: a DEBUG compiler

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

CI request: a DEBUG compiler

Richard Eisenberg-4
Hi devs,

I almost exclusively work with a DEBUG compiler. It continually shocks me that I'm relatively alone in this stance, as the ASSERTs littered throughout GHC have caught many a bug in easier a manner than long stares at -ddump-tc-trace would do. In any case, my goal in this email is not to convince you to follow suit. My goal is to request that our CI infrastructure include at least one testsuite run in a DEBUG compiler. A patch I'm working on is failing a test because of an assertion failure. I doubt my patch is the culprit, but I also can't categorically rule it out. So, I'm left rebuilding HEAD with DEBUG turned on to see if I can repro the ASSERTion failure. Clearly, having a CI trace of this would simplify things -- not to mention catch bugs earlier.

Thanks!
Richard
_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Reply | Threaded
Open this post in threaded view
|

Re: CI request: a DEBUG compiler

Ben Gamari-2
Richard Eisenberg <[hidden email]> writes:

> Hi devs,
>
> I almost exclusively work with a DEBUG compiler. It continually shocks
> me that I'm relatively alone in this stance, as the ASSERTs littered
> throughout GHC have caught many a bug in easier a manner than long
> stares at -ddump-tc-trace would do. In any case, my goal in this email
> is not to convince you to follow suit. My goal is to request that our
> CI infrastructure include at least one testsuite run in a DEBUG
> compiler. A patch I'm working on is failing a test because of an
> assertion failure. I doubt my patch is the culprit, but I also can't
> categorically rule it out. So, I'm left rebuilding HEAD with DEBUG
> turned on to see if I can repro the ASSERTion failure. Clearly, having
> a CI trace of this would simplify things -- not to mention catch bugs
> earlier.
>
I completely agree; we do need to test DEBUG. I have an open merge
request (!58) which adds support for this but it currently fails (!) and
I haven't had time to look at sorting it out. I'll try to have a look today.

Cheers,

- Ben


_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

signature.asc (497 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: CI request: a DEBUG compiler

Joachim Breitner-2
In reply to this post by Richard Eisenberg-4
Hi,

Am Sonntag, den 27.01.2019, 09:56 -0500 schrieb Richard Eisenberg:
> Clearly, having a CI trace of this would simplify things -- not to
> mention catch bugs earlier.

absolutely agree, and I can’t help but notice that our first CI setup
on travis that I created four years ago had a DEBUG build right from
the start.

(And back then I also noticed that not many developers seem to be using
a DEBUG build…)

Cheers,
Joachim
--
Joachim Breitner
  [hidden email]
  http://www.joachim-breitner.de/


_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

signature.asc (849 bytes) Download Attachment