accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4443) Make performance test category usage consistent with other categories
Date Fri, 02 Sep 2016 18:12:20 GMT


Christopher Tubbs commented on ACCUMULO-4443:

I updated the documentation to be very explicit about how to run each category or run all
but that category. I can add more documentation to describe combining them in a future issue
to have more fine-grained control. I was thinking about doing that as part of ACCUMULO-4442,
when I update the docs to describe those categories.

The problem with not having both categories, is that if you don't, the other categories won't
work correctly. Since this performance test can only run on minicluster, if both categories
weren't added, and a user ran with something like {{-DexcludedGroups=...MiniClusterOnlyTests}},
then it would not exclude this performance test, and that would be problematic.

> Make performance test category usage consistent with other categories
> ---------------------------------------------------------------------
>                 Key: ACCUMULO-4443
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: test
>    Affects Versions: 1.8.0
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>            Priority: Minor
>             Fix For: 1.8.0
>          Time Spent: 20m
>  Remaining Estimate: 0h
> Currently, performance tests categories are excluded by default in 1.8+ branches.
> This is unexpected when trying to do a full build.
> It is also documented as being triggered differently than other test categories, even
though it is using the same basic categorization method.
> For consistency, we should include all tests by default, and update the performance tests
documentation to match how the other test categories are documented and used.

This message was sent by Atlassian JIRA

View raw message