Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve error reporting from algorithms in multithreaded loops #8292

Closed
martyngigg opened this issue Jul 15, 2013 · 3 comments
Closed

Improve error reporting from algorithms in multithreaded loops #8292

martyngigg opened this issue Jul 15, 2013 · 3 comments
Labels
Framework Issues and pull requests related to components in the Framework Maintenance Unassigned issues to be addressed in the next maintenance period.
Projects

Comments

@martyngigg
Copy link
Member

This issue was originally TRAC 7446

http://trac.mantidproject.org/mantid/ticket/7325 & http://trac.mantidproject.org/mantid/ticket/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.


Keywords: Maintenance

@martyngigg
Copy link
Member Author

@NickDraper (2014-02-14T11:05:00):
Bulk move to assigned at the introduction of the triage step

@martyngigg martyngigg added Framework Issues and pull requests related to components in the Framework Maintenance Unassigned issues to be addressed in the next maintenance period. labels Jun 3, 2015
@martyngigg martyngigg self-assigned this Jun 3, 2015
@martyngigg martyngigg added this to the Release 3.6 milestone Jun 3, 2015
@martyngigg martyngigg modified the milestones: Release 3.7, Release 3.6 Nov 19, 2015
@NickDraper NickDraper modified the milestone: Release 3.7 May 20, 2016
@peterfpeterson peterfpeterson added this to To do in Maintenance Nov 20, 2018
@martyngigg martyngigg removed their assignment Jul 15, 2019
@martyngigg
Copy link
Member Author

This doesn't need to be done by me so I'm leaving it for the general maintenance pool.

@martyngigg
Copy link
Member Author

Hasn't been address and very low priority.

Maintenance automation moved this from To do to Done Oct 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues and pull requests related to components in the Framework Maintenance Unassigned issues to be addressed in the next maintenance period.
Projects
Development

No branches or pull requests

2 participants