bootcycle builds x86_64-linux-gnu?

Magnus Ihse Bursie magnus.ihse.bursie at
Mon Dec 10 10:19:24 UTC 2018

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.

... Found it! Erik's intuition was correct:

ALL_NAMED_TESTS >build core_tools ctw_1 ctw_2 ctw_3 [...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-'/<<PKGBUILDDIR>>' failure-handler make<
make[5]: Leaving directory '/<<PKGBUILDDIR>>'
make/Main.gmk:1088: *** target pattern contains no '%'.  Stop.

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.

We should probably send that as a flag to make, always.


> [1]
> [2]
>> /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, ALL_NAMED_TESTS)
>>>> /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.
>>> ALL_NAMED_TESTS >build core_tools ctw_1 ctw_2 ctw_3 hotspot_all
>>> hotspot_all_no_apps hotspot_appcds hotspot_cds hotspot_co
>>> mpiler hotspot_compiler_all_gcs hotspot_compiler_xcomp hotspot_gc
>>> hotspot_handshake hotspot_misc hotspot_native_sanity ho
>>> tspot_nmt hotspot_not_fast_compiler hotspot_not_fast_gc hotspot_rest_runtime
>>> hotspot_runtime hotspot_runtime_minimalvm ho
>>> tspot_serviceability hotspot_slow_compiler hotspot_tier2_runtime
>>> hotspot_tier2_runtime_platform_agnostic hotspot_tier3_ru
>>> ntime jaxp_all jcstress_part1 jcstress_part2 jcstress_part3 jdk_2d jdk_awt
>>> jdk_beans jdk_client_sanity jdk_collections jd
>>> k_collections_core jdk_concurrent jdk_core jdk_desktop jdk_desktop_core
>>> jdk_imageio jdk_instrument jdk_instrument_sanity
>>> jdk_io jdk_jdi jdk_jdi_sanity jdk_jfr jdk_jfr_sanity jdk_jmx jdk_jmx_sanity
>>> jdk_lang jdk_launcher jdk_management jdk_mana
>>> gement_sanity jdk_math jdk_native_sanity jdk_net jdk_nio jdk_other jdk_rmi
>>> jdk_sctp jdk_security jdk_security1 jdk_security2 jdk_security3 jdk_security4
>>> jdk_security_infra jdk_sound jdk_stable jdk_stream jdk_svc jdk_svc_sanity
>>> jdk_swing jdk_swing_core jdk_text jdk_time jdk_tools jdk_util jdk_util_other
>>> jfc_demo needs_g1gc svc_tools svc_tools_sanity tier1 tier1_common tier1_compiler
>>> tier1_compiler_1 tier1_compiler_2 tier1_compiler_3 tier1_compiler_not_cms
>>> tier1_compiler_not_xcomp tier1_gc tier1_gc_1 tier1_gc_2 tier1_gc_gcbasher
>>> tier1_gc_gcold tier1_part1 tier1_part2 tier1_part3 tier1_runtime
>>> tier1_runtime_appcds tier1_runtime_appcds_exclude tier1_serviceability tier2
>>> tier2_part1 tier2_part2 tier2_part3 tier3 vmTestbase_largepages
>>> vmTestbase_nsk_aod vmTestbase_nsk_jdb vmTestbase_nsk_jdi
>>> vmTestbase_nsk_jdi_quick vmTestbase_nsk_jdwp vmTestbase_nsk_jdwp_quick
>>> vmTestbase_nsk_jvmti vmTestbase_nsk_jvmti_quick vmTestbase_nsk_monitoring
>>> vmTestbase_nsk_monitoring_quick vmTestbase_nsk_stress vmTestbase_nsk_sysdict
>>> vmTestbase_vm_compiler vmTestbase_vm_compiler_quick vmTestbase_vm_defmeth
>>> vmTestbase_vm_g1classunloading vmTestbase_vm_gc vmTestbase_vm_gc_compact
>>> vmTestbase_vm_gc_concurrent vmTestbase_vm_gc_container vmTestbase_vm_gc_juggle
>>> vmTestbase_vm_gc_locker vmTestbase_vm_gc_misc vmTestbase_vm_gc_quick
>>> vmTestbase_vm_gc_ref vmTestbase_vm_metaspace vmTestbase_vm_mlvm gtest micro
>>> make-make-base make-java-compilation make-copy-files make-idea
>>> make-compile-commands failure-handler make<

More information about the hotspot-dev mailing list