Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

8297984: Turn on warnings as errors for javadoc #11468

Closed
wants to merge 4 commits into from

Conversation

magicus
Copy link
Member

@magicus magicus commented Dec 1, 2022

For some reason, we never turned on -Werror for javadoc. It is high time to do so.

This PR also fixes a recent issue with the javadoc in JFR that caused a warning, and enables building of javadoc on GHA. (It takes about 3 minutes, as a separate build job.)


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

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 11468

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

Using diff file

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

@magicus magicus changed the title Improve javadocs checking 8297984: Turn on warnings as errors for javadoc Dec 1, 2022
@bridgekeeper
Copy link

bridgekeeper bot commented Dec 1, 2022

👋 Welcome back ihse! 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 openjdk bot added the rfr Pull request is ready for review label Dec 1, 2022
@openjdk
Copy link

openjdk bot commented Dec 1, 2022

@magicus The following labels will be automatically applied to this pull request:

  • build
  • hotspot-jfr

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added build build-dev@openjdk.org hotspot-jfr hotspot-jfr-dev@openjdk.org labels Dec 1, 2022
@mlbridge
Copy link

mlbridge bot commented Dec 1, 2022

Webrevs

Copy link
Member

@mrserb mrserb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@openjdk
Copy link

openjdk bot commented Dec 2, 2022

@magicus This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8297984: Turn on warnings as errors for javadoc

Reviewed-by: serb, erikj

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 20 new commits pushed to the master branch:

  • 227364d: 8297953: Fix several C2 IR matching tests for RISC-V
  • 1370228: 8297941: Add override modifier in space.hpp
  • 319faa5: 8296084: javax/swing/JSpinner/4788637/bug4788637.java fails intermittently on a VM
  • b73363f: 8297686: JFR: Improve documentation of EventStream::onMetadata(Consumer)
  • 1376f33: 8297911: Memory leak in JfrUpcalls::on_retransform
  • 5c0ff26: 8291444: GHA builds/tests won't run manually if disabled from automatic running
  • 6d0fbb2: 8297645: Drop the test/jdk/java/net/httpclient/reactivestreams-tck-tests/TckDriver.java test
  • 687fd71: 8297549: RISC-V: Add support for Vector API vector load const operation
  • d50015a: 8297715: RISC-V: C2: Use single-bit instructions from the Zbs extension
  • 9bbcb54: 8297784: Optimize @stable field for Method.isCallerSensitive
  • ... and 10 more: https://git.openjdk.org/jdk/compare/09629570f5d064dc2a5cd670de8d648156ac3991...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Dec 2, 2022
@erikj79
Copy link
Member

erikj79 commented Dec 2, 2022

If you would like to exercise the full-docs build in GHA, you could make that build depend on the linux-x64 build and set --with-build-jdk and --with-docs-reference-jdk to point to it. That's how we do it internally at Oracle.

@magicus
Copy link
Member Author

magicus commented Dec 2, 2022

If you would like to exercise the full-docs build in GHA, you could make that build depend on the linux-x64 build and set --with-build-jdk and --with-docs-reference-jdk to point to it.

Good point. I don't think it's worth it, though. Since the output is not saved but thrown away, we will just be wasting CPU cycles. The full docs graph generation is unlikely to start failing as a result of general changes in the code, only if some of the code that generates the graphs were to be changed, and such PRs can test this separately.

@magicus
Copy link
Member Author

magicus commented Dec 2, 2022

Since we do not do "apt install graphviz", configure will automatically determine that full docs is impossible. My intent were to keep it that way, since if for some reason "dot" were to be installed on the GHA image, then suddenly the build time would jump from 3 minutes to 60, so I wanted to make it clear that we never want this to happen.

However, I realize my comment might be misunderstood as if full docs is impossible to do without the cost of rebuilding everything. I'll see if I can clarify it without turning it into an essay about the reasoning.

@magicus
Copy link
Member Author

magicus commented Dec 2, 2022

/integrate

@openjdk
Copy link

openjdk bot commented Dec 2, 2022

Going to push as commit df07255.
Since your change was applied there have been 20 commits pushed to the master branch:

  • 227364d: 8297953: Fix several C2 IR matching tests for RISC-V
  • 1370228: 8297941: Add override modifier in space.hpp
  • 319faa5: 8296084: javax/swing/JSpinner/4788637/bug4788637.java fails intermittently on a VM
  • b73363f: 8297686: JFR: Improve documentation of EventStream::onMetadata(Consumer)
  • 1376f33: 8297911: Memory leak in JfrUpcalls::on_retransform
  • 5c0ff26: 8291444: GHA builds/tests won't run manually if disabled from automatic running
  • 6d0fbb2: 8297645: Drop the test/jdk/java/net/httpclient/reactivestreams-tck-tests/TckDriver.java test
  • 687fd71: 8297549: RISC-V: Add support for Vector API vector load const operation
  • d50015a: 8297715: RISC-V: C2: Use single-bit instructions from the Zbs extension
  • 9bbcb54: 8297784: Optimize @stable field for Method.isCallerSensitive
  • ... and 10 more: https://git.openjdk.org/jdk/compare/09629570f5d064dc2a5cd670de8d648156ac3991...master

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Dec 2, 2022
@openjdk openjdk bot closed this Dec 2, 2022
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Dec 2, 2022
@openjdk
Copy link

openjdk bot commented Dec 2, 2022

@magicus Pushed as commit df07255.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

@magicus magicus deleted the improve-javadocs-checking branch December 2, 2022 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build build-dev@openjdk.org hotspot-jfr hotspot-jfr-dev@openjdk.org integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

3 participants