db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "TestRegressions" by DavidVanCouvering
Date Fri, 20 Jan 2006 23:37:47 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by DavidVanCouvering:
http://wiki.apache.org/db-derby/TestRegressions

------------------------------------------------------------------------------
  
  What follows are guidelines for how test regressions should be handled
  
- * A committer is responsible for committing changes that do not regress the tests.  If they
notice that a commit they made appears to have caused a test failure, they should immediately
work to resolve it, working with the contributor if necessary.  Of course a committer can
not test on all platforms, and may not even be able to resolve a test failure on a platform
to which they do not have access, so in some cases, they may need to work with someone whose
itch is to have Derby work on that platform to fix the test
+  * A committer is responsible for committing changes that do not regress the tests.  If
they notice that a commit they made appears to have caused a test failure, they should immediately
work to resolve it, working with the contributor if necessary.  Of course a committer can
not test on all platforms, and may not even be able to resolve a test failure on a platform
to which they do not have access, so in some cases, they may need to work with someone whose
itch is to have Derby work on that platform to fix the test
  
- * If anyone notices that a test that is failing and it is not immediately resolved, you
are strongly encouraged to log a JIRA issue for it.  The issue should be given a high priority
(Critical for any test failure that crosses all platforms) and assigned to the JIRA category
Regression.
+  * If anyone notices that a test that is failing and it is not immediately resolved, you
are strongly encouraged to log a JIRA issue for it.  The issue should be given a high priority
(Critical for any test failure that crosses all platforms) and assigned to the JIRA category
Regression.
  
- * Any time a known intermittent test failure occurs in publicly posted results, you are
strongly encouraged to put a comment in the issue that the test failed that day to provide
a historical record and also to provide needed attention to issues that commonly occur.
+  * Any time a known intermittent test failure occurs in publicly posted results, you are
strongly encouraged to put a comment in the issue that the test failed that day to provide
a historical record and also to provide needed attention to issues that commonly occur.
  
- * If necessary, a committer may take the matter into their own hands by directly contacting
the person they believe is responsible for the regression or even vetoing all code commits
that are not related to removing test regressions.
+  * If necessary, a committer may take the matter into their own hands by veto'ing and reverting
the patch (commit-then-review), or even vetoing all code commits that are not related to removing
test regressions.
  
- * For some test regressions, the issue may be minor and fixing the test may be significant.
 In this case the test should be removed from derbyall, or configured to not run in the configurations
which cause failures, and the JIRA issue category should be changed to Test.
+  * For some test regressions, the issue may be minor and fixing the test may be significant.
 In this case the test should be removed from derbyall, or configured to not run in the configurations
which cause failures, and the JIRA issue category should be changed to Test.
+   
  

Mime
View raw message