Skip to content

Commit 948e885

Browse files
committed
GH-178 - Fixed wording of the Perform Calibration message
1 parent 6616c5f commit 948e885

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

visualvm/libs.profiler/lib.profiler/src/org/graalvm/visualvm/lib/jfluid/Bundle.properties

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ ProfilerClient_ClassNotFoundMsg=Could not find class {0} on the class path.\nIns
4848
ProfilerClient_OutOfMemoryMsg=Too much data collected - the profiler ran out of memory.\nCollected profiling data has been deleted and profiling resumed.\nTo avoid this error please increase the -Xmx value\nin the etc/visualvm.conf file in VisualVM directory\nor lower the amount of details in profiling settings.
4949
ProfilerClient_IncorrectAgentVersionMsg=Warning\: The profiler agent you are connecting to is a different version than this profiler.\nYou may encounter errors and unexpected behavior.
5050
ProfilerClient_ErrorGettingCalibrationDataMsg=Error when retrieving saved calibration data for target JVM\:\n{0}
51-
ProfilerClient_MustCalibrateFirstMsg=Since you did not run the Profiler on this machine or target JVM before,\ndeleted the saved calibration data, or this data is corrupt, profiling will STOP now.\n\nYou have to run the calibration command for your target JVM\nbefore running the Profiler with it again.\nThe obtained calibration data will be saved and re-used\non subsequent runs, so you will not see this message anymore.\n\nTo perform the calibration, use\n\"Tools | Options | Java | Profiler | General | Manage calibration data\".\n\n
51+
ProfilerClient_MustCalibrateFirstMsg=Since you did not run the Profiler on this machine or target JVM before,\ndeleted the saved calibration data, or this data is corrupt, profiling will STOP now.\n\nYou have to run the calibration command for your target JVM\nbefore running the Profiler with it again.\nThe obtained calibration data will be saved and re-used\non subsequent runs, so you will not see this message anymore.\n\nTo perform the calibration, use\n\"Tools | Options | Profiling | Manage calibration data\".\n\n
5252
# HTML-formatted
5353
ProfilerClient_MustCalibrateFirstShortMsg=<html><b>Calibration data missing.</b><br><br>Profiling cannot be started on this JDK. Please perform<br>profiler calibration first and start profiling again.</html>
5454
# HTML-formatted

visualvm/libs.profiler/profiler/src/org/graalvm/visualvm/lib/profiler/NetBeansProfiler.java

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -153,8 +153,8 @@
153153
"NetBeansProfiler_ErrorSavingAttachSettingsMessage=Error encountered while saving attach settings: {0}",
154154
"NetBeansProfiler_CannotFindLibsMsg=Cannot find profiler libs directory",
155155
"NetBeansProfiler_EngineInitFailedMsg=Failed to initialize the Profiler engine: {0}",
156-
"NetBeansProfiler_InitialCalibrationMsg=Profiler will now perform an initial calibration of your machine and target JVM.\n\nThis calibration needs to be performed the first time you run the profiler to\nensure that timing results are accurate when profiling your application. To\nensure the calibration data is accurate, please make sure that other\napplications are not placing a noticeable load on your machine at this time.\n\nYou can run the calibration again using\n\"Tools | Options | Java | Profiler | General | Manage calibration data\"\n\nWarning: If your computer uses dynamic CPU frequency switching, please\ndisable it and do not use it when profiling.",
157-
"NetBeansProfiler_MustCalibrateFirstMsg=Profiling will STOP now because the calibration data is missing or is corrupt.\n\nIf this is the first time you are using the profiler or target JVM on this machine,\nyou first need to run the calibration for your target JVM.\nThe obtained calibration data will be saved and re-used\non subsequent runs, so you will not see this message again.\n\nTo perform calibration, use\n\"Tools | Options | Java | Profiler | General | Manage calibration data\".\n\n",
156+
"NetBeansProfiler_InitialCalibrationMsg=Profiler will now perform an initial calibration of your machine and target JVM.\n\nThis calibration needs to be performed the first time you run the profiler to\nensure that timing results are accurate when profiling your application. To\nensure the calibration data is accurate, please make sure that other\napplications are not placing a noticeable load on your machine at this time.\n\nYou can run the calibration again using\n\"Tools | Options | Profiling | Manage calibration data\"\n\nWarning: If your computer uses dynamic CPU frequency switching, please\ndisable it and do not use it when profiling.",
157+
"NetBeansProfiler_MustCalibrateFirstMsg=Profiling will STOP now because the calibration data is missing or is corrupt.\n\nIf this is the first time you are using the profiler or target JVM on this machine,\nyou first need to run the calibration for your target JVM.\nThe obtained calibration data will be saved and re-used\non subsequent runs, so you will not see this message again.\n\nTo perform calibration, use\n\"Tools | Options | Profiling | Manage calibration data\".\n\n",
158158
"NetBeansProfiler_MustCalibrateFirstShortMsg=<html><b>Calibration data missing.</b><br><br>Profiling cannot be started on this JDK. Please perform<br>profiler calibration first and start the profiling session again.</html>",
159159
"NetBeansProfiler_TerminateVMOnExitMsg=<b>The profiled application has finished execution.</b>\n Press OK to terminate the VM.",
160160
"NetBeansProfiler_TakeSnapshotOnExitMsg=<b>The profiled application has finished execution.</b>\nDo you want to take a snapshot of the collected results?",

0 commit comments

Comments
 (0)