Ticket #7446 (assigned)

Opened 7 years ago

Last modified 5 years ago

Improve error reporting from algorithms in multithreaded loops

Reported by: Martyn Gigg Owned by: Martyn Gigg
Priority: major Milestone: Release 3.6
Component: Framework Keywords: Maintenance
Cc: Blocked By:
Blocking: Tester:

Description (last modified by Nick Draper) (diff)

#7325 & #7400 raised the issue that error messages thrown from multi-threaded loops can be misleading. They always end with something like: 

PeaksInRegion-[Error] PeaksInRegion: error (see log)

where PeaksInRegion is the algorithm name.

The problem is you are generally looking at the log reading that message and there is no more information anywhere. We should try and improve the error reporting from OMP loops by maybe storing the last exception thrown and rethrowing it or at least store the message and remove the parts about seeing the log.

Change History

comment:1 Changed 7 years ago by Nick Draper

  • Owner set to Martyn Gigg
  • Status changed from new to assigned
  • Description modified (diff)

comment:2 Changed 7 years ago by Nick Draper

  • Status changed from assigned to new

comment:3 Changed 7 years ago by Nick Draper

  • Milestone changed from Release 2.7 to Backlog

comment:4 Changed 7 years ago by Nick Draper

  • Status changed from new to assigned

Bulk move to assigned at the introduction of the triage step

comment:5 Changed 5 years ago by Martyn Gigg

  • Milestone changed from Backlog to Release 3.6

comment:6 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​8292

Note: See TracTickets for help on using tickets.