4.16 I-Build: I20200513-1800

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

4.16 I-Build: I20200513-1800

genie.releng
Eclipse downloads:
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800

Build logs and/or test results (eventually):
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800/testResults.php

Software site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds

Specific (simple) site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds/I20200513-1800

Equinox downloads:
https://download.eclipse.org/equinox/drops/I20200513-1800


_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
Reply | Threaded
Open this post in threaded view
|

Re: 4.16 I-Build: I20200513-1800

Sravan K Lakkimsetti

Hi,

 

Java 14 configuration failed with “java.lang.OutOfMemoryError: Java heap space“

Log: https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/console

Max memory allocated for the container is 2GB. I believe this should be sufficient. I can go till 4GB if required

 

Is this related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=553538 ?

 

Thanks

Sravan

 

From: [hidden email] <[hidden email]>
Sent: 14 May 2020 05:57
To: [hidden email]
Subject: [EXTERNAL] [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Eclipse downloads:
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800

Build logs and/or test results (eventually):
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800/testResults.php

Software site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds

Specific (simple) site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds/I20200513-1800

Equinox downloads:
https://download.eclipse.org/equinox/drops/I20200513-1800

_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 



_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
Reply | Threaded
Open this post in threaded view
|

Re: 4.16 I-Build: I20200513-1800

Daniel Megert
Did you check whether the OOME also happens with the last good build? If not, please do so.

Dani



From:        "Sravan K Lakkimsetti" <[hidden email]>
To:        "Eclipse platform release engineering list." <[hidden email]>
Date:        14.05.2020 12:39
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        [hidden email]



Hi,

 

Java 14 configuration failed with “java.lang.OutOfMemoryError: Java heap space“

Log: https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/console

Max memory allocated for the container is 2GB. I believe this should be sufficient. I can go till 4GB if required

 

Is this related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=553538?

 

Thanks

Sravan

 

From:[hidden email] <[hidden email]>
Sent:
14 May 2020 05:57
To:
[hidden email]
Subject:
[EXTERNAL] [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Eclipse downloads:
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800

Build logs and/or test results (eventually):

https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800/testResults.php

Software site repository:

https://download.eclipse.org/eclipse/updates/4.16-I-builds

Specific (simple) site repository:

https://download.eclipse.org/eclipse/updates/4.16-I-builds/I20200513-1800

Equinox downloads:

https://download.eclipse.org/equinox/drops/I20200513-1800

_______________________________________________

platform-releng-dev mailing list


[hidden email]

To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 


_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev




_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
Reply | Threaded
Open this post in threaded view
|

Re: 4.16 I-Build: I20200513-1800

Sravan K Lakkimsetti

Hi Dani,

 

This started with Build: I20200512-1800. We didn’t have this problem before that

 

-Sravan

 

From: Daniel Megert <[hidden email]>
Sent: 14 May 2020 16:38
To: Eclipse platform release engineering list. <[hidden email]>
Subject: [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Did you check whether the OOME also happens with the last good build? If not, please do so.

Dani



From:        "Sravan K Lakkimsetti" <[hidden email]>
To:        "Eclipse platform release engineering list." <[hidden email]>
Date:        14.05.2020 12:39
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        [hidden email]


 

Hi,

 

Java 14 configuration failed with “java.lang.OutOfMemoryError: Java heap space“

Log: https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/console

Max memory allocated for the container is 2GB. I believe this should be sufficient. I can go till 4GB if required

 

Is this related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=553538?

 

Thanks

Sravan

 

From:[hidden email] <[hidden email]>
Sent:
14 May 2020 05:57
To:
[hidden email]
Subject:
[EXTERNAL] [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Eclipse downloads:
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800

Build logs and/or test results (eventually):
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800/testResults.php

Software site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds

Specific (simple) site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds/I20200513-1800

Equinox downloads:
https://download.eclipse.org/equinox/drops/I20200513-1800

_______________________________________________

platform-releng-dev mailing list


[hidden email]

To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 


_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev




_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
Reply | Threaded
Open this post in threaded view
|

Re: 4.16 I-Build: I20200513-1800

Daniel Megert
Hi Sravan

Yes, I know that. The questions is: does rerunning the tests from the last good build work or not. If yes, we have to investigate why it now uses more memory. Is there a way to check how much is used?

Dani



From:        "Sravan K Lakkimsetti" <[hidden email]>
To:        "Eclipse platform release engineering list." <[hidden email]>
Date:        14.05.2020 13:15
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        [hidden email]



Hi Dani,

 

This started with Build: I20200512-1800. We didn’t have this problem before that

 

-Sravan

 

From:Daniel Megert <[hidden email]>
Sent:
14 May 2020 16:38
To:
Eclipse platform release engineering list. <[hidden email]>
Subject:
[EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Did you check whether the OOME also happens with the last good build? If not, please do so.

Dani




From:        
"Sravan K Lakkimsetti" <sravankumarl@...>
To:        
"Eclipse platform release engineering list." <[hidden email]>
Date:        
14.05.2020 12:39
Subject:        
[EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        
[hidden email]


 

Hi,

 

Java 14 configuration failed with “java.lang.OutOfMemoryError: Java heap space“

Log: https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/console

Max memory allocated for the container is 2GB. I believe this should be sufficient. I can go till 4GB if required

 

Is this related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=553538?

 

Thanks

Sravan

 

From:[hidden email] <genie.releng@...>
Sent:
14 May 2020 05:57
To:
[hidden email]
Subject:
[EXTERNAL] [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Eclipse downloads:
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800

Build logs and/or test results (eventually):

https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800/testResults.php

Software site repository:

https://download.eclipse.org/eclipse/updates/4.16-I-builds

Specific (simple) site repository:

https://download.eclipse.org/eclipse/updates/4.16-I-builds/I20200513-1800

Equinox downloads:

https://download.eclipse.org/equinox/drops/I20200513-1800

_______________________________________________

platform-releng-dev mailing list


[hidden email]

To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 


_______________________________________________
platform-releng-dev mailing list

[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev


_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev




_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
Reply | Threaded
Open this post in threaded view
|

Re: 4.16 I-Build: I20200513-1800

Sravan K Lakkimsetti

Ok Dani I am running the tests from I20200511-1800. Last time it took more than 8 hours so it may be a while before we get results.

 

Thanks

Sravan

 

From: Daniel Megert <[hidden email]>
Sent: 14 May 2020 16:51
To: Eclipse platform release engineering list. <[hidden email]>
Subject: [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Hi Sravan

Yes, I know that. The questions is: does rerunning the tests from the last good build work or not. If yes, we have to investigate why it now uses more memory. Is there a way to check how much is used?

Dani



From:        "Sravan K Lakkimsetti" <[hidden email]>
To:        "Eclipse platform release engineering list." <[hidden email]>
Date:        14.05.2020 13:15
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        [hidden email]


 

Hi Dani,

 

This started with Build: I20200512-1800. We didn’t have this problem before that

 

-Sravan

 

From:Daniel Megert <[hidden email]>
Sent:
14 May 2020 16:38
To:
Eclipse platform release engineering list. <[hidden email]>
Subject:
[EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Did you check whether the OOME also happens with the last good build? If not, please do so.

Dani




From:        
"Sravan K Lakkimsetti" <[hidden email]>
To:        
"Eclipse platform release engineering list." <
[hidden email]>
Date:        
14.05.2020 12:39
Subject:        
[EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        
[hidden email]


 

Hi,

 

Java 14 configuration failed with “java.lang.OutOfMemoryError: Java heap space“

Log: https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/console

Max memory allocated for the container is 2GB. I believe this should be sufficient. I can go till 4GB if required

 

Is this related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=553538?

 

Thanks

Sravan

 

From:[hidden email] <[hidden email]>
Sent:
14 May 2020 05:57
To:
[hidden email]
Subject:
[EXTERNAL] [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Eclipse downloads:
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800

Build logs and/or test results (eventually):
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800/testResults.php

Software site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds

Specific (simple) site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds/I20200513-1800

Equinox downloads:
https://download.eclipse.org/equinox/drops/I20200513-1800

_______________________________________________

platform-releng-dev mailing list


[hidden email]

To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 


_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev


_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev




_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
Reply | Threaded
Open this post in threaded view
|

Re: 4.16 I-Build: I20200513-1800

Andrey Loskutov
Are we sure we have OOM on the SDK side, not in on the Jenkins agent side? I can't understand the stack below.
 
If I read the stack right, the agent dies trying to *transfer* JUnit test results?
But test aren't executed not in the same JVM where Jenkins agent lives?
Can we access generated JUnit results/logs?May be they are just *huge* for whatever reason?
May be we see after which test it misbehaves (*if* this happens during test phase and not some Jenkins issue).
Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.128.4.1/10.128.4.1:33780
		at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788)
		at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
		at hudson.remoting.Channel.call(Channel.java:998)
		at hudson.FilePath.act(FilePath.java:1069)
		at hudson.FilePath.act(FilePath.java:1058)
		at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114)
		at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137)
		at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167)
		at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:52)
		at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:25)
		at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
		at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$$Lambda$446/0000000030151E30.run(Unknown Source)
		at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
		at java.util.concurrent.FutureTask.run(Unknown Source)
		at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
java.lang.OutOfMemoryError: Java heap space
	at java.util.Arrays.copyOf(Unknown Source)
	at java.io.ByteArrayOutputStream.toByteArray(Unknown Source)
	at hudson.remoting.UserRequest._serialize(UserRequest.java:264)
	at hudson.remoting.UserRequest.serialize(UserRequest.java:272)
	at hudson.remoting.UserRequest.perform(UserRequest.java:222)
	at hudson.remoting.UserRequest.perform(UserRequest.java:54)
	at hudson.remoting.Request$2.run(Request.java:369)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:117)
	at hudson.remoting.Engine$1$$Lambda$4/000000003C01FDE0.run(Unknown Source)
Caused: java.io.IOException: Remote call on JNLP4-connect connection from 10.128.4.1/10.128.4.1:33780 failed
	at hudson.remoting.Channel.call(Channel.java:1004)
	at hudson.FilePath.act(FilePath.java:1069)
	at hudson.FilePath.act(FilePath.java:1058)
	at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114)
	at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137)
	at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167)
	at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:52)
	at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:25)
	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$$Lambda$446/0000000030151E30.run(Unknown Source)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Finished: FAILURE
Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov
 
 
Gesendet: Donnerstag, 14. Mai 2020 um 13:26 Uhr
Von: "Sravan K Lakkimsetti" <[hidden email]>
An: "Eclipse platform release engineering list." <[hidden email]>
Betreff: Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

