Ticket #10155 (closed: fixed)

Opened 6 years ago

Last modified 5 years ago

Crash on startup if default facility is not found in facilities.xml

Reported by: Nick Draper Owned by: Nick Draper
Priority: major Milestone: Release 3.3
Component: Framework Keywords:
Cc: Blocked By:
Blocking: Tester: Dan Nixon

Description

If a facility name changes, then any users with the old name as their default facility will be unable to start mantid as it has an uncaught exception on startup.

to repoduce:

  1. Select the Test-live favility as the default facility and close mantid
  2. change facilities.xml to rename the facility to something else
  3. start mantid
  4. we should just pop up the first time setup again, not crash

Change History

comment:1 Changed 6 years ago by Nick Draper

  • Status changed from new to assigned

comment:2 Changed 6 years ago by Nick Draper

  • Status changed from assigned to inprogress

re #10155 crash fixed should show 1st time setup

Changeset: 924e44cb50a8a49e997fffa719230f778aeda48f

comment:3 Changed 6 years ago by Nick Draper

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

to test: follow the steps in the description, you should now get the first time setup displayed.

comment:4 Changed 6 years ago by Dan Nixon

  • Status changed from verify to verifying
  • Tester set to Dan Nixon

comment:5 Changed 6 years ago by Dan Nixon

  • Status changed from verifying to closed

Merge remote-tracking branch 'origin/bugfix/10155_crash_if_facility_not_found'

Full changeset: ​7f79926ce7181b429752e77150ab669ff30fc2b0

comment:6 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​10997

Note: See TracTickets for help on using tickets.