7067310: 3 tests from closed/javax/sound/sampled caused BSOD on win 7 x86

[prrace]

I am de-problem listing several sound tests.
These tests pass over and over again on all platforms when run on JDK 27 in an environment that supports sound.
I'm seeing no failures at all.
There are multiple bug IDs used to problem list these tests but only one can be the 'main' bug ID.
I've picked the oldest for that, and will "add" some of the additional issues.
In a few cases they happen to be non-public bugs for the accidental reason that someone added some internal information I can't delete, so you won't be able to see those bug ids, but there's nothing special about them and I'll close them as dups of 7067310

---

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

Issues

• JDK-7067310: 3 tests from closed/javax/sound/sampled caused BSOD on win 7 x86 (Bug - P3)
• JDK-8307574: ClipIsRunningAfterStop.java failed with "../nptl/pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed." (Bug - P4)
• JDK-8308395: javax/sound/sampled/Clip/ClipFlushCrash.java timed out (Bug - P4)

Reviewers

• Sergey Bylokhov (@mrserb - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28774

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[prrace]

This test still fails so I can't remove it from the problem list.

[prrace]

/label client

[prrace]

/issue add 8265485,8307574,8308395

[bridgekeeper]

👋 Welcome back prr! 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]

@prrace 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:

7067310: 3 tests from closed/javax/sound/sampled caused BSOD on win 7 x86
8307574: ClipIsRunningAfterStop.java failed with "../nptl/pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed."
8308395: javax/sound/sampled/Clip/ClipFlushCrash.java timed out

Reviewed-by: serb

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 5 new commits pushed to the master branch:

• 325cdb7: 8373517: Revert the macos Tahoe specific change done in JDK-8359830
• c46bed7: 8371502: serviceability/jvmti/vthread/ThreadListStackTracesTest/ThreadListStackTracesTest.java failing
• ae85d89: 8373389: Two jdk/incubator/vector/ tests fails after JDK-8371446
• ... and 2 more: https://git.openjdk.org/jdk/compare/692edc4879489d44a477a03028eb3e7ef9dff388...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]

@prrace
The client label was successfully added.

[openjdk]

@prrace The issue 8265485 was not found in the JDK project - make sure you have entered it correctly.
As there were validation problems, no additional issues will be added to the list of solved issues.

[openjdk]

@prrace 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
• hotspot
• hotspot-compiler
• hotspot-gc
• hotspot-jfr
• hotspot-runtime
• i18n
• ide-support
• javadoc
• jdk
• jmx
• net
• nio
• security
• serviceability
• shenandoah

[prrace]

/issue add 8307574,8308395

[mlbridge]

Webrevs

• 00: Full (cce6bf8e)

[openjdk]

@prrace
Adding additional issue to issue list: 8307574: ClipIsRunningAfterStop.java failed with "../nptl/pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion mutex->__data.__owner == 0' failed."`.

Adding additional issue to issue list: 8308395: javax/sound/sampled/Clip/ClipFlushCrash.java timed out.

[prrace]

/integrate

[openjdk]

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

• e65e068: 8372592: Adjust logger usage in java2d tests
• 0eb2bcd: 8372250: Merge PtrQueue into SATBMarkQueue
• 6ec36d3: 8373059: Test sun/security/provider/acvp/ML_DSA_Intrinsic_Test.java should pass on Aarch64
• ... and 12 more: https://git.openjdk.org/jdk/compare/692edc4879489d44a477a03028eb3e7ef9dff388...master

Your commit was automatically rebased without conflicts.

[openjdk]

@prrace Pushed as commit 9b12c0b.

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