Ok Dani I am running the tests from I20200511-1800. Last time it took more than 8 hours so it may be a while before we get results.

 

Thanks

Sravan

 

From: Daniel Megert <[hidden email]>
Sent: 14 May 2020 16:51
To: Eclipse platform release engineering list. <[hidden email]>
Subject: [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Hi Sravan

Yes, I know that. The questions is: does rerunning the tests from the last good build work or not. If yes, we have to investigate why it now uses more memory. Is there a way to check how much is used?

Dani



From:        "Sravan K Lakkimsetti" <[hidden email]>
To:        "Eclipse platform release engineering list." <[hidden email]>
Date:        14.05.2020 13:15
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        [hidden email]


 

Hi Dani,

 

This started with Build: I20200512-1800. We didn’t have this problem before that

 

-Sravan

 

From:Daniel Megert <[hidden email]>
Sent: 14 May 2020 16:38
To: Eclipse platform release engineering list. <[hidden email]>
Subject: [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Did you check whether the OOME also happens with the last good build? If not, please do so.

Dani



From:        "Sravan K Lakkimsetti" <[hidden email]>
To:        "Eclipse platform release engineering list." <
[hidden email]>
Date:        14.05.2020 12:39
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        
[hidden email]


 

Hi,

 

Java 14 configuration failed with “java.lang.OutOfMemoryError: Java heap space“

Log: https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/console

Max memory allocated for the container is 2GB. I believe this should be sufficient. I can go till 4GB if required

 

Is this related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=553538?

 

Thanks

Sravan

 

From:[hidden email] <[hidden email]>
Sent: 14 May 2020 05:57
To:
[hidden email]
Subject: [EXTERNAL] [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Eclipse downloads:
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800

Build logs and/or test results (eventually):
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800/testResults.php

Software site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds

Specific (simple) site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds/I20200513-1800

Equinox downloads:
https://download.eclipse.org/equinox/drops/I20200513-1800

_______________________________________________

platform-releng-dev mailing list


[hidden email]

To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 


_______________________________________________
platform-releng-dev mailing list

[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev


_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 


_______________________________________________ platform-releng-dev mailing list [hidden email] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
Reply | Threaded
Open this post in threaded view
|

Re: 4.16 I-Build: I20200513-1800

Sravan K Lakkimsetti

Here are the junit test results and logs https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/artifact/

Hope this helps

 

-Sravan

 

From: Andrey Loskutov <[hidden email]>
Sent: 14 May 2020 17:27
To: [hidden email]
Subject: [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Are we sure we have OOM on the SDK side, not in on the Jenkins agent side? I can't understand the stack below.

 

If I read the stack right, the agent dies trying to *transfer* JUnit test results?

But test aren't executed not in the same JVM where Jenkins agent lives?

Can we access generated JUnit results/logs?May be they are just *huge* for whatever reason?

May be we see after which test it misbehaves (*if* this happens during test phase and not some Jenkins issue).

Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.128.4.1/10.128.4.1:33780
               at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788)
               at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
               at hudson.remoting.Channel.call(Channel.java:998)
               at hudson.FilePath.act(FilePath.java:1069)
               at hudson.FilePath.act(FilePath.java:1058)
               at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114)
               at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137)
               at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167)
               at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:52)
               at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:25)
               at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
               at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$$Lambda$446/0000000030151E30.run(Unknown Source)
               at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
               at java.util.concurrent.FutureTask.run(Unknown Source)
               at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
               at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
java.lang.OutOfMemoryError: Java heap space
        at java.util.Arrays.copyOf(Unknown Source)
        at java.io.ByteArrayOutputStream.toByteArray(Unknown Source)
        at hudson.remoting.UserRequest._serialize(UserRequest.java:264)
        at hudson.remoting.UserRequest.serialize(UserRequest.java:272)
        at hudson.remoting.UserRequest.perform(UserRequest.java:222)
        at hudson.remoting.UserRequest.perform(UserRequest.java:54)
        at hudson.remoting.Request$2.run(Request.java:369)
        at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:117)
        at hudson.remoting.Engine$1$$Lambda$4/000000003C01FDE0.run(Unknown Source)
Caused: java.io.IOException: Remote call on JNLP4-connect connection from 10.128.4.1/10.128.4.1:33780 failed
        at hudson.remoting.Channel.call(Channel.java:1004)
        at hudson.FilePath.act(FilePath.java:1069)
        at hudson.FilePath.act(FilePath.java:1058)
        at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114)
        at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137)
        at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167)
        at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:52)
        at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:25)
        at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
        at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$$Lambda$446/0000000030151E30.run(Unknown Source)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Finished: FAILURE

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

 

 

Gesendet: Donnerstag, 14. Mai 2020 um 13:26 Uhr
Von: "Sravan K Lakkimsetti" <[hidden email]>
An: "Eclipse platform release engineering list." <[hidden email]>
Betreff: Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

Ok Dani I am running the tests from I20200511-1800. Last time it took more than 8 hours so it may be a while before we get results.

 

Thanks

Sravan

 

