Stack tracing tests of sleeping thread should be more resilient to code changes

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Unresolved
    • Priority: P4
    • tbd
    • Affects Version/s: None
    • Component/s: hotspot
    • None

      At present three test classes:

      test/hotspot/jtreg/vmTestbase/nsk/monitoring/stress/thread/strace001.java
      test/hotspot/jtreg/vmTestbase/nsk/monitoring/share/ThreadController.java
      test/hotspot/jtreg/vmTestbase/nsk/monitoring/share/thread/SleepingThread.java

      examine the stack of a thread blocked in Thread.sleep. Every time the implementation of Thread.sleep changes (e.g. the JFR event, virtual threads) the list of expected stack frames needs to be updated. This is very tedious and we should find a way to avoid it.

            Assignee:
            Ramkumar Sunderbabu
            Reporter:
            David Holmes
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: