Ticket #5620 (closed: fixed)

Opened 8 years ago

Last modified 5 years ago

ManagedRawFileWorkspace is broken

Reported by: Martyn Gigg Owned by: Martyn Gigg
Priority: critical Milestone: Release 2.2
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Roman Tolchenov

Description

The GEM system tests are broken on the Win32 managed machine because the ManagedRawFileWorkspace is not writing any changes to the managed file.

Change History

comment:1 Changed 8 years ago by Martyn Gigg

  • Status changed from new to accepted

comment:2 Changed 8 years ago by Martyn Gigg

Fix bug in writeData for ManagedRawFileWorkspace. Refs #5620

The call up to ManagedWorkspace was clearing the changed flag so that the blocks were not marked as changed in the ManagedRawFileWorkspace. The test did not show this as it only wrote to the workspace once which would have just used the block in the MRU.

Changeset: cc3436fc24c7680061d20a71aab909d241f8cca4

comment:3 Changed 8 years ago by Martyn Gigg

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

comment:4 Changed 8 years ago by Martyn Gigg

Fix bug in writeData for ManagedRawFileWorkspace. Refs #5620

The call up to ManagedWorkspace was clearing the changed flag so that the blocks were not marked as changed in the ManagedRawFileWorkspace. The test did not show this as it only wrote to the workspace once which would have just used the block in the MRU.

Changeset: cc3436fc24c7680061d20a71aab909d241f8cca4

comment:5 Changed 8 years ago by Roman Tolchenov

  • Status changed from verify to verifying
  • Tester set to Roman Tolchenov

comment:6 Changed 8 years ago by Roman Tolchenov

  • Status changed from verifying to closed

Ran a simple python script to assign and read back X and Y values.

comment:7 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​6466

Note: See TracTickets for help on using tickets.