Ticket #4096 (closed: worksforme)

Opened 9 years ago

Last modified 5 years ago

Occasional failure of LoadTOFRawNexusTest

Reported by: Russell Taylor Owned by: Russell Taylor
Priority: major Milestone: Release 2.4
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Stuart Campbell

Description

Most recently seen on RHEL5:

Stacktrace 

Error: Expected (X[201] == 40200) up to 1e-4 (0.0001), found (0.0000 != 40200)
Error: Expected (Y[94] == 1.0) up to 1e-4 (0.0001), found (0.0000 != 1.0000)
Error: Expected (E[94] == 1.0) up to 1e-4 (0.0001), found (0.0000 != 1.0000)
Error: Expected (spec->dataY()[105] == 23.0) up to 1e-4 (0.0001), found (0.0000 != 23.0000)
Error: Expected (spec->dataE()[105] == sqrt(23.0)) up to 1e-4 (0.0001), found (0.0000 != 4.7958)

Standard Output 

In LoadTOFRawNexusTest::test_exec:
/home/mantidlog/jenkins/workspace/isis_rhel5/Code/Mantid/Framework/DataHandling/test/LoadTOFRawNexusTest.h:76: Error: Expected (X[201] == 40200) up to 1e-4 (0.0001), found (0.0000 != 40200)
/home/mantidlog/jenkins/workspace/isis_rhel5/Code/Mantid/Framework/DataHandling/test/LoadTOFRawNexusTest.h:79: Error: Expected (Y[94] == 1.0) up to 1e-4 (0.0001), found (0.0000 != 1.0000)
/home/mantidlog/jenkins/workspace/isis_rhel5/Code/Mantid/Framework/DataHandling/test/LoadTOFRawNexusTest.h:80: Error: Expected (E[94] == 1.0) up to 1e-4 (0.0001), found (0.0000 != 1.0000)
/home/mantidlog/jenkins/workspace/isis_rhel5/Code/Mantid/Framework/DataHandling/test/LoadTOFRawNexusTest.h:87: Error: Expected (spec->dataY()[105] == 23.0) up to 1e-4 (0.0001), found (0.0000 != 23.0000)
/home/mantidlog/jenkins/workspace/isis_rhel5/Code/Mantid/Framework/DataHandling/test/LoadTOFRawNexusTest.h:88: Error: Expected (spec->dataE()[105] == sqrt(23.0)) up to 1e-4 (0.0001), found (0.0000 != 4.7958)

Change History

comment:1 Changed 9 years ago by Nick Draper

  • Status changed from new to assigned
  • Owner set to Roman Tolchenov

comment:2 Changed 9 years ago by Russell Taylor

May be related to the race conditions under investigation/fixed in #4133. Probably one to just keep an eye out for for the time being - I'll add a note here if I see it fail again.

comment:3 Changed 9 years ago by Nick Draper

  • Milestone changed from Iteration 32 to Iteration 33

Moved to iteration 33 at iteration 32 code freeze

comment:4 Changed 9 years ago by Wenduo Zhou

Modify input's comment. Refs #4096.

Changeset: 014aeb7de5564142e5dde800d14b60aa98fa49bb

comment:5 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.1 to Release 2.2

Moved at end of release 2.1

comment:6 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.2 to Release 2.3

Moved at the end of release 2.2

comment:7 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.3 to Release 2.4

Moved to milestone 2.4

comment:8 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.4 to Release 2.5

Moved at the code freeze for release 2.4

comment:9 Changed 8 years ago by Russell Taylor

  • Status changed from assigned to accepted
  • Owner changed from Roman Tolchenov to Russell Taylor
  • Milestone changed from Release 2.5 to Release 2.4

comment:10 Changed 8 years ago by Russell Taylor

  • Status changed from accepted to verify
  • Resolution set to worksforme

Not seen in a long time. Seems as if the way to fix these kind of tickets is to ignore them.

comment:11 Changed 8 years ago by Stuart Campbell

  • Status changed from verify to verifying
  • Tester set to Stuart Campbell

comment:12 Changed 8 years ago by Stuart Campbell

  • Status changed from verifying to closed

comment:13 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​4943

Note: See TracTickets for help on using tickets.