8380282: [lworld] Problem-list several SA/jhsdb tests when running with --enable-preview#2236
8380282: [lworld] Problem-list several SA/jhsdb tests when running with --enable-preview#2236Arraying wants to merge 4 commits intoopenjdk:lworldfrom
Conversation
|
👋 Welcome back phubner! A progress list of the required criteria for merging this PR into |
|
@Arraying 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: 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 125 new commits pushed to the
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 |
Webrevs
|
|
What is the motivation for disabling all the SA tests instead of problem listing just the failing tests? How many SA tests are failing with --enable-preview? |
|
I would 100% much rather we programmatically disable them than problem list a list of tests. The ProblemList list is noise that I thought I cleaned out once but it keeps changing. This is a lot better. Also if this fixes this test to not run, it should be removed from the problem list. |
|
I agree with Chris. |
|
I feel like this makes extra work in categorizing and triaging issues for something that is going to continue to break in different ways all the time. Maybe we could have one issue to reenable the tests and fix them, if we plan on fixing these in the future. |
|
It is best to detect new failures as they happen, not months down the road when someone decides to disable this change and retest, and then has to figure out what changes caused the new failures. It looks like only 8 tests out of about 90 tests are failing. Most of the failures I skimmed over already have bugs filed for them. We should get them all problem listed so we have clean results and can then readily detect new failures. |
|
Thanks for the feedback, everyone. I've disabled the tests I found failing, and created JBS issues where necessary. |
coleenp
left a comment
There was a problem hiding this comment.
I guess it's only two bugs so not a big effort. Looks good.
|
@plummercj @alexmenkov could I get a quick svc review/look before I integrate? TIA. |
| serviceability/sa/TestJmapCore.java 8380779 generic-all | ||
| serviceability/sa/TestJmapCoreMetaspace.java 8380779 generic-all |
There was a problem hiding this comment.
The following tests should use 8379925:
serviceability/sa/TestJmapCore.java
serviceability/sa/TestJmapCoreMetaspace.java
serviceability/sa/ClhsdbDumpheap.java
The other 4 are all separate issues and they don't require -XX:-UseCompressedOops to reproduce. I was actually getting ready to do a problem list update myself (already have the diffs in place) but was just holding off until I could get bugs filed. If you want to file them all under 8379925 for now that is ok. I might change them once I file new CRs, but you should update the CR to not require -XX:-UseCompressedOops.
There was a problem hiding this comment.
Actually the 8380769 CR is correct for TestHeapDumpForLargeArray.java. I misread it as 8380779
There was a problem hiding this comment.
I think you meant 8379920 (8379925 is about /jdk/sun/tools/jhsdb/ tests)
I've closed 8379920 as a dup of 8380779
There was a problem hiding this comment.
Either 8379925 or 8379920 is fine. They are dups, so whichever one is kept open.
There was a problem hiding this comment.
I filed JDK-8380851 for serviceability/sa/ClhsdbJstackWithConcurrentLock.java
There was a problem hiding this comment.
I filed JDK-8380852 for serviceability/sa/CDSJMapClstats.java
There was a problem hiding this comment.
I filed JDK-8380853 for the serviceability/sa/ClhsdbJhisto.java failure
|
@plummercj @alexmenkov thanks for the feedback. I've updated the tests to use 8379925 and removed the ones being addressed in the PR. I'll address the comments in the JBS issues momentarily. |
|
I did not mean to close the PR, but if you think it's easier to do the problemlist changes in your respective feature PRs I'm okay to abandon this. |
Hi,
The following tests fail with
--enable-previewand have been bulk problemlisted:Testing on Linux (x64, AArch64), macOS (x64, AArch64), Windows x64:
:hotspot_serviceability(most of the SA tests), with and without preview:hotspot_resourcehogs(some SA tests), with and without preview:svc_tools(somejhsdbtests), with and without previewProgress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/valhalla.git pull/2236/head:pull/2236$ git checkout pull/2236Update a local copy of the PR:
$ git checkout pull/2236$ git pull https://git.openjdk.org/valhalla.git pull/2236/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 2236View PR using the GUI difftool:
$ git pr show -t 2236Using diff file
Download this PR as a diff file:
https://git.openjdk.org/valhalla/pull/2236.diff
Using Webrev
Link to Webrev Comment