-
Bug
-
Resolution: Fixed
-
P3
-
12
-
b21
The build-microbenchmark target currently depends on a few modules, but actually has compile dependencies on at least one additional (java.xml). This went unnoticed since once a few modules like jdk.unsupported and java.management has been built, many other modules will have already been built since this phase is typically highly parallelized. On some systems this intermittently fail, making it obvious that an explicit dependency is needed.
While more fine-grained options exist, if we were to change to depend on exploded-image we will probably avoid any future fragility altogether with only minimal effective difference in build task parallelism:
- build-microbenchmark: interim-langtools jdk.unsupported java.management
+ build-microbenchmark: interim-langtools exploded-image
While more fine-grained options exist, if we were to change to depend on exploded-image we will probably avoid any future fragility altogether with only minimal effective difference in build task parallelism:
- build-microbenchmark: interim-langtools jdk.unsupported java.management
+ build-microbenchmark: interim-langtools exploded-image