8358627: tools/sincechecker/modules/java.base/JavaBaseCheckSince.java fails with JDK 26

[nizarbenalla]

Once 8346295 is resolved, JavaBaseCheckSince no longer needs to be problemlisted.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8358627: tools/sincechecker/modules/java.base/JavaBaseCheckSince.java fails with JDK 26 (Bug - P4)

Reviewers

• SendaoYan (@sendaoYan - Committer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25855/head:pull/25855
$ git checkout pull/25855

Update a local copy of the PR:
$ git checkout pull/25855
$ git pull https://git.openjdk.org/jdk.git pull/25855/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25855

View PR using the GUI difftool:
$ git pr show -t 25855

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25855.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back nbenalla! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

[openjdk]

@nizarbenalla To determine the appropriate audience for reviewing this pull request, one or more labels corresponding to different subsystems will normally be applied automatically. However, no automatic labelling rule matches the changes in this pull request. In order to have an "RFR" email sent to the correct mailing list, you will need to add one or more applicable labels manually using the /label pull request command.

Applicable Labels

• build
• client
• compiler
• core-libs
• graal
• hotspot
• hotspot-compiler
• hotspot-gc
• hotspot-jfr
• hotspot-runtime
• i18n
• ide-support
• javadoc
• jdk
• jmx
• kulla
• net
• nio
• security
• serviceability
• shenandoah

[nizarbenalla]

/label add javadoc
/label add core-libs

[openjdk]

@nizarbenalla
The javadoc label was successfully added.

[openjdk]

@nizarbenalla
The core-libs label was successfully added.

[mlbridge]

Webrevs

• 00: Full (861f4388)

[openjdk-notifier]

The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork:

git checkout problemlisted-sincecheck-test
git fetch https://git.openjdk.org/jdk.git master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push