[
https://issues.apache.org/jira/browse/HDDS-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861089#comment-16861089
]
Elek, Marton commented on HDDS-1554:
------------------------------------
bq. Yeah, if the user knows where to look. Robot plugin shows the link on the
navigation of the build, which is a much nicer way to access the html report
than digging into aggregated artifact link to find the log file.
Sorry, I misunderstood. Until now you mentioned the problem about " Color
coding in test summary report". This is a different problem and also can be
solved:
https://wiki.jenkins.io/display/JENKINS/HTML+Publisher+Plugin
2. HDDS-1583 can be catched by robot framework tests imho. It's not about the
exception it's about the environment (but I may be wrong)
3. My current problem is that I have only this patch as information and you may
have more detailed plan or vision in your mind. (You can help me with sharing
more details about the future plans). This patch executes very simple ozone
shell commands and very high level FileInputStream operations. I think both can
be tested with existing robot tests + miniozone tests with less problem (for
example you can forget your volume permission problem). But I have no problem
to maintain multiple type of tests IF the complexity is not increased or if
there are additional benefits to increase the complexity.
> 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
> Attachments: HDDS-1554.001.patch, HDDS-1554.002.patch,
> HDDS-1554.003.patch, HDDS-1554.004.patch
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
