Attila Doroszlai created HDDS-13688:
---------------------------------------

             Summary: Recon taskstatus test pollutes test output
                 Key: HDDS-13688
                 URL: https://issues.apache.org/jira/browse/HDDS-13688
             Project: Apache Ozone
          Issue Type: Bug
          Components: test
            Reporter: Attila Doroszlai
            Assignee: Abhishek Pal


Robot test should not log to console:

{code}
hadoop-ozone/dist/src/main/smoketest/recon/recon-taskstatus.robot
43:  Log To Console          Sending CURL request to ${TRIGGER_SYNC_ENDPOINT}
48:  Log To Console          Sending CURL request to ${TASK_STATUS_ENDPOINT}
108:    Log To Console          Triggering OM DB sync for updates
109:    Log To Console          Wait for few seconds to let previous OM DB Sync 
thread to finish
{code}

because it pollutes test runner output:

{code}
Recon.Recon-Taskstatus :: Test to validate the recon task status API works ...
==============================================================================
Prepopulate Data and Trigger OM DB Sync :: Use Freon to prepopulat... Sending 
CURL request to http://recon:9888/api/v1/triggerdbsync/om
| PASS |
------------------------------------------------------------------------------
Validate Task Status After Sync :: Validate that task status is up... Sending 
CURL request to http://recon:9888/api/v1/task/status
| PASS |
------------------------------------------------------------------------------
Validate Stats for Specific Task :: Validate response for a specif... Sending 
CURL request to http://recon:9888/api/v1/task/status
| PASS |
------------------------------------------------------------------------------
Validate All Tasks Updated After Sync :: Ensure all tasks have bee... Sending 
CURL request to http://recon:9888/api/v1/task/status
| PASS |
------------------------------------------------------------------------------
Validate Sequence number is updated after sync                        
Triggering OM DB sync for updates
Wait for few seconds to let previous OM DB Sync thread to finish
Sending CURL request to http://recon:9888/api/v1/triggerdbsync/om
Sending CURL request to http://recon:9888/api/v1/task/status
| FAIL |
1509 != 1527
------------------------------------------------------------------------------
Recon.Recon-Taskstatus :: Test to validate the recon task status A... | FAIL |
5 tests, 4 passed, 1 failed
==============================================================================
Recon                                                                 | FAIL |
28 tests, 27 passed, 1 failed
{code}

Compare that to other tests:

{code}
Recon.Recon-Nssummary :: Smoke test for Recon Namespace Summary Endpoint fo...
==============================================================================
Check volume creation                                                 | PASS |
------------------------------------------------------------------------------
Check bucket creation                                                 | PASS |
------------------------------------------------------------------------------
Check keys creation                                                   | PASS |
------------------------------------------------------------------------------
Check Summary api access                                              | PASS |
------------------------------------------------------------------------------
Check Disk Usage api access                                           | PASS |
------------------------------------------------------------------------------
Check Quota Usage api access                                          | PASS |
------------------------------------------------------------------------------
Check File Size Distribution api access                               | PASS |
------------------------------------------------------------------------------
Check Recon Namespace Summary Root                                    | PASS |
...
{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to