Ticket #1940 (closed: wontfix)

Opened 10 years ago

Last modified 5 years ago

Hang occurs if previously used file no longer exists

Reported by: Stuart Campbell Owned by: Nick Draper
Priority: major Milestone: Release 2.2
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Martyn Gigg

Description

I noticed this while we were having some network problems at the SNS.

I had last run the algorithm LoadSNSEventNexus using the file /SNS/SEQ/2010_2_17_SCI/1/6745/NeXus/SEQ_6745_event.nxs. The directory /SNS/SEQ is a automount point for the data archive.

If I try to run this algorithm again when /SNS/SEQ is not available, MantidPlot just hangs with a blank screen.

Running through strace I get as the last line ...

stat("/SNS/SEQ/2010_2_17_SCI/1/6745/NeXus/SEQ_6745_event.nxs", 

Change History

comment:1 Changed 10 years ago by Nick Draper

  • Owner changed from Nick Draper to Stuart Campbell
  • Status changed from new to assigned

Stuart,

Could you add a bit more detail. Is this is we loose network connection while loading a file? Or is it if we lose connection after the workspace is loaded, perhaps while doing something else?

Assign it back to me once you answered.

comment:2 Changed 10 years ago by Alex Buts

(In [7895]) refs# 1977; refs #1940 CP algorithm returned to working state after refactoring. Memory management and class ownership is still in a mess.

comment:3 Changed 10 years ago by Stuart Campbell

It is if the network is lost at the point of running the algorithm the next time.

comment:4 Changed 10 years ago by Nick Draper

  • Milestone changed from Iteration 26 to Iteration 27

Bulk move of tickets to iteration 27, if your ticket is essential for Iteration 26 then move it back.

comment:5 Changed 10 years ago by Stuart Campbell

  • Owner changed from Stuart Campbell to Nick Draper

Oops, forgot to assign it back to you.

If you actually delete the file in between accesses, then it is fine. This is probably only a problem for network drives that are unstable.

comment:6 Changed 10 years ago by Nick Draper

  • Milestone changed from Iteration 27 to Iteration 28

Bulk move of tickets at the end of iteration 27

comment:7 Changed 9 years ago by Nick Draper

  • Milestone changed from Iteration 28 to Iteration 29

Bulk move of tickets at the end of iteration 28

comment:8 Changed 9 years ago by Nick Draper

  • Milestone changed from Iteration 29 to Iteration 30

Accepted and assigned tickets moved at iteration 29 code freeze

comment:9 Changed 9 years ago by Nick Draper

  • Milestone changed from Iteration 30 to Iteration 31

Bulk move of tickets to iteration 31 at the iteration 30 code freeze

comment:10 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:11 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:12 Changed 8 years ago by Nick Draper

  • Status changed from assigned to accepted

comment:13 Changed 8 years ago by Nick Draper

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

There are limits to what we should be able to handle. The file disappearing while we are loading it is going to be rare.

comment:14 Changed 8 years ago by Martyn Gigg

  • Status changed from verify to verifying
  • Tester set to Martyn Gigg

comment:15 Changed 8 years ago by Martyn Gigg

  • Status changed from verifying to closed

The problem seems to have gone away anyway.

I tried loading a file, removing the mount point then running the algorithm and it simply said that the file doesn't exist.

comment:16 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 2787

Note: See TracTickets for help on using tickets.