Inconsistent reporting of failed parses when using -reparse

[GoogleCodeExporter]

What steps will reproduce the problem?
1. checkout RELEASE_1_0 branch, changeset 1035:977a87837605  (although even in 
a version of default branch, changeset 1071:c867467ddf39 with issue 3 fixed, 
the following behavior is still observed)
2. run the following two commands from bash:
a.
echo -e "The why x w v you tee s are queue pea oh n m el que jay I age gee if e 
thee see b a.\nThe why x w v you tee s are queue pea oh n m el que jay I age 
gee if e thee see b a.\nThe why x w v you tee s are queue pea oh n m el que jay 
I age gee if e thee see b a."  | build-dist/parse -g models/eng.sm6.gr.gz -fom 
models/eng.sm6.fom.gz -beamModel models/eng.sm6.bcm.gz -O 
beamModelBias="-200,-200,-200,-200" | tail -n 1

b.
echo -e "The why x w v you tee s are queue pea oh n m el que jay I age gee if e 
thee see b a.\nThe why x w v you tee s are queue pea oh n m el que jay I age 
gee if e thee see b a.\nThe why x w v you tee s are queue pea oh n m el que jay 
I age gee if e thee see b a."  | build-dist/parse -g models/eng.sm6.gr.gz -fom 
models/eng.sm6.fom.gz -beamModel models/eng.sm6.bcm.gz -O 
beamModelBias="-200,-200,-200,-200" -reparse 5 | tail -n 1

What is the expected output? What do you see instead?
observed:
a.
INFO: numSentences=3 numFail=3 reparsedSentences=0 totalReparses=0 
totalSeconds=0.339 cpuSeconds=0.339 avgSecondsPerSent=0.113 wordsPerSec=230.089
b.
INFO: numSentences=3 numFail=0 reparsedSentences=1 totalReparses=1 
totalSeconds=0.632 cpuSeconds=0.632 avgSecondsPerSent=0.211 wordsPerSec=123.418

expected:
a. (same as above)
b. numFail + reparsedSentences should equal 3

What version of the product are you using? On what operating system?
The problem appears in default branch changeset 1071:c867467ddf39 . I'm running 
on 64 bit Linux

Please provide any additional information below.
I've also observed some behavior where sentences that *did not* fail to parse 
without the -reparse 5 option on were parsed *differently* when -reparse 5 was 
on.

Original issue reported on code.google.com by adamteic...@gmail.com on 9 Jan 2013 at 10:10

[GoogleCodeExporter]

(slight correction to the question "What version of the product are you using? 
On what operating system?": just look at the "What steps will reproduce the 
problem?" section to see what version is offending.)

Original comment by adamteic...@gmail.com on 9 Jan 2013 at 10:27

[GoogleCodeExporter]

This issue was closed by revision ae49fc2f0fc6.

Original comment by aaron.du...@gmail.com on 21 Feb 2013 at 1:34

• Changed state: Fixed