[LU-1401] sanity test passed but it's marked ABORT Created: 13/May/12  Updated: 31/May/12  Resolved: 31/May/12

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.3.0
Fix Version/s: None

Type: Bug Priority: Blocker
Reporter: Maloo Assignee: WC Triage
Resolution: Duplicate Votes: 0
Labels: None

Attachments: File results.yml    
Severity: 3
Rank (Obsolete): 6398

 Description   

Maloo test log shows sanity test passed, but it's marked ABORTED.

This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/2b2ebe70-9bad-11e1-a0a0-52540035b04c.

 Comments   
Comment by Mike Stok (Inactive) [ 14/May/12 ]

The YAML file uploaded to maloo by autotest. It appears to be truncated - the sanity test "stanza" should have a status: entry for the test rather than the subtest.

Comment by Mike Stok (Inactive) [ 14/May/12 ]

In maloo there is this fragment of code which deliberately sets the status to ABORTED if there is not explicit status in the test result file (in app/models/import_task.rb):

  def import_session_suites(test_sets, log_dir)
    test_sets.each do |set|
      import_log.info "Test suite #{set['name']}"

      # Test scripts don't give us a status or duration if a test suite's output
      # is cut off.  This is how we detect a test run that was cut short.
      status = set["status"]
      if status == nil
        status = ABORT_STATUS
      end
Comment by Peter Jones [ 31/May/12 ]

duplicate of LU-1450

Generated at Sat Feb 10 01:16:18 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.