public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Quentin Barnes <qbarnes@urbana.css.mot.com>
To: David Smith <dsmith@redhat.com>
Cc: systemtap@sources.redhat.com
Subject: Re: ARM port of testsuite and general testsuite fixes
Date: Wed, 06 Jun 2007 21:35:00 -0000	[thread overview]
Message-ID: <20070606213541.GG20115@urbana.css.mot.com> (raw)
In-Reply-To: <466720A2.4070709@redhat.com>

>Well, you've improved things, but you're still missing the "Pass 4" 
>output line.

That's because of another bug in the expect script.  (I've fixed a
dozen of these bugs now so I'm rather disappointed with myself that
I missed this one until now.)

Patched attached.  With the patch, systemtap.base/cache.exp passes
all 18 tests just fine now.  I had to bump the timeout up too.
I added a "timeout" condition to be complete.


As an aside, any reason that spaces are escaped in these regular
expressions?  I didn't change it in this patch, but why are the
regular expressions written like this:
  -re {^Pass\ [1234]:[^\r]*\ in\ [^\r]*\ ms\.\r\n} {exp_continue}
  -re {^Pass\ [34]: using cached [^\r\n]+\r\n} {incr cached 1; exp_continue}

And not like this?:
  -re {^Pass [1234]:[^\r]* in [^\r]* ms\.\r\n} {exp_continue}
  -re {^Pass [34]: using cached [^\r\n]+\r\n}  {incr cached 1; exp_continue}
 
Quentin


Index: systemtap.base/cache.exp
===================================================================
--- systemtap.base/cache.exp	(revision 211)
+++ systemtap.base/cache.exp	(working copy)
@@ -27,12 +27,14 @@
     set cached 0
     set compile_errors 0
     expect {
-	-re {^Pass\ [1234]:[^\r]*\ in\ .*\ ms\.\r\n} {exp_continue}
+	-timeout 90
+	-re {^Pass\ [1234]:[^\r]*\ in\ [^\r]*\ ms\.\r\n} {exp_continue}
 	-re {^Pass\ [34]: using cached [^\r\n]+\r\n} {incr cached 1; exp_continue}
         # pass-4 output
 	-re {^/[^\r\n]+\.ko\r\n} {exp_continue}
 	-re "compilation failed" {incr compile_errors 1; exp_continue}
 	-re "semantic error:" {incr compile_errors 1; exp_continue}
+	timeout { fail "$test (timeout)" }
     }
     catch close
     wait

  reply	other threads:[~2007-06-06 21:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06  0:36 Quentin Barnes
2007-06-06 16:02 ` David Smith
2007-06-06 17:11   ` Quentin Barnes
2007-06-06 18:22     ` David Smith
2007-06-06 18:39       ` Martin Hunt
2007-06-06 19:25       ` Quentin Barnes
2007-06-06 19:51         ` David Smith
2007-06-06 20:00           ` Quentin Barnes
2007-06-06 20:07             ` David Smith
2007-06-06 20:39               ` Quentin Barnes
2007-06-06 21:01                 ` David Smith
2007-06-06 21:35                   ` Quentin Barnes [this message]
2007-06-06 21:51                     ` David Smith
2007-06-06 23:10                       ` Roland McGrath
2007-06-06 23:44                         ` Quentin Barnes
2007-06-07  1:05                           ` Roland McGrath
2007-06-08 16:27 ` Quentin Barnes

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=20070606213541.GG20115@urbana.css.mot.com \
    --to=qbarnes@urbana.css.mot.com \
    --cc=dsmith@redhat.com \
    --cc=systemtap@sources.redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).