[
https://issues.apache.org/jira/browse/HDDS-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841489#comment-16841489
]
Eric Yang commented on HDDS-1458:
---------------------------------
{quote}Why are we removing this? We want to have all tests in the release
package up until GA.
"${ROOT}/hadoop-ozone/dist/src/main/blockade". It would be nice to have the
ability to run the blockade tests as we do today so users can use either of
mechanism to run the tests.{quote}
Blockade tests are not removed. They are moving to fault-injection-test
module to improve organization of code and follow maven build life cycle
instead of dumping everything in dist subdirectory. The release tarball can
still run blockade tests as we have in Ozone 0.4.0 release using:
{code}
cd $DIRECTORY_OF_OZONE
python -m pytest -s tests/blockade
{code}
This has been explained in [previous
comments|https://issues.apache.org/jira/browse/HDDS-1458?focusedCommentId=16831213&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16831213]
and [this
instructions|https://issues.apache.org/jira/browse/HDDS-1458?focusedCommentId=16838941&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16838941]
to perform integration-tests from maven directly to reduce manual steps.
> Create a maven profile to run fault injection tests
> ---------------------------------------------------
>
> Key: HDDS-1458
> URL: https://issues.apache.org/jira/browse/HDDS-1458
> Project: Hadoop Distributed Data Store
> Issue Type: Test
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.4.1
>
> Attachments: HDDS-1458.001.patch, HDDS-1458.002.patch,
> HDDS-1458.003.patch, HDDS-1458.004.patch, HDDS-1458.005.patch,
> HDDS-1458.006.patch, HDDS-1458.007.patch
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Some fault injection tests have been written using blockade. It would be
> nice to have ability to start docker compose and exercise the blockade test
> cases against Ozone docker containers, and generate reports. This is
> optional integration tests to catch race conditions and fault tolerance
> defects.
> We can introduce a profile with id: it (short for integration tests). This
> will launch docker compose via maven-exec-plugin and run blockade to simulate
> container failures and timeout.
> Usage command:
> {code}
> mvn clean verify -Pit
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