From: Daniel Megert <[hidden email]>
Sent: 14 May 2020 16:51
To: Eclipse platform release engineering list. <[hidden email]>
Subject: [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Hi Sravan

Yes, I know that. The questions is: does rerunning the tests from the last good build work or not. If yes, we have to investigate why it now uses more memory. Is there a way to check how much is used?

Dani



From:        "Sravan K Lakkimsetti" <[hidden email]>
To:        "Eclipse platform release engineering list." <[hidden email]>
Date:        14.05.2020 13:15
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        [hidden email]


 

Hi Dani,

 

This started with Build: I20200512-1800. We didn’t have this problem before that

 

-Sravan

 

From:Daniel Megert <[hidden email]>
Sent: 14 May 2020 16:38
To: Eclipse platform release engineering list. <[hidden email]>
Subject: [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Did you check whether the OOME also happens with the last good build? If not, please do so.

Dani



From:        "Sravan K Lakkimsetti" <[hidden email]>
To:        "Eclipse platform release engineering list." <
[hidden email]>
Date:        14.05.2020 12:39
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        
[hidden email]


 

Hi,

 

Java 14 configuration failed with “java.lang.OutOfMemoryError: Java heap space“

Log: https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/console

Max memory allocated for the container is 2GB. I believe this should be sufficient. I can go till 4GB if required

 

Is this related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=553538?

 

Thanks

Sravan

 

From:[hidden email] <[hidden email]>
Sent: 14 May 2020 05:57
To:
[hidden email]
Subject: [EXTERNAL] [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Eclipse downloads:
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800

Build logs and/or test results (eventually):
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800/testResults.php

Software site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds

Specific (simple) site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds/I20200513-1800

Equinox downloads:
https://download.eclipse.org/equinox/drops/I20200513-1800

_______________________________________________

platform-releng-dev mailing list


[hidden email]

To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 


_______________________________________________
platform-releng-dev mailing list

[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev


_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 


_______________________________________________ platform-releng-dev mailing list [hidden email] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 



_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
Reply | Threaded
Open this post in threaded view
|

Re: 4.16 I-Build: I20200513-1800

Andrey Loskutov
I see that the size of the all result data nearly doubled from build 71 to 72.
 
In build 71 results from org.eclipse.jdt.core.tests.compiler.regression.TestAll.xml are empty, in following builds it is about 11 MB.
 
 
https://ci-staging.eclipse.org/releng/view/Automated tests/job/ep416I-unit-cen64-gtk3-java14/71/artifact/workarea/I20200511-1800/eclipse-testing/results/ep416I-unit-cen64-gtk3-java14_linux.gtk.x86_64_14/
https://ci-staging.eclipse.org/releng/view/Automated tests/job/ep416I-unit-cen64-gtk3-java14/72/artifact/workarea/I20200512-1800/eclipse-testing/results/ep416I-unit-cen64-gtk3-java14_linux.gtk.x86_64_14/
 
So I assume it is Jenkins who died now with OOM, and because we now have compiler regression tests with lot of output.
 
Before build 72, compiler tests *died* with this stack trace:
 
DumpStackTracesTimer almost reached timeout '7200000'.
totalMemory:            1037959168
freeMemory (before GC): 806520888
freeMemory (after GC):  811775832
Thread dump 0 at 2020-05-12 07:58:42 +0000:
java.lang.Exception: ThreadDump for thread "main"
    at java.base@14/sun.nio.ch.Net.accept(Native Method)
    at java.base@14/sun.nio.ch.NioSocketImpl.accept(NioSocketImpl.java:755)
    at java.base@14/java.net.ServerSocket.implAccept(ServerSocket.java:684)
    at java.base@14/java.net.ServerSocket.platformImplAccept(ServerSocket.java:650)
    at java.base@14/java.net.ServerSocket.implAccept(ServerSocket.java:626)
    at java.base@14/java.net.ServerSocket.implAccept(ServerSocket.java:583)
    at java.base@14/java.net.ServerSocket.accept(ServerSocket.java:540)
    at org.eclipse.jdt.core.tests.util.TestVerifier.launchVerifyTestsIfNeeded(TestVerifier.java:547)
    at org.eclipse.jdt.core.tests.util.TestVerifier.verifyClassFiles(TestVerifier.java:635)
    at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runTest(AbstractRegressionTest.java:3457)
    at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runTest(AbstractRegressionTest.java:3127)
    at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runConformTest(AbstractRegressionTest.java:1851)
    at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runConformTest(AbstractRegressionTest.java:1848)
    at org.eclipse.jdt.core.tests.compiler.regression.ConditionalExpressionTest.test001(ConditionalExpressionTest.java:47)
    at java.base@14/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.base@14/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at java.base@14/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 
So I would increase agent heap and may be re-trigger results parsing if possible? We *have* test results.
 
Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov
 
 
Gesendet: Donnerstag, 14. Mai 2020 um 14:07 Uhr
Von: "Sravan K Lakkimsetti" <[hidden email]>
An: "Eclipse platform release engineering list." <[hidden email]>
Betreff: Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

Here are the junit test results and logs https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/artifact/

Hope this helps

 

-Sravan

 

From: Andrey Loskutov <[hidden email]>
Sent: 14 May 2020 17:27
To: [hidden email]
Subject: [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Are we sure we have OOM on the SDK side, not in on the Jenkins agent side? I can't understand the stack below.

 

If I read the stack right, the agent dies trying to *transfer* JUnit test results?

But test aren't executed not in the same JVM where Jenkins agent lives?

Can we access generated JUnit results/logs?May be they are just *huge* for whatever reason?

May be we see after which test it misbehaves (*if* this happens during test phase and not some Jenkins issue).

Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.128.4.1/10.128.4.1:33780
               at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788)
               at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
               at hudson.remoting.Channel.call(Channel.java:998)
               at hudson.FilePath.act(FilePath.java:1069)
               at hudson.FilePath.act(FilePath.java:1058)
               at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114)
               at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137)
               at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167)
               at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:52)
               at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:25)
               at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
               at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$$Lambda$446/0000000030151E30.run(Unknown Source)
               at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
               at java.util.concurrent.FutureTask.run(Unknown Source)
               at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
               at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
java.lang.OutOfMemoryError: Java heap space
        at java.util.Arrays.copyOf(Unknown Source)
        at java.io.ByteArrayOutputStream.toByteArray(Unknown Source)
        at hudson.remoting.UserRequest._serialize(UserRequest.java:264)
        at hudson.remoting.UserRequest.serialize(UserRequest.java:272)
        at hudson.remoting.UserRequest.perform(UserRequest.java:222)
        at hudson.remoting.UserRequest.perform(UserRequest.java:54)
        at hudson.remoting.Request$2.run(Request.java:369)
        at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:117)
        at hudson.remoting.Engine$1$$Lambda$4/000000003C01FDE0.run(Unknown Source)
Caused: java.io.IOException: Remote call on JNLP4-connect connection from 10.128.4.1/10.128.4.1:33780 failed
        at hudson.remoting.Channel.call(Channel.java:1004)
        at hudson.FilePath.act(FilePath.java:1069)
        at hudson.FilePath.act(FilePath.java:1058)
        at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114)
        at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137)
        at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167)
        at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:52)
        at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:25)
        at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
        at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$$Lambda$446/0000000030151E30.run(Unknown Source)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Finished: FAILURE

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

 

 

Gesendet: Donnerstag, 14. Mai 2020 um 13:26 Uhr
Von: "Sravan K Lakkimsetti" <[hidden email]>
An: "Eclipse platform release engineering list." <[hidden email]>
Betreff: Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

Ok Dani I am running the tests from I20200511-1800. Last time it took more than 8 hours so it may be a while before we get results.

 

Thanks

Sravan

 

