You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "ctubbsii (via GitHub)" <gi...@apache.org> on 2023/08/02 08:34:10 UTC

[GitHub] [accumulo] ctubbsii commented on issue #3646: Refactor scan consistency IT so that it can also be run standalone

ctubbsii commented on issue #3646:
URL: https://github.com/apache/accumulo/issues/3646#issuecomment-1661751469

   > > As a long running test, would this be more fitting to move to AccumuloTesting? Or do you think it should stay here?
   > 
   > I think its nice to have as an IT that stresses a lot of functionality together that's always expected to work (that is why I added it as a sunny day test). So I think its nice to leave it here.
   
   I think the point of the sunny day test suite is that they test base functionality, and is something that gives us a quick "yes" or "no" on mergability for any particular patch or contribution. If one of those tests fails, it means Accumulo stopped doing basic things, like starting up, or communicating between server types. These are tests we expect a contributor to have not broken, and should be fast enough to run the whole batch of them on a modest developer hardware, like a contributor's personal laptop. I don't think we should be putting stress tests in there, or edge case coverage, or anything that is nondeterministic or flaky. Of those, I'd consider this test "edge case coverage", and don't think it warrants making sunny take longer to execute.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org