-
Notifications
You must be signed in to change notification settings - Fork 2
/
rplt.txt
31 lines (23 loc) · 1.32 KB
/
rplt.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
rp-locatetest passes all the ruby files it can find on the system (using
the unix command locate) to bin/redparse --vsparsetree. In other words,
it's comparing the output of RedParse (when cvt'd to a ParseTree-style
tree) to the actual output of ParseTree.
I usually run it like this:
nice ruby test/rp-locatetest.rb >test.log 2>&1 &
That runs rp-locatetest at low priority, in the background, saving
stdout and stderr to test.log.
You can then trawl through test.log, looking for lines that don't start
with 'no differences in '. (Other than the page of warnings in the
beginning, which is repeated every so often.) Or, you can look for
non-commented lines in the file 'problemfiles'. (Which is just a list of
files that caused failures in rp-locatetest.)
Ok, this is more complicated than it ought to be. Sorry.
rp-locatetest takes a LONG time to run, and hogs the cpu at 100%. That's
why I was using nice. So, make sure it's ok to do that on whatever
server you run it on. I always get impatient and kill it after some
hours or days. On a subsequent run it'll pick up again where it left
off.
Right now, about 0.5% of my ruby files cause problems for rp-locatetest.
Most of those failures correspond to known problems (the file is listed
at the end of the README and/or there's a case in test_redparse.rb for
that failure).