From: Daniel Megert <[hidden email]>
Sent: 14 May 2020 16:51
To: Eclipse platform release engineering list. <[hidden email]>
Subject: [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Hi Sravan

Yes, I know that. The questions is: does rerunning the tests from the last good build work or not. If yes, we have to investigate why it now uses more memory. Is there a way to check how much is used?

Dani



From:        "Sravan K Lakkimsetti" <[hidden email]>
To:        "Eclipse platform release engineering list." <[hidden email]>
Date:        14.05.2020 13:15
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        [hidden email]


 

Hi Dani,

 

This started with Build: I20200512-1800. We didn’t have this problem before that

 

-Sravan

 

From:Daniel Megert <[hidden email]>
Sent: 14 May 2020 16:38
To: Eclipse platform release engineering list. <[hidden email]>
Subject: [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Did you check whether the OOME also happens with the last good build? If not, please do so.

Dani



From:        "Sravan K Lakkimsetti" <[hidden email]>
To:        "Eclipse platform release engineering list." <
[hidden email]>
Date:        14.05.2020 12:39
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        
[hidden email]


 

Hi,

 

Java 14 configuration failed with “java.lang.OutOfMemoryError: Java heap space“

Log: https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/console

Max memory allocated for the container is 2GB. I believe this should be sufficient. I can go till 4GB if required

 

Is this related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=553538?

 

Thanks

Sravan

 

From:[hidden email] <[hidden email]>
Sent: 14 May 2020 05:57
To:
[hidden email]
Subject: [EXTERNAL] [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Eclipse downloads:
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800

Build logs and/or test results (eventually):
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800/testResults.php

Software site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds

Specific (simple) site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds/I20200513-1800

Equinox downloads:
https://download.eclipse.org/equinox/drops/I20200513-1800

_______________________________________________

platform-releng-dev mailing list


[hidden email]

To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 


_______________________________________________
platform-releng-dev mailing list

[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev


_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 


_______________________________________________ platform-releng-dev mailing list [hidden email] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 


_______________________________________________ platform-releng-dev mailing list [hidden email] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
Reply | Threaded
Open this post in threaded view
|

Re: 4.16 I-Build: I20200513-1800

Daniel Megert
> So I assume it is Jenkins who died now with OOM, and because we now have compiler regression tests with lot of output.

Was this merged after the last good build?

Dani



From:        "Andrey Loskutov" <[hidden email]>
To:        [hidden email]
Date:        14.05.2020 14:36
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        [hidden email]




I see that the size of the all result data nearly doubled from build 71 to 72.
 
In build 71 results from org.eclipse.jdt.core.tests.compiler.regression.TestAll.xml are empty, in following builds it is about 11 MB.
 
 
https://ci-staging.eclipse.org/releng/view/Automatedtests/job/ep416I-unit-cen64-gtk3-java14/71/artifact/workarea/I20200511-1800/eclipse-testing/results/ep416I-unit-cen64-gtk3-java14_linux.gtk.x86_64_14/
https://ci-staging.eclipse.org/releng/view/Automatedtests/job/ep416I-unit-cen64-gtk3-java14/72/artifact/workarea/I20200512-1800/eclipse-testing/results/ep416I-unit-cen64-gtk3-java14_linux.gtk.x86_64_14/
 
So I assume it is Jenkins who died now with OOM, and because we now have compiler regression tests with lot of output.
 
Before build 72, compiler tests *died* with this stack trace:
 
DumpStackTracesTimer almost reached timeout '7200000'.
totalMemory:            1037959168
freeMemory (before GC): 806520888
freeMemory (after GC):  811775832
Thread dump 0 at 2020-05-12 07:58:42 +0000:
java.lang.Exception: ThreadDump for thread "main"
   at java.base@14/sun.nio.ch.Net.accept(Native Method)
   at java.base@14/sun.nio.ch.NioSocketImpl.accept(NioSocketImpl.java:755)
   at java.base@14/java.net.ServerSocket.implAccept(ServerSocket.java:684)
   at java.base@14/java.net.ServerSocket.platformImplAccept(ServerSocket.java:650)
   at java.base@14/java.net.ServerSocket.implAccept(ServerSocket.java:626)
   at java.base@14/java.net.ServerSocket.implAccept(ServerSocket.java:583)
   at java.base@14/java.net.ServerSocket.accept(ServerSocket.java:540)
   at org.eclipse.jdt.core.tests.util.TestVerifier.launchVerifyTestsIfNeeded(TestVerifier.java:547)
   at org.eclipse.jdt.core.tests.util.TestVerifier.verifyClassFiles(TestVerifier.java:635)
   at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runTest(AbstractRegressionTest.java:3457)
   at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runTest(AbstractRegressionTest.java:3127)
   at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runConformTest(AbstractRegressionTest.java:1851)
   at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runConformTest(AbstractRegressionTest.java:1848)
   at org.eclipse.jdt.core.tests.compiler.regression.ConditionalExpressionTest.test001(ConditionalExpressionTest.java:47)
   at java.base@14/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at java.base@14/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
   at java.base@14/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

 
So I would increase agent heap and may be re-trigger results parsing if possible? We *have* test results.
 
Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov
 
 
Gesendet: Donnerstag, 14. Mai 2020 um 14:07 Uhr
Von:
"Sravan K Lakkimsetti" <[hidden email]>
An:
"Eclipse platform release engineering list." <[hidden email]>
Betreff:
Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

Here are the junit test results and logs https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/artifact/
Hope this helps
 
-Sravan
 
From: Andrey Loskutov <[hidden email]>
Sent:
14 May 2020 17:27
To:
[hidden email]
Subject:
[EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 
Are we sure we have OOM on the SDK side, not in on the Jenkins agent side? I can't understand the stack below.
 
If I read the stack right, the agent dies trying to *transfer* JUnit test results?
But test aren't executed not in the same JVM where Jenkins agent lives?
Can we access generated JUnit results/logs?May be they are just *huge* for whatever reason?
May be we see after which test it misbehaves (*if* this happens during test phase and not some Jenkins issue).
Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.128.4.1/10.128.4.1:33780
               at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788)
               at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
               at hudson.remoting.Channel.call(Channel.java:998)
               at hudson.FilePath.act(FilePath.java:1069)
               at hudson.FilePath.act(FilePath.java:1058)
               at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114)
               at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137)
               at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167)
               at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:52)
               at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:25)
               at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
               at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$$Lambda$446/0000000030151E30.run(Unknown Source)
               at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
               at java.util.concurrent.FutureTask.run(Unknown Source)
               at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
               at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
java.lang.OutOfMemoryError: Java heap space
        at java.util.Arrays.copyOf(Unknown Source)
        at java.io.ByteArrayOutputStream.toByteArray(Unknown Source)
        at hudson.remoting.UserRequest._serialize(UserRequest.java:264)
        at hudson.remoting.UserRequest.serialize(UserRequest.java:272)
        at hudson.remoting.UserRequest.perform(UserRequest.java:222)
        at hudson.remoting.UserRequest.perform(UserRequest.java:54)
        at hudson.remoting.Request$2.run(Request.java:369)
        at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:117)
        at hudson.remoting.Engine$1$$Lambda$4/000000003C01FDE0.run(Unknown Source)
Caused: java.io.IOException: Remote call on JNLP4-connect connection from 10.128.4.1/10.128.4.1:33780 failed
        at hudson.remoting.Channel.call(Channel.java:1004)
        at hudson.FilePath.act(FilePath.java:1069)
        at hudson.FilePath.act(FilePath.java:1058)
        at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114)
        at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137)
        at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167)
        at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:52)
        at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:25)
        at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
        at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$$Lambda$446/0000000030151E30.run(Unknown Source)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Finished: FAILURE
Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov
 
 
Gesendet: Donnerstag, 14. Mai 2020 um 13:26 Uhr
Von:
"Sravan K Lakkimsetti" <
sravankumarl@...>
An:
"Eclipse platform release engineering list." <
[hidden email]>
Betreff:
Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

Ok Dani I am running the tests from I20200511-1800. Last time it took more than 8 hours so it may be a while before we get results.
 
Thanks
Sravan
 
