failing test on master

Robert O'Callahan robert at
Tue Aug 9 20:04:30 UTC 2016

On Wed, Aug 10, 2016 at 12:59 AM, Ted Mielczarek <ted at> wrote:

> On Mon, Aug 8, 2016, at 11:39 PM, Robert O'Callahan wrote:
> OK I think I see the problem, though I don't understand it.
> has
> TARGET_EVENT=$(grep 'thread 2 launched ' record.out | awk '{print
> substr($3,0,3)}')
> echo Targeting recorded pid $TARGET_PID at event $TARGET_EVENT ...
> Your test output says
> Targeting recorded pid 29313 at event 47 ...
> But record.out contains
> [rr 29313 473]thread 2 launched with data 0x1bc7040
> So it looks like we're only using the first two characters of the third
> token to get the event number, and getting 47 when we should get 473.
> I don't know awk at all, but that expression sure looks like it should be
> getting the first three characters of the token :-(.
> Maybe you can re-run that grep/awk expression from the command line and
> determine why it's computing 47 instead of 473?
> Is there a reason the test driver scripts are all written in shell instead
> of something like Python? Sure seems like that'd make some things easier.

I don't know. The tests are mostly about spawning command-line-driven
processes so that probably had something to do with it.

lbir ye,ea yer.tnietoehr  rdn rdsme,anea lurpr  edna e hnysnenh hhe uresyf
selthor  stor  edna  siewaoeodm  or v sstvr  esBa  kbvted,t
o l euetiuruewFa  kbn e hnystoivateweh uresyf tulsa rehr  rdm  or rnea
.a war hsrer holsa rodvted,t  nenh hneireseoouot.tniesiewaoeivatewt sstvr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the rr-dev mailing list