Skip to content
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

Open
osa1 opened this issue Jul 6, 2015 · 5 comments
Open

Problems with logging and LVish debug flag #114

osa1 opened this issue Jul 6, 2015 · 5 comments

Comments

@osa1
Copy link
Member

osa1 commented Jul 6, 2015

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.

@rrnewton
Copy link
Member

rrnewton commented Jul 6, 2015

Yeah, it seems like we would need the (nonexistent) cabal feature where we depend on a particular flag setting of the lvish package from the test-suite section.

Short of that I think we can only enforce this in our scripts, not in the cabal setup.

@osa1
Copy link
Member Author

osa1 commented Jul 7, 2015

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 internalLiftIO to collect logs. How does that sound?

@rrnewton
Copy link
Member

rrnewton commented Jul 7, 2015

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 <[email protected]

wrote:

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 internalLiftIO
to collect logs. How does that sound?


Reply to this email directly or view it on GitHub
#114 (comment).

@rrnewton
Copy link
Member

rrnewton commented Jul 7, 2015

Or, maybe we should follow a convention where we use different package name
for the debug version e.g. "lvish-debug".

Cabal doesn't directly support that either of course, so I guess it would
have to be a separate cabal file.-

On Tue, Jul 7, 2015 at 12:44 PM, Ryan Newton [email protected] wrote:

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 <
[email protected]> wrote:

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 internalLiftIO
to collect logs. How does that sound?


Reply to this email directly or view it on GitHub
#114 (comment).

@osa1
Copy link
Member Author

osa1 commented Jul 8, 2015

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.

@osa1 osa1 removed their assignment Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants