All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Ian Jackson <ian.jackson@eu.citrix.com>
Subject: [OSSTEST PATCH 5/6] timing traces: Executive: Provide processing timestamp facilities
Date: Mon, 10 Aug 2020 12:20:46 +0100	[thread overview]
Message-ID: <20200810112047.30285-5-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <20200810112047.30285-1-ian.jackson@eu.citrix.com>

Nothing uses these yet.

Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
---
 Osstest/Executive.pm | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/Osstest/Executive.pm b/Osstest/Executive.pm
index c46a979d..1e94b282 100644
--- a/Osstest/Executive.pm
+++ b/Osstest/Executive.pm
@@ -51,6 +51,7 @@ BEGIN {
                       report_run_getinfo report_altcolour
                       report_altchangecolour opendb_tests
                       report_blessingscond report_find_push_age_info
+		      log_stderr_timestamped
                       tcpconnect_queuedaemon plan_search
                       manual_allocation_base_jobinfo
                       alloc_resources alloc_resources_rollback_begin_work
@@ -293,11 +294,23 @@ sub restrictflight_arg ($) {
         $restrictflight_cond .= " AND flights.flight != $_"
 	    foreach split /,/, $1;
 	return 1;
+    } elsif ($arg =~ m/^--report-processing-start-time$/) {
+	# This functionality is wanted by all the callers of
+	# restrictflight_arg and is here for convenience, rather than
+	# out of principle.
+	log_stderr_timestamped("starting...");
+	return 1;
     } else {
 	return 0;
     }
 }
 
+sub log_stderr_timestamped ($) {
+    my $us = $0;
+    $us =~ s{.*/}{};
+    print STDERR (show_abs_time time)." $us: @_\n";
+}
+
 sub restrictflight_cond () {
     return "($restrictflight_cond)";
 }
-- 
2.20.1



  parent reply	other threads:[~2020-08-10 11:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 11:20 [OSSTEST PATCH 1/6] cr-publish-flight-logs: Make a proper option parser Ian Jackson
2020-08-10 11:20 ` [OSSTEST PATCH 2/6] timing traces: cr-publish-flight-logs: Report more progress Ian Jackson
2020-08-10 11:20 ` [OSSTEST PATCH 3/6] timing traces: cr-daily-branch: Add more calls to date >&2 Ian Jackson
2020-08-10 11:20 ` [OSSTEST PATCH 4/6] timing traces: sg-check-tested: Add prints of (show_abs_time time) Ian Jackson
2020-08-10 11:20 ` Ian Jackson [this message]
2020-08-10 11:20 ` [OSSTEST PATCH 6/6] timing traces: cri-args-hostlists: Add some timestamps Ian Jackson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200810112047.30285-5-ian.jackson@eu.citrix.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.