bootcycle builds x86_64-linux-gnu? (original) (raw)

Severin Gehwolf sgehwolf at redhat.com
Tue Dec 11 13:22:01 UTC 2018

On Mon, 2018-12-10 at 19:02 +0100, Matthias Klose wrote:

On 10.12.18 11:19, Magnus Ihse Bursie wrote: > > > On 2018-12-09 11:58, Matthias Klose wrote: > > On 06.12.18 22:03, Erik Joelsson wrote: > > > Nothing strange in there. Is it only printed once? I wouldn't be surprised if > > > this got printed more than one time during a normal make execution (due to > > > reloads caused by -include). If it is, then perhaps there is something different > > > in a later print? > > > > no, it's only printed once. And it seems to be independent of the test-image > > target. just the bootcycle-images target is enough to trigger that [1]. Also not > > architecture specific for the hotspot targets. Builds without the bootcycle > > target succeed [2]. > > > > Anything else wrong with the configury in [1]? > > It's a bit hard to say. I'm reacting to "make -C build", maybe the -C does not > play well with bootcycle builds? I don't think that's a very well tested > combination, and bootcycle builds is really like running the build twice in > different directories. But I don't know, it shouldn't affect things... > You are also running with a very detailed log level, it hardly makes it easier > to read the log. I recommend using "info,cmdlines" instead of "debug" unless > actively debugging a hard-to-find issue.

I'm using the separate build dir to build the server and zero jvm variants. In the past --with-jvm-variants=server,zero was not supported, and you can't do bootcycle builds for both variants. Replacing LOG=debug with LOG=info,cmdlines still lets the build fail, or was that expected? > ... Found it! Erik's intuition was correct: > > ALLNAMEDTESTS >build coretools ctw1 ctw2 ctw3 [...snip...] gtest micro > make-make-base make-java-compilation make-copy-files make-idea > make-compile-commands make-make[5]: make-Leaving make-directory > make-'/<>' failure-handler make<_ _> make[5]: Leaving directory '/<>' > make/Main.gmk:1088: *** target pattern contains no '%'. Stop.

Reproduced. I've filed https://bugs.openjdk.java.net/browse/JDK-8215213

Thanks, Severin

> So once again we're being bit by the make changedir message. And maybe that's > triggered in a new way due to the -C? Try adding --no-print-directory to your > top-level make invocation, as a workaround.

Yes, this lets the bootcycle build succeed. Thanks for the pointer! Matthias

