db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <Knut.Hat...@Sun.COM>
Subject Re: [jira] Resolved: (DERBY-2677) OnlineCompressTest failed reporting NullPointerException, actual problem in derby.log is a page checksum error.
Date Mon, 16 Jun 2008 11:29:36 GMT
Kristian Waagan <Kristian.Waagan@Sun.COM> writes:

> Knut Anders Hatlen (JIRA) wrote:
>>      [ https://issues.apache.org/jira/browse/DERBY-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> Knut Anders Hatlen resolved DERBY-2677.
>> ---------------------------------------
>>     Resolution: Duplicate
>> I don't think this failure has been seen after the fix for DERBY-3347 went in, so
I'm closing the issue. If it happens again, please reopen or file a new bug.
> Do you mean close or resolve?

I meant resolve. Have updated the comment.

> And what is our policy on closing when it comes to issues resolved as
> duplicates again?

I don't know if we have any formal policy, but I would expect that it's
more or less the same as how it's normally done for issues that are
resolved as fixed: The reporter verifies that the problem has been
resolved and closes the issue, or reopens it if the problem is still
present. If there is no feedback within a reasonable period of time, we
just assume that the resolution is OK and go ahead and close the issue.

Knut Anders

View raw message