New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

shippable: unstable execution of pitest for pitest-checkstyle-common profile #5022

Closed
romani opened this Issue Aug 29, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@romani
Member

romani commented Aug 29, 2017

Survived items:target/pit-reports/201708290005/com.puppycrawl.tools.checkstyle/XMLLogger.java.html:<td class='survived'> target/pit-reports/201708290005/com.puppycrawl.tools.checkstyle/XMLLogger.java.html:<td class='covered'><pre><span class='survived'> fileMessages.clear();</span></pre></td></tr>
Survived items found in reports, build will be failed

https://app.shippable.com/github/checkstyle/checkstyle/runs/4762/19/console
Please also rebase all your further PRs to avoid such issue again.

Update:
log from build , looks like unrelated to current fix

12:07:08 AM PIT >> INFO : Created  19 mutation test units
12:08:41 AM PIT >> WARNING : Minion exited abnormally due to TIMED_OUT
12:11:31 AM PIT >> WARNING : Minion exited abnormally due to TIMED_OUT
12:11:31 AM PIT >> WARNING : Minion exited abnormally due to TIMED_OUT
12:11:31 AM PIT >> WARNING : Minion exited abnormally due to TIMED_OUT
12:11:35 AM PIT >> WARNING : Minion exited abnormally due to TIMED_OUT
12:15:36 AM PIT >> WARNING : Minion exited abnormally due to TIMED_OUT
12:16:33 AM PIT >> WARNING : Minion exited abnormally due to TIMED_OUT
stderr  : Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000de900000, 165150720, 0) failed; error='Cannot allocate memory' (errno=12)
stderr  : Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000f3180000, 58720256, 0) failed; error='Cannot allocate memory' (errno=12)
12:17:27 AM PIT >> WARNING : Error while watching child process
java.util.concurrent.ExecutionException: org.pitest.util.PitError: null

Please copy and paste the information and the complete stacktrace below when reporting an issue
VM : Java HotSpot(TM) 64-Bit Server VM
Vendor : Oracle Corporation
Version : 25.72-b15
Uptime : 752776
Input -> 
 1 : -Dclassworlds.conf=/usr/local/apache-maven-3.2.5/bin/m2.conf
 2 : -Dmaven.home=/usr/local/apache-maven-3.2.5
BootClassPathSupported : true

	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(FutureTask.java:192)
	at org.pitest.util.CommunicationThread.waitToFinish(CommunicationThread.java:60)
	at org.pitest.mutationtest.execute.MutationTestProcess.waitToDie(MutationTestProcess.java:47)
	at org.pitest.mutationtest.build.MutationTestUnit.waitForMinionToDie(MutationTestUnit.java:92)
	at org.pitest.mutationtest.build.MutationTestUnit.runTestInSeperateProcessForMutationRange(MutationTestUnit.java:85)
	at org.pitest.mutationtest.build.MutationTestUnit.runTestsInSeperateProcess(MutationTestUnit.java:68)
	at org.pitest.mutationtest.build.MutationTestUnit.call(MutationTestUnit.java:55)
	at org.pitest.mutationtest.build.MutationTestUnit.call(MutationTestUnit.java:30)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: org.pitest.util.PitError: null

Please copy and paste the information and the complete stacktrace below when reporting an issue
VM : Java HotSpot(TM) 64-Bit Server VM
Vendor : Oracle Corporation
Version : 25.72-b15
Uptime : 752776
Input -> 
 1 : -Dclassworlds.conf=/usr/local/apache-maven-3.2.5/bin/m2.conf
 2 : -Dmaven.home=/usr/local/apache-maven-3.2.5
BootClassPathSupported : true

	at org.pitest.util.Unchecked.translateCheckedException(Unchecked.java:20)
	at org.pitest.util.SafeDataInputStream.readByte(SafeDataInputStream.java:65)
	at org.pitest.util.SocketReadingCallable.receiveResults(SocketReadingCallable.java:65)
	at org.pitest.util.SocketReadingCallable.call(SocketReadingCallable.java:37)
	at org.pitest.util.SocketReadingCallable.call(SocketReadingCallable.java:12)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	... 1 more
Caused by: java.io.EOFException
	at java.io.DataInputStream.readByte(DataInputStream.java:267)
	at org.pitest.util.SafeDataInputStream.readByte(SafeDataInputStream.java:63)
	... 5 more
12:17:27 AM PIT >> WARNING : Error while watching child process
java.util.concurrent.ExecutionException: org.pitest.util.PitError: null

Please copy and paste the information and the complete stacktrace below when reporting an issue
VM : Java HotSpot(TM) 64-Bit Server VM
Vendor : Oracle Corporation
Version : 25.72-b15
Uptime : 752776
Input -> 
 1 : -Dclassworlds.conf=/usr/local/apache-maven-3.2.5/bin/m2.conf
 2 : -Dmaven.home=/usr/local/apache-maven-3.2.5
