You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metron.apache.org by justinleet <gi...@git.apache.org> on 2017/04/26 11:48:26 UTC

[GitHub] incubator-metron issue #459: METRON-726: Clean up mvn site generation

Github user justinleet commented on the issue:

    https://github.com/apache/incubator-metron/pull/459
  
    @dlyle65535, @mmiklavc, @mattf-horton Update here, I'm interested in your thoughts, given the following.
    
    This has been sitting here awhile and I've been trying to play with it to resolve issues, but I'm honestly not sure I can easily resolve them.  Errors are intermittent and inconsistent. To complicate matters, this appears to be the case on master as well.
    
    I've been doing a pretty simple `while true; do date; mvn clean install; sleep 5; done >> ~/log_file 2>&1 ` to just run the build in a loop and see what comes up.  It's possible some of this is an artifact of running it in a loop like this, and I can definitely run it up in a Travis repeatedly to see if the same problems show (and I haven't seen Travis issues in a while that appear to be this branch's issue).  Having said that, it's worrying that our build is (very) unstable on both this branch and master when run like this.
    
    A lot of these seem to be related to our integration tests with the in memory components.  I don't see anything obviously wrong (although I did add some code to make sure ComponentRunners actually get cleaned up in finallys which may help a bit, but didn't resolve it).
    
    I'm not at all sure how to move forward on this, given that the state of master itself makes it almost impossible (unless someone has a clever idea!) to know if each issue is in this branch or not since every issue is intermittent.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---