Github user kxepal commented on the pull request:

    https://github.com/apache/couchdb-chttpd/pull/10#issuecomment-65086583
  
    > however, do we need to have "httpd_handler_callback_test:206:" before 
each output line? 
    
    That will save a lot of time if something will go wrong since it directly 
points on the exact line in exact module where to start your search. 
    
    > I don't know what apache/couchdb-chttpd does differently with the eunit 
setup but the same test source did not print these module:line hints before 
every line. 
    
    IIRC that's some eunit internal thing about using `setup`. I'd fight with 
the output year ago and might be forgot all the details, but one I know for 
sure:  it's an easy to produce useless test report with eunit. Need to note, 
that I'm care here about further test suite support.
    
    > Also, I am using io:format to prevent even more prefix in each line and I 
will try out your setup but all I ever found was that ?debugFmt inevitably adds 
to the line. I did not invent using io:format(user, ... that is from the Eunit 
docs, the way to produce screen output.
    
    Sorry if "reinvent" was sound a bit rude. The problem of io:format that it 
will always print things to stdout. As for ?debug, you can turn this output off 
after defining NODEBUG leaving whole report clean. 
    
    > I polished this output to be concise because I needed to find a race 
condition that only became apparent in the logs.
    
    Sounds like you'll have to add another case on that (; Good luck with 
chasing RC - that's not an easy.
    
    > From that I got to appreciate briefer, readable, cleaned up logs and 
modelled it after the etap output. 
    
    I see. Well, for eunit other tests are already uses the "default" output 
format, so if you think it could be improved, it need to be improved everywhere.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to