Logging is broken on fresh mantid install

[Martyn Gigg]

Spotted when cleaning out a windows build configuration. The build directory was deleted and then rebuilt. When starting MantidPlot the console displays:

Trouble configuring the logging framework File not found

and logging is broken. If you try and run an algorithm you will see no output at all.

[Martyn Gigg]

It looks like this is to do with the existence of the mantid.log file. If you create an empty dummy file in your user properties directory (the build dir on windows, $HOME/.mantid on Linux) then logging works again.

[Peter Peterson]

Should have moved things from backlog into the release before working on it.

[Martyn Gigg]

Check for writability of log path more verbosely.

As commented in the code the Poco & Windows APIs are not reliable enough to check for write permissions on a directory. Refs #8080

Changeset: cd059e5acd2aaaa4aa8817ec807241d8f4eadf6a

[Martyn Gigg]

Branch: bugfix/8080_logging_broken_clean_install

Tester: The problem here was the lack of a mantid.log file when Mantid was starting. I would suggest testing before the merge and then after to see if it solves the issue.

To test first locate your mantid.log files:

• Linux/Mac - In $HOME/.mantid
• Windows - The same directory as the executable

and remove all mantid.log.* files. Now start MantidPlot and try and run an algorithm to see if the logging is behaving.

Also, check that a non-writable log directory allows Mantid to start and puts the log file in system temp.

[Alex Buts]

Merge remote-tracking branch 'origin/bugfix/8080_logging_broken_clean_install'

Full changeset: ​5ffea0b8c47fd5268fa4ac107c3430bc94ba8886

[Alex Buts]

works as described

[Stuart Campbell]

This ticket has been transferred to github issue ​8925