Jenkins build became unstable: Derby-trunk-suites.All #181

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Jenkins build became unstable: Derby-trunk-suites.All #181

Apache Jenkins Server-2
Reply | Threaded
Open this post in threaded view
|

Fwd: Jenkins build became unstable: Derby-trunk-suites.All #181

Rick Hillegas-3

Does anyone understand what went wrong with this build? The console log says that the build was successful and that there were no errors in the tests. When I search the console log, I can't find any errors or warnings.

Thanks,

-Rick



-------- Forwarded Message --------
Subject: Jenkins build became unstable: Derby-trunk-suites.All #181
Date: Fri, 6 Jul 2018 02:07:27 +0000 (UTC)
From: Apache Jenkins Server [hidden email]
To: [hidden email], [hidden email]


See <https://builds.apache.org/job/Derby-trunk-suites.All/181/display/redirect?page=changes>


Reply | Threaded
Open this post in threaded view
|

Re: Jenkins build became unstable: Derby-trunk-suites.All #181

Bryan Pendleton-3
It seems like a handful of tests failed:

    [junit] Tests run: 339, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 489.468 sec
    [junit] Test org.apache.derbyTesting.functionTests.tests.derbynet._Suite FAILED
    [junit] Running org.apache.derbyTesting.functionTests.tests.tools._Suite
    [junit] Tests run: 129, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 69.327 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.demo._Suite
    [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.12 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.lang._Suite
    [junit] Tests run: 3244, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,631.967 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite
    [junit] Tests run: 8015, Failures: 0, Errors: 8, Skipped: 0, Time elapsed: 1,658.97 sec
    [junit] Test org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite FAILED

You can see a bit more about the failures here:


It looks like there are file permission problems with paths containing internationalized characters.

bryan

On Fri, Jul 6, 2018 at 6:11 AM, Rick Hillegas <[hidden email]> wrote:

Does anyone understand what went wrong with this build? The console log says that the build was successful and that there were no errors in the tests. When I search the console log, I can't find any errors or warnings.

Thanks,

-Rick



-------- Forwarded Message --------
Subject: Jenkins build became unstable: Derby-trunk-suites.All #181
Date: Fri, 6 Jul 2018 02:07:27 +0000 (UTC)
From: Apache Jenkins Server [hidden email]
To: [hidden email], [hidden email]


See <https://builds.apache.org/job/Derby-trunk-suites.All/181/display/redirect?page=changes>



Reply | Threaded
Open this post in threaded view
|

Re: Jenkins build became unstable: Derby-trunk-suites.All #181

Rick Hillegas-3
Thanks for drawing my attention to those failures. The errors all occur when checking the existence of a database before trying to delete it. Have we discussed this issue before?

Thanks,
-Rick

On 7/6/18 6:09 PM, Bryan Pendleton wrote:
It seems like a handful of tests failed:

    [junit] Tests run: 339, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 489.468 sec
    [junit] Test org.apache.derbyTesting.functionTests.tests.derbynet._Suite FAILED
    [junit] Running org.apache.derbyTesting.functionTests.tests.tools._Suite
    [junit] Tests run: 129, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 69.327 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.demo._Suite
    [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.12 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.lang._Suite
    [junit] Tests run: 3244, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,631.967 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite
    [junit] Tests run: 8015, Failures: 0, Errors: 8, Skipped: 0, Time elapsed: 1,658.97 sec
    [junit] Test org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite FAILED

You can see a bit more about the failures here:


It looks like there are file permission problems with paths containing internationalized characters.

bryan

On Fri, Jul 6, 2018 at 6:11 AM, Rick Hillegas <[hidden email]> wrote:

Does anyone understand what went wrong with this build? The console log says that the build was successful and that there were no errors in the tests. When I search the console log, I can't find any errors or warnings.

Thanks,

-Rick



-------- Forwarded Message --------
Subject: Jenkins build became unstable: Derby-trunk-suites.All #181
Date: Fri, 6 Jul 2018 02:07:27 +0000 (UTC)
From: Apache Jenkins Server [hidden email]
To: [hidden email], [hidden email]


See <https://builds.apache.org/job/Derby-trunk-suites.All/181/display/redirect?page=changes>




Reply | Threaded
Open this post in threaded view
|

Re: Jenkins build became unstable: Derby-trunk-suites.All #181

Bryan Pendleton-3
It seems really familiar, but I couldn't find it in a quick search of my own email archives. I have this feeling maybe we noticed it last winter and decided to defer it until other larger issues were addressed.

bryan


On Sat, Jul 7, 2018 at 8:39 AM, Rick Hillegas <[hidden email]> wrote:
Thanks for drawing my attention to those failures. The errors all occur when checking the existence of a database before trying to delete it. Have we discussed this issue before?

Thanks,
-Rick


On 7/6/18 6:09 PM, Bryan Pendleton wrote:
It seems like a handful of tests failed:

    [junit] Tests run: 339, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 489.468 sec
    [junit] Test org.apache.derbyTesting.functionTests.tests.derbynet._Suite FAILED
    [junit] Running org.apache.derbyTesting.functionTests.tests.tools._Suite
    [junit] Tests run: 129, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 69.327 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.demo._Suite
    [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.12 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.lang._Suite
    [junit] Tests run: 3244, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,631.967 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite
    [junit] Tests run: 8015, Failures: 0, Errors: 8, Skipped: 0, Time elapsed: 1,658.97 sec
    [junit] Test org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite FAILED

You can see a bit more about the failures here:


It looks like there are file permission problems with paths containing internationalized characters.

bryan

On Fri, Jul 6, 2018 at 6:11 AM, Rick Hillegas <[hidden email]> wrote:

Does anyone understand what went wrong with this build? The console log says that the build was successful and that there were no errors in the tests. When I search the console log, I can't find any errors or warnings.

Thanks,

-Rick



-------- Forwarded Message --------
Subject: Jenkins build became unstable: Derby-trunk-suites.All #181
Date: Fri, 6 Jul 2018 02:07:27 +0000 (UTC)
From: Apache Jenkins Server [hidden email]
To: [hidden email], [hidden email]


See <https://builds.apache.org/job/Derby-trunk-suites.All/181/display/redirect?page=changes>





Reply | Threaded
Open this post in threaded view
|

Re: Jenkins build became unstable: Derby-trunk-suites.All #181

Rick Hillegas-3
The failures occur while running on Ubuntu xenial (16.04). I installed Ubuntu 16.04 on a VM running in Virtual Box on Windows 10. Then I built Derby and ran the junit tests under Java 10 (I couldn'find the Java 9 jdk). The tests ran cleanly. It's possible that the problem only surfaces when the JDK is Java 9. Or that could be a red herring too. The name of the Jenkins VM seems to be H29. Does anyone know how to reserve that machine and log onto it so that we can understand what is different its environment?

Thanks,
-Rick


On 7/7/18 9:12 AM, Bryan Pendleton wrote:
It seems really familiar, but I couldn't find it in a quick search of my own email archives. I have this feeling maybe we noticed it last winter and decided to defer it until other larger issues were addressed.

bryan


On Sat, Jul 7, 2018 at 8:39 AM, Rick Hillegas <[hidden email]> wrote:
Thanks for drawing my attention to those failures. The errors all occur when checking the existence of a database before trying to delete it. Have we discussed this issue before?

Thanks,
-Rick


On 7/6/18 6:09 PM, Bryan Pendleton wrote:
It seems like a handful of tests failed:

    [junit] Tests run: 339, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 489.468 sec
    [junit] Test org.apache.derbyTesting.functionTests.tests.derbynet._Suite FAILED
    [junit] Running org.apache.derbyTesting.functionTests.tests.tools._Suite
    [junit] Tests run: 129, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 69.327 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.demo._Suite
    [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.12 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.lang._Suite
    [junit] Tests run: 3244, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,631.967 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite
    [junit] Tests run: 8015, Failures: 0, Errors: 8, Skipped: 0, Time elapsed: 1,658.97 sec
    [junit] Test org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite FAILED

You can see a bit more about the failures here:


It looks like there are file permission problems with paths containing internationalized characters.

bryan

On Fri, Jul 6, 2018 at 6:11 AM, Rick Hillegas <[hidden email]> wrote:

Does anyone understand what went wrong with this build? The console log says that the build was successful and that there were no errors in the tests. When I search the console log, I can't find any errors or warnings.

Thanks,

-Rick



-------- Forwarded Message --------
Subject: Jenkins build became unstable: Derby-trunk-suites.All #181
Date: Fri, 6 Jul 2018 02:07:27 +0000 (UTC)
From: Apache Jenkins Server [hidden email]
To: [hidden email], [hidden email]


See <https://builds.apache.org/job/Derby-trunk-suites.All/181/display/redirect?page=changes>






Reply | Threaded
Open this post in threaded view
|

Re: Jenkins build became unstable: Derby-trunk-suites.All #181

Bryan Pendleton-3
You could try re-enabling the "echoproperties" that we commented out
in rev 1832736 (see DERBY-6998) because it was quite noisy.

Perhaps there are some clues in that output that will tell us more
about the particulars of the Jenkins machine environment that relate
to the international character set issues?

bryan


On Sun, Jul 8, 2018 at 8:05 AM, Rick Hillegas <[hidden email]> wrote:
The failures occur while running on Ubuntu xenial (16.04). I installed Ubuntu 16.04 on a VM running in Virtual Box on Windows 10. Then I built Derby and ran the junit tests under Java 10 (I couldn'find the Java 9 jdk). The tests ran cleanly. It's possible that the problem only surfaces when the JDK is Java 9. Or that could be a red herring too. The name of the Jenkins VM seems to be H29. Does anyone know how to reserve that machine and log onto it so that we can understand what is different its environment?

Thanks,
-Rick



On 7/7/18 9:12 AM, Bryan Pendleton wrote:
It seems really familiar, but I couldn't find it in a quick search of my own email archives. I have this feeling maybe we noticed it last winter and decided to defer it until other larger issues were addressed.

bryan


On Sat, Jul 7, 2018 at 8:39 AM, Rick Hillegas <[hidden email]> wrote:
Thanks for drawing my attention to those failures. The errors all occur when checking the existence of a database before trying to delete it. Have we discussed this issue before?

Thanks,
-Rick


On 7/6/18 6:09 PM, Bryan Pendleton wrote:
It seems like a handful of tests failed:

    [junit] Tests run: 339, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 489.468 sec
    [junit] Test org.apache.derbyTesting.functionTests.tests.derbynet._Suite FAILED
    [junit] Running org.apache.derbyTesting.functionTests.tests.tools._Suite
    [junit] Tests run: 129, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 69.327 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.demo._Suite
    [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.12 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.lang._Suite
    [junit] Tests run: 3244, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,631.967 sec
    [junit] Running org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite
    [junit] Tests run: 8015, Failures: 0, Errors: 8, Skipped: 0, Time elapsed: 1,658.97 sec
    [junit] Test org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite FAILED

You can see a bit more about the failures here:


It looks like there are file permission problems with paths containing internationalized characters.

bryan

On Fri, Jul 6, 2018 at 6:11 AM, Rick Hillegas <[hidden email]> wrote:

Does anyone understand what went wrong with this build? The console log says that the build was successful and that there were no errors in the tests. When I search the console log, I can't find any errors or warnings.

Thanks,

-Rick



-------- Forwarded Message --------
Subject: Jenkins build became unstable: Derby-trunk-suites.All #181
Date: Fri, 6 Jul 2018 02:07:27 +0000 (UTC)
From: Apache Jenkins Server [hidden email]
To: [hidden email], [hidden email]


See <https://builds.apache.org/job/Derby-trunk-suites.All/181/display/redirect?page=changes>







Reply | Threaded
Open this post in threaded view
|

Jenkins build is back to stable : Derby-trunk-suites.All #182

Apache Jenkins Server-2
In reply to this post by Apache Jenkins Server-2
Reply | Threaded
Open this post in threaded view
|

Fwd: Jenkins build is back to stable : Derby-trunk-suites.All #182

Rick Hillegas-3

For what it's worth, this successful build/test cycle ran on Ubuntu 14.04 as opposed to the failed cycle, which ran on Ubuntu 16.04. Maybe we should configure the build/test cycle to use 14.04.



-------- Forwarded Message --------
Subject: Jenkins build is back to stable : Derby-trunk-suites.All #182
Date: Thu, 12 Jul 2018 00:54:51 +0000 (UTC)
From: Apache Jenkins Server [hidden email]
To: [hidden email], [hidden email]


See <https://builds.apache.org/job/Derby-trunk-suites.All/182/display/redirect?page=changes>


Reply | Threaded
Open this post in threaded view
|

Re: Jenkins build is back to stable : Derby-trunk-suites.All #182

Bryan Pendleton-3
No objections, though I think that's only a temporary solution.

It's 2018, after all, and even Ubuntu 16.04 is already 4 releases out of date.

bryan


On Wed, Jul 11, 2018 at 7:29 PM, Rick Hillegas <[hidden email]> wrote:

For what it's worth, this successful build/test cycle ran on Ubuntu 14.04 as opposed to the failed cycle, which ran on Ubuntu 16.04. Maybe we should configure the build/test cycle to use 14.04.



-------- Forwarded Message --------
Subject: Jenkins build is back to stable : Derby-trunk-suites.All #182
Date: Thu, 12 Jul 2018 00:54:51 +0000 (UTC)
From: Apache Jenkins Server [hidden email]
To: [hidden email], [hidden email]


See <https://builds.apache.org/job/Derby-trunk-suites.All/182/display/redirect?page=changes>



Reply | Threaded
Open this post in threaded view
|

Re: Jenkins build is back to stable : Derby-trunk-suites.All #182

Rick Hillegas-3
I have changed the operating system from "ubuntu" to "ubuntu && trusty" and I have kicked off a build. Let's see if this works...

Thanks,
-Rick

On 7/11/18 7:49 PM, Bryan Pendleton wrote:
No objections, though I think that's only a temporary solution.

It's 2018, after all, and even Ubuntu 16.04 is already 4 releases out of date.

bryan


On Wed, Jul 11, 2018 at 7:29 PM, Rick Hillegas <[hidden email]> wrote:

For what it's worth, this successful build/test cycle ran on Ubuntu 14.04 as opposed to the failed cycle, which ran on Ubuntu 16.04. Maybe we should configure the build/test cycle to use 14.04.



-------- Forwarded Message --------
Subject: Jenkins build is back to stable : Derby-trunk-suites.All #182
Date: Thu, 12 Jul 2018 00:54:51 +0000 (UTC)
From: Apache Jenkins Server [hidden email]
To: [hidden email], [hidden email]


See <https://builds.apache.org/job/Derby-trunk-suites.All/182/display/redirect?page=changes>