Difference between revisions of "Documentation/Nightly/Developers/FAQ/Dashboard"
From Slicer Wiki
| (4 intermediate revisions by the same user not shown) | |||
| Line 11: | Line 11: | ||
* http://download.slicer.org | * http://download.slicer.org | ||
* http://slicer.cdash.org/index.php?project=Slicer4 <small>(Click the package icon in the "Nightly-Packages" section</small> | * http://slicer.cdash.org/index.php?project=Slicer4 <small>(Click the package icon in the "Nightly-Packages" section</small> | ||
| − | |||
== How can I setup a dashboard ? == | == How can I setup a dashboard ? == | ||
| Line 17: | Line 16: | ||
See [[Documentation/{{documentation/version}}/Developers/Tutorials/DashboardSetup|dashboard setup instruction]]. | See [[Documentation/{{documentation/version}}/Developers/Tutorials/DashboardSetup|dashboard setup instruction]]. | ||
| − | == Windows: How to prevent Error reporting UI from showing up when a | + | == Windows: How to prevent "Error reporting UI" dialog from showing up when a program crash ?== |
Set registry key <tt>DontShowUI</tt> to <tt>1</tt> (see <tt>HKEY_CURRENT_USER\Software\Microsoft\Windows\Windows Error Reporting</tt>) | Set registry key <tt>DontShowUI</tt> to <tt>1</tt> (see <tt>HKEY_CURRENT_USER\Software\Microsoft\Windows\Windows Error Reporting</tt>) | ||
| − | This will prevent Error reporting UI from showing up when a tested program crash. | + | This will prevent <b>Error reporting UI</b> from showing up when a program crash. |
| + | |||
| + | == macOS: How to prevent the "application quit unexpectedly" dialog from showing up when a tested program crash ?== | ||
| + | |||
| + | <b>Option1:</b> | ||
| + | |||
| + | To prevent <i>CrashReporter dialog</i> from showing up when a program crash: | ||
| + | |||
| + | <pre> | ||
| + | defaults write com.apple.CrashReporter DialogType none | ||
| + | </pre> | ||
| + | |||
| + | <b>Option2:</b> | ||
| + | |||
| + | To prevent <i>CrashReporter dialog</i> from showing up when a program crash and instead let the problem appear as a notification instead: | ||
| + | |||
| + | <pre> | ||
| + | defaults write com.apple.CrashReporter UseUNC 1 | ||
| + | </pre> | ||
| + | |||
| + | References: | ||
| + | |||
| + | * https://apple.stackexchange.com/questions/105846/prevent-application-quit-unexpectedly-message-on-sigquit | ||
| + | |||
| + | * https://www.macissues.com/2016/04/12/using-the-os-x-crash-reporter-to-diagnose-a-program-failure/ | ||
Latest revision as of 03:18, 5 March 2018
Home < Documentation < Nightly < Developers < FAQ < Dashboard
|
For the latest Slicer documentation, visit the read-the-docs. |
Contents
Dashboard
What time the nightly dashboard starts ?
The nightly build are expected to start every day after 3am UTC (22pm EST) and should be available in the morning. If no build error occurred, the latest packages can be downloaded using on of these links:
- http://download.slicer.org
- http://slicer.cdash.org/index.php?project=Slicer4 (Click the package icon in the "Nightly-Packages" section
How can I setup a dashboard ?
See dashboard setup instruction.
Windows: How to prevent "Error reporting UI" dialog from showing up when a program crash ?
Set registry key DontShowUI to 1 (see HKEY_CURRENT_USER\Software\Microsoft\Windows\Windows Error Reporting)
This will prevent Error reporting UI from showing up when a program crash.
macOS: How to prevent the "application quit unexpectedly" dialog from showing up when a tested program crash ?
Option1:
To prevent CrashReporter dialog from showing up when a program crash:
defaults write com.apple.CrashReporter DialogType none
Option2:
To prevent CrashReporter dialog from showing up when a program crash and instead let the problem appear as a notification instead:
defaults write com.apple.CrashReporter UseUNC 1
References:
