You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@geode.apache.org by "upthewaterspout (GitHub)" <gi...@apache.org> on 2018/11/22 00:06:09 UTC

[GitHub] [geode-benchmarks] upthewaterspout opened pull request #4: GEODE-6086: Looking for the output files in the correct location

Yardstick creates a subdirectory, so find the files in that directory

[ Full content available at: https://github.com/apache/geode-benchmarks/pull/4 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org

[GitHub] [geode-benchmarks] WireBaron commented on pull request #4: GEODE-6086: Looking for the output files in the correct location

Posted by "WireBaron (GitHub)" <gi...@apache.org>.

Lingering comment

[ Full content available at: https://github.com/apache/geode-benchmarks/pull/4 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org

[GitHub] [geode-benchmarks] WireBaron commented on pull request #4: GEODE-6086: Looking for the output files in the correct location

Posted by "WireBaron (GitHub)" <gi...@apache.org>.

Should these directories end in "-yardstick-output"?

[ Full content available at: https://github.com/apache/geode-benchmarks/pull/4 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org

[GitHub] [geode-benchmarks] upthewaterspout closed pull request #4: GEODE-6086: Looking for the output files in the correct location

Posted by "upthewaterspout (GitHub)" <gi...@apache.org>.

[ pull request closed by upthewaterspout ]

[ Full content available at: https://github.com/apache/geode-benchmarks/pull/4 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org