profiling: use "stat" profiler to profile individual request stable
authorPierre-Yves David <pierre-yves.david@octobus.net>
Wed, 11 Sep 2024 12:03:39 +0200
branchstable
changeset 51841 102770bbf270
parent 51840 1bb71046f5e0
child 51842 3785814bc2b7
child 51869 37a079410507
profiling: use "stat" profiler to profile individual request The ls profiler no longer works for that. As the lsprof profiler is not default and not great is general, lets side step the issue for now.
tests/test-profile.t
--- a/tests/test-profile.t	Wed Sep 11 12:02:38 2024 +0200
+++ b/tests/test-profile.t	Wed Sep 11 12:03:39 2024 +0200
@@ -50,11 +50,15 @@
 
 #endif
 
-#if lsprof serve
+#if serve
 
 Profiling of HTTP requests works
 
-  $ prof \
+  $ stats_prof () {
+  >   hg --config profiling.type=stat --profile $@
+  > }
+
+  $ stats_prof \
   >   --config profiling.format=text \
   >   --config profiling.output=../profile.log \
   >  serve -d \
@@ -67,7 +71,9 @@
   $ cat ../error.log
 
 A single profile is logged because file logging doesn't append
-  $ grep CallCount ../profile.log | wc -l
+  $ grep 'Sample count:' ../profile.log | wc -l
+  \s*1 (re)
+  $ grep 'Total time:' ../profile.log | wc -l
   \s*1 (re)
 
 #endif