> > We should probably send that as a flag to make, always. > > /Magnus > > > > > [1] > > https://buildd.debian.org/status/fetch.php?pkg=openjdk-12&arch=amd64&ver=12~23-2&stamp=1544145960&raw=0 > > > > [2] https://buildd.debian.org/status/package.php?p=openjdk-12 > > > > > > > /Erik > > > > > > On 2018-12-06 11:23, Matthias Klose wrote: > > > > On 06.12.18 20:04, Erik Joelsson wrote: > > > > > Could you insert this before line 1087 in make/Main.gmk and post the output? > > > > > > > > > > $(call PrintVar, ALLNAMEDTESTS) > > > > > > > > > > /Erik > > > > > > > > > > On 2018-12-06 10:31, Matthias Klose wrote: > > > > > > On 06.12.18 17:41, Aleksey Shipilev wrote: > > > > > > > On 12/6/18 4:34 PM, Matthias Klose wrote: > > > > > > > > my bad, that happens in the test-image target: > > > > > > > > > > > > > > > > In the build log I see: > > > > > > > > > > > > > > > > FindJtregGroups /home/packages/openjdk/12/openjdk-12-12~23/test/jdk > > > > > > > > FindJtregGroups /home/packages/openjdk/12/openjdk-12-12~23/test/langtools > > > > > > > > FindJtregGroups /home/packages/openjdk/12/openjdk-12-12~23/test/nashorn > > > > > > > > FindJtregGroups /home/packages/openjdk/12/openjdk-12-12~23/test/jaxp > > > > > > > > > > > > > > > > > > > > > > > > make[5]: Leaving directory '/home/packages/openjdk/12/openjdk-12-12~23' > > > > > > > > make/Main.gmk:1087: *** target pattern contains no '%'. Stop. > > > > > > > > make[5]: Entering directory '/home/packages/openjdk/12/openjdk-12-12~23' > > > > > > > > make[5]: warning: -j1 forced in submake: resetting jobserver mode. > > > > > > > > > > > > > > I wonder if "~" in your path screws things up. > > > > > > > > > > > > that worked at least for the openjdk-11 development cycle, and replacing the > > > > > > tilde with a dash makes no difference. > > > > > > > > ALLNAMEDTESTS >build coretools ctw1 ctw2 ctw3 hotspotall > > > > hotspotallnoapps hotspotappcds hotspotcds hotspotco > > > > mpiler hotspotcompilerallgcs hotspotcompilerxcomp hotspotgc > > > > hotspothandshake hotspotmisc hotspotnativesanity ho > > > > tspotnmt hotspotnotfastcompiler hotspotnotfastgc hotspotrestruntime > > > > hotspotruntime hotspotruntimeminimalvm ho > > > > tspotserviceability hotspotslowcompiler hotspottier2runtime > > > > hotspottier2runtimeplatformagnostic hotspottier3ru > > > > ntime jaxpall jcstresspart1 jcstresspart2 jcstresspart3 jdk2d jdkawt > > > > jdkbeans jdkclientsanity jdkcollections jd > > > > kcollectionscore jdkconcurrent jdkcore jdkdesktop jdkdesktopcore > > > > jdkimageio jdkinstrument jdkinstrumentsanity > > > > jdkio jdkjdi jdkjdisanity jdkjfr jdkjfrsanity jdkjmx jdkjmxsanity > > > > jdklang jdklauncher jdkmanagement jdkmana > > > > gementsanity jdkmath jdknativesanity jdknet jdknio jdkother jdkrmi > > > > jdksctp jdksecurity jdksecurity1 jdksecurity2 jdksecurity3 jdksecurity4 > > > > jdksecurityinfra jdksound jdkstable jdkstream jdksvc jdksvcsanity > > > > jdkswing jdkswingcore jdktext jdktime jdktools jdkutil jdkutilother > > > > jfcdemo needsg1gc svctools svctoolssanity tier1 tier1common > > > > tier1compiler > > > > tier1compiler1 tier1compiler2 tier1compiler3 tier1compilernotcms > > > > tier1compilernotxcomp tier1gc tier1gc1 tier1gc2 tier1gcgcbasher > > > > tier1gcgcold tier1part1 tier1part2 tier1part3 tier1runtime > > > > tier1runtimeappcds tier1runtimeappcdsexclude tier1serviceability tier2 > > > > tier2part1 tier2part2 tier2part3 tier3 vmTestbaselargepages > > > > vmTestbasenskaod vmTestbasenskjdb vmTestbasenskjdi > > > > vmTestbasenskjdiquick vmTestbasenskjdwp vmTestbasenskjdwpquick > > > > vmTestbasenskjvmti vmTestbasenskjvmtiquick vmTestbasenskmonitoring > > > > vmTestbasenskmonitoringquick vmTestbasenskstress vmTestbasensksysdict > > > > vmTestbasevmcompiler vmTestbasevmcompilerquick vmTestbasevmdefmeth > > > > vmTestbasevmg1classunloading vmTestbasevmgc vmTestbasevmgccompact > > > > vmTestbasevmgcconcurrent vmTestbasevmgccontainer vmTestbasevmgcjuggle > > > > vmTestbasevmgclocker vmTestbasevmgcmisc vmTestbasevmgcquick > > > > vmTestbasevmgcref vmTestbasevmmetaspace vmTestbasevmmlvm gtest micro > > > > make-make-base make-java-compilation make-copy-files make-idea > > > > make-compile-commands failure-handler make<

More information about the build-dev mailing list