[
https://issues.apache.org/jira/browse/HDDS-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921541#comment-16921541
]
Eric Yang commented on HDDS-1554:
---------------------------------
[~arp] closer examination shows that:
{code}
mvn -T 1C clean install -DskipTests=true -Pdist -Dtar -DskipShade
-Pit,docker-build -Ddocker.image=apache/ozone:0.5.0-SNAPSHOT
{code}
This does not work because skipTests flag is set.
{code}
mvn test -Pit -Ddocker.image=apache/ozone:0.5.0-SNAPSHOT
{code}
This also doesn't work because the tests are written for integration-test
phase. By running test phase only, it does not trigger integration tests to
run.
The proper command to run, looks like any of the following examples:
{code}
mvn clean install -Pit,docker-build
mvn verify -Pit -Ddocker.image=apache/ozone:0.5.0-SNAPSHOT
{code}
Hope this clarifies the usage of maven commands for these integration tests.
If the commands are too cumbersome, we can remove "it" profile. I prefer to
avoid docker-build, or docker.image parameters. They are mandatory today
because the dist module supports three ways of using docker images. Hence it
is necessary to drive from the top level to instruct which image to use.
> Create disk tests for fault injection test
> ------------------------------------------
>
> Key: HDDS-1554
> URL: https://issues.apache.org/jira/browse/HDDS-1554
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: build
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Major
> Labels: pull-request-available
> Attachments: HDDS-1554.001.patch, HDDS-1554.002.patch,
> HDDS-1554.003.patch, HDDS-1554.004.patch, HDDS-1554.005.patch,
> HDDS-1554.006.patch, HDDS-1554.007.patch, HDDS-1554.008.patch,
> HDDS-1554.009.patch, HDDS-1554.010.patch, HDDS-1554.011.patch,
> HDDS-1554.012.patch, HDDS-1554.013.patch, HDDS-1554.014.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The current plan for fault injection disk tests are:
> # Scenario 1 - Read/Write test
> ## Run docker-compose to bring up a cluster
> ## Initialize scm and om
> ## Upload data to Ozone cluster
> ## Verify data is correct
> ## Shutdown cluster
> # Scenario 2 - Read/Only test
> ## Repeat Scenario 1
> ## Mount data disk as read only
> ## Try to write data to Ozone cluster
> ## Validate error message is correct
> ## Shutdown cluster
> # Scenario 3 - Corruption test
> ## Repeat Scenario 2
> ## Shutdown cluster
> ## Modify data disk data
> ## Restart cluster
> ## Validate error message for read from corrupted data
> ## Validate error message for write to corrupted volume
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