From: Daniel Megert <daniel_megert@...>
Sent:
14 May 2020 16:51
To:
Eclipse platform release engineering list. <
[hidden email]>
Subject:
[EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 
Hi Sravan

Yes, I know that. The questions is: does rerunning the tests from the last good build work or not. If yes, we have to investigate why it now uses more memory. Is there a way to check how much is used?


Dani




From:        
"Sravan K Lakkimsetti" <sravankumarl@...>
To:        
"Eclipse platform release engineering list." <[hidden email]>
Date:        
14.05.2020 13:15
Subject:        
[EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        
[hidden email]

 

Hi Dani,

 

This started with Build: I20200512-1800. We didn’t have this problem before that

 

-Sravan

 

From:Daniel Megert <daniel_megert@...>
Sent:
14 May 2020 16:38
To:
Eclipse platform release engineering list. <
[hidden email]>
Subject:
[EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Did you check whether the OOME also happens with the last good build? If not, please do so.

Dani




From:        
"Sravan K Lakkimsetti" <sravankumarl@...>
To:        
"Eclipse platform release engineering list." <[hidden email]>
Date:        
14.05.2020 12:39
Subject:        
[EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        
[hidden email]


 

Hi,

 

Java 14 configuration failed with “java.lang.OutOfMemoryError: Java heap space“

Log: https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/console

Max memory allocated for the container is 2GB. I believe this should be sufficient. I can go till 4GB if required

 

Is this related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=553538?

 

Thanks

Sravan

 

From:[hidden email] <genie.releng@...>
Sent:
14 May 2020 05:57
To:
[hidden email]
Subject:
[EXTERNAL] [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Eclipse downloads:
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800

Build logs and/or test results (eventually):

https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800/testResults.php

Software site repository:

https://download.eclipse.org/eclipse/updates/4.16-I-builds

Specific (simple) site repository:

https://download.eclipse.org/eclipse/updates/4.16-I-builds/I20200513-1800

Equinox downloads:

https://download.eclipse.org/equinox/drops/I20200513-1800

_______________________________________________

platform-releng-dev mailing list


[hidden email]

To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 


_______________________________________________
platform-releng-dev mailing list

[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev


_______________________________________________
platform-releng-dev mailing list

[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev



_______________________________________________ platform-releng-dev mailing list
[hidden email]To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
 

_______________________________________________ platform-releng-dev mailing list [hidden email] To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev




_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
Reply | Threaded
Open this post in threaded view
|

Re: 4.16 I-Build: I20200513-1800

Andrey Loskutov
Dani,
 
not sure what do you mean with "this".
 
Build 71 was last "good" one (I20200511-1800 with results), but only because the compiler regression tests timed out with an error and so the test results xml was not generated properly and so Jenkins was happy to parse empty xml file.
 
After that we see no timeout / crash in build 72 and later, but that increased the xml size (11 MB) and now it looks like Jenkins crashes with OOM trying to parse or transfer them (just because there are lot of compiler regression tests).
 
Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov
 
 
Gesendet: Donnerstag, 14. Mai 2020 um 14:44 Uhr
Von: "Daniel Megert" <[hidden email]>
An: "Eclipse platform release engineering list." <[hidden email]>
Betreff: Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
> So I assume it is Jenkins who died now with OOM, and because we now have compiler regression tests with lot of output.

Was this merged after the last good build?

Dani



From:        "Andrey Loskutov" <[hidden email]>
To:        [hidden email]
Date:        14.05.2020 14:36
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        [hidden email]



I see that the size of the all result data nearly doubled from build 71 to 72.
 
In build 71 results from org.eclipse.jdt.core.tests.compiler.regression.TestAll.xml are empty, in following builds it is about 11 MB.
 
 
https://ci-staging.eclipse.org/releng/view/Automatedtests/job/ep416I-unit-cen64-gtk3-java14/71/artifact/workarea/I20200511-1800/eclipse-testing/results/ep416I-unit-cen64-gtk3-java14_linux.gtk.x86_64_14/
https://ci-staging.eclipse.org/releng/view/Automatedtests/job/ep416I-unit-cen64-gtk3-java14/72/artifact/workarea/I20200512-1800/eclipse-testing/results/ep416I-unit-cen64-gtk3-java14_linux.gtk.x86_64_14/
 
So I assume it is Jenkins who died now with OOM, and because we now have compiler regression tests with lot of output.
 
Before build 72, compiler tests *died* with this stack trace:
 
DumpStackTracesTimer almost reached timeout '7200000'.
totalMemory:            1037959168
freeMemory (before GC): 806520888
freeMemory (after GC):  811775832
Thread dump 0 at 2020-05-12 07:58:42 +0000:
java.lang.Exception: ThreadDump for thread "main"
   at java.base@14/sun.nio.ch.Net.accept(Native Method)
   at java.base@14/sun.nio.ch.NioSocketImpl.accept(NioSocketImpl.java:755)
   at java.base@14/java.net.ServerSocket.implAccept(ServerSocket.java:684)
   at java.base@14/java.net.ServerSocket.platformImplAccept(ServerSocket.java:650)
   at java.base@14/java.net.ServerSocket.implAccept(ServerSocket.java:626)
   at java.base@14/java.net.ServerSocket.implAccept(ServerSocket.java:583)
   at java.base@14/java.net.ServerSocket.accept(ServerSocket.java:540)
   at org.eclipse.jdt.core.tests.util.TestVerifier.launchVerifyTestsIfNeeded(TestVerifier.java:547)
   at org.eclipse.jdt.core.tests.util.TestVerifier.verifyClassFiles(TestVerifier.java:635)
   at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runTest(AbstractRegressionTest.java:3457)
   at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runTest(AbstractRegressionTest.java:3127)
   at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runConformTest(AbstractRegressionTest.java:1851)
   at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runConformTest(AbstractRegressionTest.java:1848)
   at org.eclipse.jdt.core.tests.compiler.regression.ConditionalExpressionTest.test001(ConditionalExpressionTest.java:47)
   at java.base@14/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at java.base@14/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
   at java.base@14/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

 
So I would increase agent heap and may be re-trigger results parsing if possible? We *have* test results.
 
Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих


https://www.eclipse.org/user/aloskutov
 
 
Gesendet: Donnerstag, 14. Mai 2020 um 14:07 Uhr
Von: "Sravan K Lakkimsetti" <[hidden email]>
An: "Eclipse platform release engineering list." <[hidden email]>
Betreff: Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

Here are the junit test results and logs https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/artifact/
Hope this helps
 
-Sravan
 
From: Andrey Loskutov <[hidden email]>
Sent: 14 May 2020 17:27
To: [hidden email]
Subject: [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 
Are we sure we have OOM on the SDK side, not in on the Jenkins agent side? I can't understand the stack below.
 
If I read the stack right, the agent dies trying to *transfer* JUnit test results?
But test aren't executed not in the same JVM where Jenkins agent lives?
Can we access generated JUnit results/logs?May be they are just *huge* for whatever reason?
May be we see after which test it misbehaves (*if* this happens during test phase and not some Jenkins issue).
Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.128.4.1/10.128.4.1:33780
               at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788)
               at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
               at hudson.remoting.Channel.call(Channel.java:998)
               at hudson.FilePath.act(FilePath.java:1069)
               at hudson.FilePath.act(FilePath.java:1058)
               at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114)
               at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137)
               at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167)
               at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:52)
               at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:25)
               at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
               at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$$Lambda$446/0000000030151E30.run(Unknown Source)
               at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
               at java.util.concurrent.FutureTask.run(Unknown Source)
               at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
               at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
java.lang.OutOfMemoryError: Java heap space
        at java.util.Arrays.copyOf(Unknown Source)
        at java.io.ByteArrayOutputStream.toByteArray(Unknown Source)
        at hudson.remoting.UserRequest._serialize(UserRequest.java:264)
        at hudson.remoting.UserRequest.serialize(UserRequest.java:272)
        at hudson.remoting.UserRequest.perform(UserRequest.java:222)
        at hudson.remoting.UserRequest.perform(UserRequest.java:54)
        at hudson.remoting.Request$2.run(Request.java:369)
        at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:117)
        at hudson.remoting.Engine$1$$Lambda$4/000000003C01FDE0.run(Unknown Source)
Caused: java.io.IOException: Remote call on JNLP4-connect connection from 10.128.4.1/10.128.4.1:33780 failed
        at hudson.remoting.Channel.call(Channel.java:1004)
        at hudson.FilePath.act(FilePath.java:1069)
        at hudson.FilePath.act(FilePath.java:1058)
        at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114)
        at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137)
        at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167)
        at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:52)
        at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:25)
        at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
        at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$$Lambda$446/0000000030151E30.run(Unknown Source)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Finished: FAILURE
Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих


https://www.eclipse.org/user/aloskutov
 
 
Gesendet: Donnerstag, 14. Mai 2020 um 13:26 Uhr
Von: "Sravan K Lakkimsetti" <
[hidden email]>
An: "Eclipse platform release engineering list." <
[hidden email]>
Betreff: Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

Ok Dani I am running the tests from I20200511-1800. Last time it took more than 8 hours so it may be a while before we get results.
 
Thanks
Sravan
 
From: Daniel Megert <[hidden email]>
Sent: 14 May 2020 16:51
To: Eclipse platform release engineering list. <
[hidden email]>
Subject: [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 
Hi Sravan

Yes, I know that. The questions is: does rerunning the tests from the last good build work or not. If yes, we have to investigate why it now uses more memory. Is there a way to check how much is used?

Dani



From:        "Sravan K Lakkimsetti" <[hidden email]>
To:        "Eclipse platform release engineering list." <[hidden email]>
Date:        14.05.2020 13:15
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        [hidden email]

 

Hi Dani,

 

This started with Build: I20200512-1800. We didn’t have this problem before that

 

-Sravan

 

From:Daniel Megert <[hidden email]>
Sent: 14 May 2020 16:38
To: Eclipse platform release engineering list. <
[hidden email]>
Subject: [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Did you check whether the OOME also happens with the last good build? If not, please do so.

Dani



From:        "Sravan K Lakkimsetti" <[hidden email]>
To:        "Eclipse platform release engineering list." <[hidden email]>
Date:        14.05.2020 12:39
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        [hidden email]


 

Hi,

 

Java 14 configuration failed with “java.lang.OutOfMemoryError: Java heap space“

Log: https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/console

Max memory allocated for the container is 2GB. I believe this should be sufficient. I can go till 4GB if required

 

Is this related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=553538?

 

Thanks

Sravan

 

From:[hidden email] <[hidden email]>
Sent: 14 May 2020 05:57
To:
[hidden email]
Subject: [EXTERNAL] [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Eclipse downloads:
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800

Build logs and/or test results (eventually):
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800/testResults.php

Software site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds

Specific (simple) site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds/I20200513-1800

Equinox downloads:
https://download.eclipse.org/equinox/drops/I20200513-1800

_______________________________________________

platform-releng-dev mailing list


[hidden email]

To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 


_______________________________________________
platform-releng-dev mailing list

[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev


_______________________________________________
platform-releng-dev mailing list

[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
 



_______________________________________________ platform-releng-dev mailing list [hidden email]To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
 

_______________________________________________ platform-releng-dev mailing list [hidden email] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev



_______________________________________________ platform-releng-dev mailing list [hidden email] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
Reply | Threaded
Open this post in threaded view
|

Re: 4.16 I-Build: I20200513-1800

Daniel Megert
Hi Andrey

I meant the code that generates more data.

Dani



From:        "Andrey Loskutov" <[hidden email]>
To:        [hidden email]
Date:        14.05.2020 14:58
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        [hidden email]




Dani,
 
not sure what do you mean with "this".
 
Build 71 was last "good" one (I20200511-1800 with results), but only because the compiler regression tests timed out with an error and so the test results xml was not generated properly and so Jenkins was happy to parse empty xml file.
 
After that we see no timeout / crash in build 72 and later, but that increased the xml size (11 MB) and now it looks like Jenkins crashes with OOM trying to parse or transfer them (just because there are lot of compiler regression tests).

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov
 
 
Gesendet: Donnerstag, 14. Mai 2020 um 14:44 Uhr
Von:
"Daniel Megert" <[hidden email]>
An:
"Eclipse platform release engineering list." <[hidden email]>
Betreff:
Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

> So I assume it is Jenkins who died now with OOM, and because we now have compiler regression tests with lot of output.

Was this merged after the last good build?


Dani




From:        
"Andrey Loskutov" <[hidden email]>
To:        
[hidden email]
Date:        
14.05.2020 14:36
Subject:        
[EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        
[hidden email]



I see that the size of the all result data nearly doubled from build 71 to 72.

In build 71 results from org.eclipse.jdt.core.tests.compiler.regression.TestAll.xml are empty, in following builds it is about 11 MB.


https://ci-staging.eclipse.org/releng/view/Automatedtests/job/ep416I-unit-cen64-gtk3-java14/71/artifact/workarea/I20200511-1800/eclipse-testing/results/ep416I-unit-cen64-gtk3-java14_linux.gtk.x86_64_14/
https://ci-staging.eclipse.org/releng/view/Automatedtests/job/ep416I-unit-cen64-gtk3-java14/72/artifact/workarea/I20200512-1800/eclipse-testing/results/ep416I-unit-cen64-gtk3-java14_linux.gtk.x86_64_14/

So I assume it is Jenkins who died now with OOM, and because we now have compiler regression tests with lot of output.

Before build 72, compiler tests *died* with this stack trace:

DumpStackTracesTimer almost reached timeout '7200000'.
totalMemory:            1037959168
freeMemory (before GC): 806520888
freeMemory (after GC):  811775832
Thread dump 0 at 2020-05-12 07:58:42 +0000:
java.lang.Exception: ThreadDump for thread "main"
  at java.base@14/sun.nio.ch.Net.accept(Native Method)
  at java.base@14/sun.nio.ch.NioSocketImpl.accept(NioSocketImpl.java:755)
  at java.base@14/java.net.ServerSocket.implAccept(ServerSocket.java:684)
  at java.base@14/java.net.ServerSocket.platformImplAccept(ServerSocket.java:650)
  at java.base@14/java.net.ServerSocket.implAccept(ServerSocket.java:626)
  at java.base@14/java.net.ServerSocket.implAccept(ServerSocket.java:583)
  at java.base@14/java.net.ServerSocket.accept(ServerSocket.java:540)
  at org.eclipse.jdt.core.tests.util.TestVerifier.launchVerifyTestsIfNeeded(TestVerifier.java:547)
  at org.eclipse.jdt.core.tests.util.TestVerifier.verifyClassFiles(TestVerifier.java:635)
  at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runTest(AbstractRegressionTest.java:3457)
  at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runTest(AbstractRegressionTest.java:3127)
  at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runConformTest(AbstractRegressionTest.java:1851)
  at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runConformTest(AbstractRegressionTest.java:1848)
  at org.eclipse.jdt.core.tests.compiler.regression.ConditionalExpressionTest.test001(ConditionalExpressionTest.java:47)
  at java.base@14/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at java.base@14/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
  at java.base@14/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

So I would increase agent heap and may be re-trigger results parsing if possible? We *have* test results.

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov
 
 
Gesendet:
Donnerstag, 14. Mai 2020 um 14:07 Uhr
Von:
"Sravan K Lakkimsetti" <[hidden email]>
An:
"Eclipse platform release engineering list." <[hidden email]>
Betreff:
Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Here are the junit test results and logs
https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/artifact/
Hope this helps

-Sravan

From:
Andrey Loskutov <[hidden email]>
Sent:
14 May 2020 17:27
To:
[hidden email]
Subject:
[EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

Are we sure we have OOM on the SDK side, not in on the Jenkins agent side? I can't understand the stack below.

If I read the stack right, the agent dies trying to *transfer* JUnit test results?
But test aren't executed not in the same JVM where Jenkins agent lives?
Can we access generated JUnit results/logs?May be they are just *huge* for whatever reason?
May be we see after which test it misbehaves (*if* this happens during test phase and not some Jenkins issue).
Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.128.4.1/10.128.4.1:33780
              at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788)
              at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
              at hudson.remoting.Channel.call(Channel.java:998)
              at hudson.FilePath.act(FilePath.java:1069)
              at hudson.FilePath.act(FilePath.java:1058)
              at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114)
              at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137)
              at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167)
              at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:52)
              at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:25)
              at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
              at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$$Lambda$446/0000000030151E30.run(Unknown Source)
              at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
              at java.util.concurrent.FutureTask.run(Unknown Source)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
java.lang.OutOfMemoryError: Java heap space
       at java.util.Arrays.copyOf(Unknown Source)
       at java.io.ByteArrayOutputStream.toByteArray(Unknown Source)
       at hudson.remoting.UserRequest._serialize(UserRequest.java:264)
       at hudson.remoting.UserRequest.serialize(UserRequest.java:272)
       at hudson.remoting.UserRequest.perform(UserRequest.java:222)
       at hudson.remoting.UserRequest.perform(UserRequest.java:54)
       at hudson.remoting.Request$2.run(Request.java:369)
       at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
       at java.util.concurrent.FutureTask.run(Unknown Source)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
       at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:117)
       at hudson.remoting.Engine$1$$Lambda$4/000000003C01FDE0.run(Unknown Source)
