Heads-up: default configuration name change in jdk11u-dev?

[Langer, Christoph]

Hi Aleksey,

thanks for spotting this. It obviously was an oversight. I tried to review this change as thorough as I could but I feared something like this could happen. Hopefully there's nothing else, though.

Regarding JDK-8210962, I see two options. Either back it out or mark it as backported. I would think we could go with the latter, though, as I would hope "only" some CI scripts could be affected. 

Best regards
Christoph

> -----Original Message-----
> From: jdk-updates-dev <jdk-updates-dev-retn at openjdk.org> On Behalf Of
> Aleksey Shipilev
> Sent: Montag, 19. September 2022 20:24
> To: jdk-updates-dev at openjdk.java.net
> Subject: Heads-up: default configuration name change in jdk11u-dev?
> 
> Hi,
> 
> I was sifting through my CI build logs and I realized that all of the sudden
> jdk11u-dev tree now configures itself into "linux-x86_64-server-fastdebug", not
> into "linux-x86_64-normal-server-fastdebug", as usual. Which breaks CI scripts.
> Granted, more reliable scripts would set the configuration names explicitly, but
> still this is a subtle breakage.
> 
> Upstream removed "-normal-" part with:
>    https://bugs.openjdk.org/browse/JDK-8210962
> 
> jdk11u-dev bisection shows the same happened in this backport:
>    https://github.com/openjdk/jdk11u-
> dev/commit/75b3e45fe9d16a8e29f4fd51f93e01acc9436562
> 
> Notice the "move" around CONF_NAME variable from basics.m4 to basic.m4.
> This actually makes me wonder if there are other subtle changes happened
> during this move.
> 
> --
> Thanks,
> -Aleksey