BootClassPathSupported : true

	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(FutureTask.java:192)
	at org.pitest.util.CommunicationThread.waitToFinish(CommunicationThread.java:60)
	at org.pitest.mutationtest.execute.MutationTestProcess.waitToDie(MutationTestProcess.java:47)
	at org.pitest.mutationtest.build.MutationTestUnit.waitForMinionToDie(MutationTestUnit.java:92)
	at org.pitest.mutationtest.build.MutationTestUnit.runTestInSeperateProcessForMutationRange(MutationTestUnit.java:85)
	at org.pitest.mutationtest.build.MutationTestUnit.runTestsInSeperateProcess(MutationTestUnit.java:68)
	at org.pitest.mutationtest.build.MutationTestUnit.call(MutationTestUnit.java:55)
	at org.pitest.mutationtest.build.MutationTestUnit.call(MutationTestUnit.java:30)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: org.pitest.util.PitError: null

Please copy and paste the information and the complete stacktrace below when reporting an issue
VM : Java HotSpot(TM) 64-Bit Server VM
Vendor : Oracle Corporation
Version : 25.72-b15
Uptime : 752776
Input -> 
 1 : -Dclassworlds.conf=/usr/local/apache-maven-3.2.5/bin/m2.conf
 2 : -Dmaven.home=/usr/local/apache-maven-3.2.5
BootClassPathSupported : true

	at org.pitest.util.Unchecked.translateCheckedException(Unchecked.java:20)
	at org.pitest.util.SafeDataInputStream.readByte(SafeDataInputStream.java:65)
	at org.pitest.util.SocketReadingCallable.receiveResults(SocketReadingCallable.java:65)
	at org.pitest.util.SocketReadingCallable.call(SocketReadingCallable.java:37)
	at org.pitest.util.SocketReadingCallable.call(SocketReadingCallable.java:12)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	... 1 more
Caused by: java.io.EOFException
	at java.io.DataInputStream.readByte(DataInputStream.java:267)
	at org.pitest.util.SafeDataInputStream.readByte(SafeDataInputStream.java:63)
	... 5 more
12:17:27 AM PIT >> WARNING : Minion exited abnormally due to RUN_ERROR
12:17:27 AM PIT >> WARNING : Minion exited abnormally due to RUN_ERROR
12:17:55 AM PIT >> WARNING : Minion exited abnormally due to TIMED_OUT
12:18:13 AM PIT >> WARNING : Minion exited abnormally due to MEMORY_ERROR
12:19:35 AM PIT >> WARNING : Minion exited abnormally due to MEMORY_ERROR
12:21:01 AM PIT >> WARNING : Minion exited abnormally due to MEMORY_ERROR
12:21:02 AM PIT >> INFO : Completed in 928 seconds

I can not reproduce this crash on local, pitest validation works fine.
shippable is relaunched.

romani added a commit that referenced this issue Aug 29, 2017

romani added a commit that referenced this issue Aug 30, 2017

soon added a commit to soon/checkstyle that referenced this issue Aug 30, 2017

soon added a commit to soon/checkstyle that referenced this issue Aug 30, 2017

soon added a commit to soon/checkstyle that referenced this issue Aug 30, 2017

soon added a commit to soon/checkstyle that referenced this issue Aug 30, 2017

soon added a commit to soon/checkstyle that referenced this issue Aug 30, 2017

soon added a commit to soon/checkstyle that referenced this issue Aug 30, 2017

soon added a commit to soon/checkstyle that referenced this issue Aug 30, 2017

soon added a commit to soon/checkstyle that referenced this issue Aug 30, 2017

soon added a commit to soon/checkstyle that referenced this issue Aug 30, 2017

soon added a commit to soon/checkstyle that referenced this issue Aug 30, 2017

soon added a commit to soon/checkstyle that referenced this issue Aug 30, 2017

soon added a commit to soon/checkstyle that referenced this issue Aug 30, 2017

soon added a commit to soon/checkstyle that referenced this issue Aug 30, 2017

soon added a commit to soon/checkstyle that referenced this issue Aug 30, 2017

soon added a commit to soon/checkstyle that referenced this issue Aug 30, 2017

soon added a commit to soon/checkstyle that referenced this issue Aug 30, 2017

romani added a commit that referenced this issue Aug 30, 2017

@romani

This comment has been minimized.

Show comment
Hide comment
@romani

romani Aug 30, 2017

Member

investigation issue - #5024

I created an issue on pitest for clarification - hcoles/pitest#390

Member

romani commented Aug 30, 2017

investigation issue - #5024

I created an issue on pitest for clarification - hcoles/pitest#390

@romani romani closed this Aug 30, 2017

@romani romani added this to the 8.2 milestone Aug 30, 2017

timurt added a commit to timurt/checkstyle that referenced this issue Dec 19, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment