[testbug] CoreThreadTimeOut still uses hardcoded timeout

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P3
    • 9
    • Affects Version/s: 9
    • Component/s: core-libs

        java/util/concurrent/ThreadPoolExecutor/CoreThreadTimeOut.java has 2 wrong assumptions:
        1) test assumes that 10 tested threads won't finish in 30 milliseconds
        2) test assumes that 10 tested threads will finish in 10 seconds

        both assumptions are hw- and system- specific. Depending on system load and hw capabilities these time metrics might be wrong. Test needs to be re-organized to not rely on hardcoded timeouts.

              Assignee:
              Martin Buchholz
              Reporter:
              Dmitrij Pochepko
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: