JDK-8191943 : [TESTBUG] docker/TestCPUAwareness fails on machine with 2 CPUs
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 10
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2017-11-28
  • Updated: 2024-06-04
  • Resolved: 2017-12-01
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 10
10 b36Fixed
Related Reports
Relates :  
JDK-8189762 - [TESTBUG] Create tests for JDK-8146115 container awareness and resource configuration
Description
When running on machine with 2 CPUs, the test test/hotspot/jtreg/runtime/containers/docker$ enw TestCPUAwareness.java fails. 
The test should check for number of CPUs available on a test host/node and skip test configurations that are not applicable for given number of CPUs.
Comments
URL: http://hg.openjdk.java.net/jdk/jdk/rev/59ebea050a0d User: jwilhelm Date: 2017-12-07 09:00:22 +0000
07-12-2017
URL: http://hg.openjdk.java.net/jdk/hs/rev/59ebea050a0d User: mseledtsov Date: 2017-12-01 04:48:45 +0000
01-12-2017
Addressed feedback from Bob and David: http://cr.openjdk.java.net/~mseledtsov/8191943.02/
30-11-2017
After discussions with Bob I took a different approach. Rather then limiting test case execution for cases exceeding the available CPUs the change now updates expected Active Process Count value to not exceed the number of available CPUs. This closed reflects the VM behavior. Here is the updated webrev: http://cr.openjdk.java.net/~mseledtsov/8191943.01/
30-11-2017
Fixed; tested. WebRev: http://cr.openjdk.java.net/~mseledtsov/8191943.00/ Testing: 1. Locally: exercised the affected test locally on Linux-x64 2. Exercised the affected test on 2 processor machine 3. Exercise the affected test via automated distributed test system In progress
29-11-2017