-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with logging and LVish debug flag #114
Comments
Yeah, it seems like we would need the (nonexistent) cabal feature where we depend on a particular flag setting of the Short of that I think we can only enforce this in our scripts, not in the cabal setup. |
Scripts and Cabal are already causing enough problems.. I was wondering if we could fix this by not relying on logging in tests(unless the test is about logging, of course). We can easily use an IORef with |
Oh, that's fine too... so to kind of manually do logging in the tests. On Tue, Jul 7, 2015 at 12:04 PM, Ömer Sinan Ağacan <notifications@github.com
|
Or, maybe we should follow a convention where we use different package name Cabal doesn't directly support that either of course, so I guess it would On Tue, Jul 7, 2015 at 12:44 PM, Ryan Newton rrnewton@gmail.com wrote:
|
I made some progress on this, tests are now passing when -fdebug is not used(Travis is green), but we're having some problems when it's used. |
Some of the tests depend on logging with
-fdebug
, but others break when-fdebug
is enabled.par-transformers
wants it.lvish
breaks when it's enabled.par-mergesort
takes forever when it's enabled.Not sure about how to solve this yet.
The text was updated successfully, but these errors were encountered: