Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8249618 normalize usage of @ignore and ProblemList
  3. JDK-8249833

java/util/zip/3GBZipFiles.sh uses @ignore w/o bug-id

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: P4 P4
    • tbd
    • 8, 11, 15, 16
    • core-libs

      java/util/zip/3GBZipFiles.sh has '@ignore ignore runs for hours and eats up 7 Gigabytes of disk space'; canonically, @ignore should be followed by the id of the bug which describes the problem and will be used to eventually fix it.

      the more appropriate solutions for a situation when tests have special requirements:
       - use `@requires` to check that the necessary conditions are met. in this case, this might including the creation of new at-requires property (in /test/lib/jtreg-ext/requires/VMProps.java or better a separate EnvProps class) which check how much of disk space is available;
       - using custom check login in tests and throwing jtreg.SkippedException;
       - using '/manual' jtreg option, which will exclude tests from automated runs, yet will still be possible for "manual" execution by direct jtreg invocation.

      please note, that currently, both @run are excluded when jtreg is run w/ -ignore:quite (which is what run-test uses), to restore "fast" @run, the test should be split into two sub-tests -- two comment section where each one starts w/ @test tag. `@requires` solution will also require the test to be split, as `@requires` applied for the whole @test, not an individual @run.

            isipka Ivan Sipka
            iignatyev Igor Ignatyev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: