You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2009/03/17 20:22:50 UTC

[jira] Created: (DERBY-4100) intermittent test failure 10.3 with weme6.1 in lang/logStream.java

intermittent test failure 10.3 with weme6.1 in lang/logStream.java
------------------------------------------------------------------

                 Key: DERBY-4100
                 URL: https://issues.apache.org/jira/browse/DERBY-4100
             Project: Derby
          Issue Type: Bug
    Affects Versions: 10.3.3.1
            Reporter: Myrna van Lunteren
            Priority: Minor


I've seen this twice - first on 3/10 with 10.3.3.1 - (752355), and then on 3/16 with 10.3.3.1 - (755092). 
The diff is like so:
3a4,8
> derby.log has content ?  false
> SHUTDOWN Derby
> SHUTDOWN :Derby system shutdown.
> derby.log exists ?       true
> derby.log is directory ? false
5,9d9
< SHUTDOWN Derby
< SHUTDOWN :Derby system shutdown.
< derby.log exists ?       true
< derby.log is directory ? false
< derby.log has content ?  true

This diff is confusing, basically, the test reports that derby.log has no content, whereas the master shows it expects output.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (DERBY-4100) intermittent test failure 10.3 with weme6.1 in lang/logStream.java

Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683592#action_12683592 ] 

Myrna van Lunteren commented on DERBY-4100:
-------------------------------------------

Now I've also seen this with 10.2 (revision 755814 and wctme5.7(foundation 1.0)). And again on 10.3 (revision 755813 and weme6.1 (foundation 1.1)).



> intermittent test failure 10.3 with weme6.1 in lang/logStream.java
> ------------------------------------------------------------------
>
>                 Key: DERBY-4100
>                 URL: https://issues.apache.org/jira/browse/DERBY-4100
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.3.3.1
>            Reporter: Myrna van Lunteren
>            Priority: Minor
>
> I've seen this twice - first on 3/10 with 10.3.3.1 - (752355), and then on 3/16 with 10.3.3.1 - (755092). 
> The diff is like so:
> 3a4,8
> > derby.log has content ?  false
> > SHUTDOWN Derby
> > SHUTDOWN :Derby system shutdown.
> > derby.log exists ?       true
> > derby.log is directory ? false
> 5,9d9
> < SHUTDOWN Derby
> < SHUTDOWN :Derby system shutdown.
> < derby.log exists ?       true
> < derby.log is directory ? false
> < derby.log has content ?  true
> This diff is confusing, basically, the test reports that derby.log has no content, whereas the master shows it expects output.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (DERBY-4100) intermittent test failure 10.3 with weme6.1 in lang/logStream.java

Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Matrigali updated DERBY-4100:
----------------------------------

    Component/s: Test

> intermittent test failure 10.3 with weme6.1 in lang/logStream.java
> ------------------------------------------------------------------
>
>                 Key: DERBY-4100
>                 URL: https://issues.apache.org/jira/browse/DERBY-4100
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.3.3.1
>            Reporter: Myrna van Lunteren
>            Priority: Minor
>
> I've seen this twice - first on 3/10 with 10.3.3.1 - (752355), and then on 3/16 with 10.3.3.1 - (755092). 
> The diff is like so:
> 3a4,8
> > derby.log has content ?  false
> > SHUTDOWN Derby
> > SHUTDOWN :Derby system shutdown.
> > derby.log exists ?       true
> > derby.log is directory ? false
> 5,9d9
> < SHUTDOWN Derby
> < SHUTDOWN :Derby system shutdown.
> < derby.log exists ?       true
> < derby.log is directory ? false
> < derby.log has content ?  true
> This diff is confusing, basically, the test reports that derby.log has no content, whereas the master shows it expects output.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (DERBY-4100) intermittent test failure 10.3 with weme6.1 in lang/logStream.java

Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695260#action_12695260 ] 

Mamta A. Satoor commented on DERBY-4100:
----------------------------------------

I saw it on 10.1.3.3 codeline revision 759424 on ibm1.4.2

> intermittent test failure 10.3 with weme6.1 in lang/logStream.java
> ------------------------------------------------------------------
>
>                 Key: DERBY-4100
>                 URL: https://issues.apache.org/jira/browse/DERBY-4100
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.3.3.1
>            Reporter: Myrna van Lunteren
>            Priority: Minor
>
> I've seen this twice - first on 3/10 with 10.3.3.1 - (752355), and then on 3/16 with 10.3.3.1 - (755092). 
> The diff is like so:
> 3a4,8
> > derby.log has content ?  false
> > SHUTDOWN Derby
> > SHUTDOWN :Derby system shutdown.
> > derby.log exists ?       true
> > derby.log is directory ? false
> 5,9d9
> < SHUTDOWN Derby
> < SHUTDOWN :Derby system shutdown.
> < derby.log exists ?       true
> < derby.log is directory ? false
> < derby.log has content ?  true
> This diff is confusing, basically, the test reports that derby.log has no content, whereas the master shows it expects output.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.