accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4510) Accumulo test benchmarks should go in a separate git repo
Date Wed, 25 Jan 2017 15:57:26 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837961#comment-15837961
] 

ASF GitHub Bot commented on ACCUMULO-4510:
------------------------------------------

Github user keith-turner commented on a diff in the pull request:

    https://github.com/apache/accumulo-testing/pull/2#discussion_r97805921
  
    --- Diff: bin/accumulo-testing ---
    @@ -25,8 +25,16 @@ function print_usage() {
     Usage: accumulo-testing <command> (<argument>)
     
     Possible commands:
    -  rw-local <module>         Runs randomwalk <module> in local java process
    -  rw-yarn <num> <module>    Runs randomwalk <module> in <num>
containers on YARN
    +  agitator <command>            Runs agitator <command>. Available commands:
start, stop
    +  ci-createtable                Creates Accumulo table with splits for continuous ingest
tests
    +  ci-local <application>        Runs continuous ingest <application> in local
java process
    --- End diff --
    
    this is nice


> Accumulo test benchmarks should go in a separate git repo
> ---------------------------------------------------------
>
>                 Key: ACCUMULO-4510
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4510
>             Project: Accumulo
>          Issue Type: Task
>            Reporter: Christopher Tubbs
>            Assignee: Mike Walch
>            Priority: Minor
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Benchmarks should be version-independent, and/or work across versions to be meaningful.
The tests/benchmark scripts which accompany Accumulo releases are also not necessarily tested
or even functional. They should be shipped separately, if we continue to maintain them at
all. I actually don't even think they need to be released. They can be continuously updated
as needed for developer testing/benchmarking, without necessarily releasing (similar with
examples, and website documentation).
> We can request a new git repo easily at https://reporeq.apache.org



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message