Caused: java.io.IOException: Remote call on JNLP4-connect connection from 10.128.4.1/10.128.4.1:33780 failed
       at hudson.remoting.Channel.call(Channel.java:1004)
       at hudson.FilePath.act(FilePath.java:1069)
       at hudson.FilePath.act(FilePath.java:1058)
       at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114)
       at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137)
       at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167)
       at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:52)
       at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:25)
       at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
       at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$$Lambda$446/0000000030151E30.run(Unknown Source)
       at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
       at java.util.concurrent.FutureTask.run(Unknown Source)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
       at java.lang.Thread.run(Unknown Source)
Finished: FAILURE
Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov
 
 
Gesendet:
Donnerstag, 14. Mai 2020 um 13:26 Uhr
Von:
"Sravan K Lakkimsetti" <
sravankumarl@...>
An:
"Eclipse platform release engineering list." <
[hidden email]>
Betreff:
Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Ok Dani I am running the tests from I20200511-1800. Last time it took more than 8 hours so it may be a while before we get results.

Thanks
Sravan

From:
Daniel Megert <
daniel_megert@...>
Sent:
14 May 2020 16:51
To:
Eclipse platform release engineering list. <
[hidden email]>
Subject:
[EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

Hi Sravan


Yes, I know that. The questions is: does rerunning the tests from the last good build work or not. If yes, we have to investigate why it now uses more memory. Is there a way to check how much is used?


Dani




From:        
"Sravan K Lakkimsetti" <sravankumarl@...>
To:        
"Eclipse platform release engineering list." <[hidden email]>
Date:        
14.05.2020 13:15
Subject:        
[EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        
[hidden email]


 

Hi Dani,

 

This started with Build: I20200512-1800. We didn’t have this problem before that

 

-Sravan

 

From:Daniel Megert <daniel_megert@...>
Sent:
14 May 2020 16:38
To:
Eclipse platform release engineering list. <
[hidden email]>
Subject:
[EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Did you check whether the OOME also happens with the last good build? If not, please do so.

Dani




From:        
"Sravan K Lakkimsetti" <sravankumarl@...>
To:        
"Eclipse platform release engineering list." <[hidden email]>
Date:        
14.05.2020 12:39
Subject:        
[EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        
[hidden email]



 

Hi,

 

Java 14 configuration failed with “java.lang.OutOfMemoryError: Java heap space“

Log: https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/console

Max memory allocated for the container is 2GB. I believe this should be sufficient. I can go till 4GB if required

 

Is this related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=553538?

 

Thanks

Sravan

 

From:[hidden email] <genie.releng@...>
Sent:
14 May 2020 05:57
To:
[hidden email]
Subject:
[EXTERNAL] [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Eclipse downloads:
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800

Build logs and/or test results (eventually):

https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800/testResults.php

Software site repository:

https://download.eclipse.org/eclipse/updates/4.16-I-builds

Specific (simple) site repository:

https://download.eclipse.org/eclipse/updates/4.16-I-builds/I20200513-1800

Equinox downloads:

https://download.eclipse.org/equinox/drops/I20200513-1800

_______________________________________________

platform-releng-dev mailing list


[hidden email]

To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 


_______________________________________________
platform-releng-dev mailing list

[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev



_______________________________________________
platform-releng-dev mailing list

[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev



_______________________________________________ platform-releng-dev mailing list
[hidden email]To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list

[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev


_______________________________________________ platform-releng-dev mailing list [hidden email] To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev



_______________________________________________ platform-releng-dev mailing list [hidden email] To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev




_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
Reply | Threaded
Open this post in threaded view
|

Re: 4.16 I-Build: I20200513-1800

Andrey Loskutov
OK,
 
but can we please just increase heap for Jenkins agent, because it obviously unable to keep up with the amount of test data our compiler tests generate on Java 14.
I assume this hits especially 14, because the test amount depends on the number of possible JLS specification to test against, and the most are on the highest JVM version.
 
Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov
 
 
Gesendet: Donnerstag, 14. Mai 2020 um 15:03 Uhr
Von: "Daniel Megert" <[hidden email]>
An: "Eclipse platform release engineering list." <[hidden email]>
Betreff: Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Hi Andrey

I meant the code that generates more data.

Dani



From:        "Andrey Loskutov" <[hidden email]>
To:        [hidden email]
Date:        14.05.2020 14:58
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        [hidden email]



Dani,
 
not sure what do you mean with "this".
 
Build 71 was last "good" one (I20200511-1800 with results), but only because the compiler regression tests timed out with an error and so the test results xml was not generated properly and so Jenkins was happy to parse empty xml file.
 
After that we see no timeout / crash in build 72 and later, but that increased the xml size (11 MB) and now it looks like Jenkins crashes with OOM trying to parse or transfer them (just because there are lot of compiler regression tests).

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих


https://www.eclipse.org/user/aloskutov
 
 
Gesendet: Donnerstag, 14. Mai 2020 um 14:44 Uhr
Von: "Daniel Megert" <[hidden email]>
An: "Eclipse platform release engineering list." <[hidden email]>
Betreff: Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

> So I assume it is Jenkins who died now with OOM, and because we now have compiler regression tests with lot of output.

Was this merged after the last good build?

Dani



From:        "Andrey Loskutov" <[hidden email]>
To:        [hidden email]
Date:        14.05.2020 14:36
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        [hidden email]



I see that the size of the all result data nearly doubled from build 71 to 72.

In build 71 results from org.eclipse.jdt.core.tests.compiler.regression.TestAll.xml are empty, in following builds it is about 11 MB.



https://ci-staging.eclipse.org/releng/view/Automatedtests/job/ep416I-unit-cen64-gtk3-java14/71/artifact/workarea/I20200511-1800/eclipse-testing/results/ep416I-unit-cen64-gtk3-java14_linux.gtk.x86_64_14/
https://ci-staging.eclipse.org/releng/view/Automatedtests/job/ep416I-unit-cen64-gtk3-java14/72/artifact/workarea/I20200512-1800/eclipse-testing/results/ep416I-unit-cen64-gtk3-java14_linux.gtk.x86_64_14/

So I assume it is Jenkins who died now with OOM, and because we now have compiler regression tests with lot of output.

Before build 72, compiler tests *died* with this stack trace:

DumpStackTracesTimer almost reached timeout '7200000'.
totalMemory:            1037959168
freeMemory (before GC): 806520888
freeMemory (after GC):  811775832
Thread dump 0 at 2020-05-12 07:58:42 +0000:
java.lang.Exception: ThreadDump for thread "main"
  at java.base@14/sun.nio.ch.Net.accept(Native Method)
  at java.base@14/sun.nio.ch.NioSocketImpl.accept(NioSocketImpl.java:755)
  at java.base@14/java.net.ServerSocket.implAccept(ServerSocket.java:684)
  at java.base@14/java.net.ServerSocket.platformImplAccept(ServerSocket.java:650)
  at java.base@14/java.net.ServerSocket.implAccept(ServerSocket.java:626)
  at java.base@14/java.net.ServerSocket.implAccept(ServerSocket.java:583)
  at java.base@14/java.net.ServerSocket.accept(ServerSocket.java:540)
  at org.eclipse.jdt.core.tests.util.TestVerifier.launchVerifyTestsIfNeeded(TestVerifier.java:547)
  at org.eclipse.jdt.core.tests.util.TestVerifier.verifyClassFiles(TestVerifier.java:635)
  at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runTest(AbstractRegressionTest.java:3457)
  at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runTest(AbstractRegressionTest.java:3127)
  at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runConformTest(AbstractRegressionTest.java:1851)
  at org.eclipse.jdt.core.tests.compiler.regression.AbstractRegressionTest.runConformTest(AbstractRegressionTest.java:1848)
  at org.eclipse.jdt.core.tests.compiler.regression.ConditionalExpressionTest.test001(ConditionalExpressionTest.java:47)
  at java.base@14/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at java.base@14/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
  at java.base@14/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

So I would increase agent heap and may be re-trigger results parsing if possible? We *have* test results.

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих


https://www.eclipse.org/user/aloskutov
 
 
Gesendet: Donnerstag, 14. Mai 2020 um 14:07 Uhr
Von: "Sravan K Lakkimsetti" <[hidden email]>
An: "Eclipse platform release engineering list." <[hidden email]>
Betreff: Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Here are the junit test results and logs
https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/artifact/
Hope this helps

-Sravan

From: Andrey Loskutov <[hidden email]>
Sent: 14 May 2020 17:27
To: [hidden email]
Subject: [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

Are we sure we have OOM on the SDK side, not in on the Jenkins agent side? I can't understand the stack below.

If I read the stack right, the agent dies trying to *transfer* JUnit test results?
But test aren't executed not in the same JVM where Jenkins agent lives?
Can we access generated JUnit results/logs?May be they are just *huge* for whatever reason?
May be we see after which test it misbehaves (*if* this happens during test phase and not some Jenkins issue).
Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.128.4.1/10.128.4.1:33780
              at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788)
              at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
              at hudson.remoting.Channel.call(Channel.java:998)
              at hudson.FilePath.act(FilePath.java:1069)
              at hudson.FilePath.act(FilePath.java:1058)
              at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114)
              at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137)
              at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167)
              at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:52)
              at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:25)
              at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
              at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$$Lambda$446/0000000030151E30.run(Unknown Source)
              at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
              at java.util.concurrent.FutureTask.run(Unknown Source)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
java.lang.OutOfMemoryError: Java heap space
       at java.util.Arrays.copyOf(Unknown Source)
       at java.io.ByteArrayOutputStream.toByteArray(Unknown Source)
       at hudson.remoting.UserRequest._serialize(UserRequest.java:264)
       at hudson.remoting.UserRequest.serialize(UserRequest.java:272)
       at hudson.remoting.UserRequest.perform(UserRequest.java:222)
       at hudson.remoting.UserRequest.perform(UserRequest.java:54)
       at hudson.remoting.Request$2.run(Request.java:369)
       at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
       at java.util.concurrent.FutureTask.run(Unknown Source)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
       at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:117)
       at hudson.remoting.Engine$1$$Lambda$4/000000003C01FDE0.run(Unknown Source)
Caused: java.io.IOException: Remote call on JNLP4-connect connection from 10.128.4.1/10.128.4.1:33780 failed
       at hudson.remoting.Channel.call(Channel.java:1004)
       at hudson.FilePath.act(FilePath.java:1069)
       at hudson.FilePath.act(FilePath.java:1058)
       at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114)
       at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137)
       at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167)
       at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:52)
       at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:25)
       at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
       at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$$Lambda$446/0000000030151E30.run(Unknown Source)
       at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
       at java.util.concurrent.FutureTask.run(Unknown Source)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
       at java.lang.Thread.run(Unknown Source)
Finished: FAILURE
Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих


https://www.eclipse.org/user/aloskutov
 
 
Gesendet: Donnerstag, 14. Mai 2020 um 13:26 Uhr
Von: "Sravan K Lakkimsetti" <
[hidden email]>
An: "Eclipse platform release engineering list." <
[hidden email]>
Betreff: Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Ok Dani I am running the tests from I20200511-1800. Last time it took more than 8 hours so it may be a while before we get results.

Thanks
Sravan

From: Daniel Megert <
[hidden email]>
Sent: 14 May 2020 16:51
To: Eclipse platform release engineering list. <
[hidden email]>
Subject: [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800


Hi Sravan

Yes, I know that. The questions is: does rerunning the tests from the last good build work or not. If yes, we have to investigate why it now uses more memory. Is there a way to check how much is used?

Dani



From:        "Sravan K Lakkimsetti" <[hidden email]>
To:        "Eclipse platform release engineering list." <[hidden email]>
Date:        14.05.2020 13:15
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        [hidden email]


 

Hi Dani,

 

This started with Build: I20200512-1800. We didn’t have this problem before that

 

-Sravan

 

From:Daniel Megert <[hidden email]>
Sent: 14 May 2020 16:38
To: Eclipse platform release engineering list. <
[hidden email]>
Subject: [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Did you check whether the OOME also happens with the last good build? If not, please do so.

Dani



From:        "Sravan K Lakkimsetti" <[hidden email]>
To:        "Eclipse platform release engineering list." <[hidden email]>
Date:        14.05.2020 12:39
Subject:        [EXTERNAL] Re: [platform-releng-dev] 4.16 I-Build: I20200513-1800
Sent by:        [hidden email]



 

Hi,

 

Java 14 configuration failed with “java.lang.OutOfMemoryError: Java heap space“

Log: https://ci-staging.eclipse.org/releng/view/Automated%20tests/job/ep416I-unit-cen64-gtk3-java14/74/console

Max memory allocated for the container is 2GB. I believe this should be sufficient. I can go till 4GB if required

 

Is this related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=553538?

 

Thanks

Sravan

 

From:[hidden email] <[hidden email]>
Sent: 14 May 2020 05:57
To:
[hidden email]
Subject: [EXTERNAL] [platform-releng-dev] 4.16 I-Build: I20200513-1800

 

Eclipse downloads:
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800

Build logs and/or test results (eventually):
https://download.eclipse.org/eclipse/downloads/drops4/I20200513-1800/testResults.php

Software site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds

Specific (simple) site repository:
https://download.eclipse.org/eclipse/updates/4.16-I-builds/I20200513-1800

Equinox downloads:
https://download.eclipse.org/equinox/drops/I20200513-1800

_______________________________________________

platform-releng-dev mailing list


[hidden email]

To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

 


_______________________________________________
platform-releng-dev mailing list

[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev



_______________________________________________
platform-releng-dev mailing list

[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev



_______________________________________________ platform-releng-dev mailing list [hidden email]To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list

[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev


_______________________________________________ platform-releng-dev mailing list [hidden email] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev



_______________________________________________ platform-releng-dev mailing list [hidden email] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-releng-dev



_______________________________________________ platform-releng-dev mailing list [hidden email] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev

_______________________________________________
platform-releng-dev mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-releng-dev