Ticket #1604 (closed: fixed)

Opened 10 years ago

Last modified 5 years ago

Prevent the LoadDAE unit test reporting a failure if run outside RAL

Reported by: Russell Taylor Owned by: Russell Taylor
Priority: major Milestone: Iteration 25
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Janik Zikovsky

Description


Change History

comment:1 Changed 10 years ago by Russell Taylor

  • Status changed from new to accepted

comment:2 Changed 10 years ago by Russell Taylor

(In [6103]) Try and make LoadDAETest pass when outside of RAL (by not actually executing the algorithm). Re #1604

comment:3 Changed 10 years ago by Russell Taylor

(In [6104]) Fix test on Windows (?????). Re #1604.

comment:4 Changed 10 years ago by Russell Taylor

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

This test now passes on a machine that's not at RAL. I've tested that it's definitely running the full test on the Mac buildserver and the algorithm log on the linux buildserver shows that it's running it there too. The tester should check that the Windows buildservers are running the full test (i.e. executing the algorithm - can tell by examining the log file - called Test.log, I think).

comment:5 Changed 10 years ago by Russell Taylor

I've also checked the log on the Windows buildserver (ndw714) and the algorithm is running there.

comment:6 Changed 10 years ago by Janik Zikovsky

  • Status changed from verify to verifying
  • Component set to Mantid
  • Tester set to Janik Zikovsky

comment:7 Changed 10 years ago by Janik Zikovsky

  • Status changed from verifying to closed

I'm not at RAL, and the test successfully passes (by not doing anything) on my end. Pass!

comment:8 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​2451

Note: See TracTickets for help on using tickets.