540044 – Potential issue with concurrent builds

Bug 540044 - Potential issue with concurrent builds

Summary: Potential issue with concurrent builds

Status:	VERIFIED DUPLICATE of bug 539139

Alias:	None

Product:	JDT
Classification:	Eclipse Project
Component:	Core (show other bugs)
Version:	4.5
Hardware:	All All

Importance:	P3 normal (vote)
Target Milestone:	4.10 M1
Assignee:	JDT-Core-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:	531554
	Show dependency tree

Reported:	2018-10-11 07:43 EDT by Mickael Istria
Modified:	2018-11-27 01:09 EST (History)
CC List:	3 users (show)

See Also:	539139

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Mickael Istria

2018-10-11 07:43:13 EDT

Running builds in parallel, I got (once, not deterministic) the following stack

java.nio.file.FileSystemAlreadyExistsException
	at jdk.zipfs/jdk.nio.zipfs.ZipFileSystemProvider.newFileSystem(ZipFileSystemProvider.java:99)
	at java.base/java.nio.file.FileSystems.newFileSystem(FileSystems.java:344)
	at java.base/java.nio.file.FileSystems.newFileSystem(FileSystems.java:293)
	at org.eclipse.jdt.internal.core.builder.ClasspathJrt.initialize(ClasspathJrt.java:195)
	at org.eclipse.jdt.internal.core.builder.ClasspathJrt.<init>(ClasspathJrt.java:79)
	at org.eclipse.jdt.internal.core.builder.ClasspathLocation.forJrtSystem(ClasspathLocation.java:142)
	at org.eclipse.jdt.internal.core.builder.NameEnvironment.computeClasspathLocations(NameEnvironment.java:309)
	at org.eclipse.jdt.internal.core.builder.NameEnvironment.<init>(NameEnvironment.java:59)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.initializeBuilder(JavaBuilder.java:622)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:173)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:834)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:228)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:271)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:324)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:327)
	at org.eclipse.core.internal.events.BuildManager.lambda$2(BuildManager.java:446)
	at org.eclipse.core.internal.events.GraphProcessor$1.run(GraphProcessor.java:119)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

Comment 1 Andrey Loskutov

2018-10-11 08:03:39 EDT

This is most likely bug 539139.

Comment 2 Andrey Loskutov

2018-10-11 08:04:35 EDT

Mickael, which *exact* SDK version are you running? 4.5 isn't for sure.

Comment 3 Mickael Istria

2018-10-11 08:30:13 EDT

Good news then. I'm very happy to learn by the way that you're also building stuff in parallel, so you'll face and fix most issues early and that makes the parallel build of workspace much more likely to be successful ;)
I was indeed running an older version of JDT (in a Launch Configuration) before 663d2aeab612e27f9394dd869bac4e6be7efb149 got merged when this happened.

*** This bug has been marked as a duplicate of bug 539139 ***

Comment 4 Jay Arthanareeswaran

2018-11-27 01:09:34 EST

Verified for 4.10 M1 using build I20181121-1800.