Author db3l
Recipients LorenzMende, ammar2, db3l, eryksun, heckad, miss-islington, paul.moore, skoslowski, steve.dower, tim.golden, vstinner, zach.ware
Date 2019-10-02.22:14:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1570054459.13.0.0669928774781.issue36670@roundup.psfhosted.org>
In-reply-to
Content
I've confirmed the partial read with some local modifications, and the failures are always split between time stamp and value:

Warning -- Failed to parse typeperf output: '"10/02/2019 17:42:26.229"'
0.0
Warning -- Missing first field: ,"0.000000"
0.0

Adding multiple variables to the typeperf command can vary the split position, but I've only seen it at a variable boundary (starting with the comma).  So I'm guessing with the current implementation the above is probably the only point where the I/Os can be interleaved.

Also, CRLF seems to only appear at the start of each read, never at the end.  You can see that behavior interactively too where the cursor waits at the end of the line between samples.  So changes to wait for a complete line to be read would also delay load values by one sample interval.

So I'm thinking just reverting to silently ignoring this case is probably simplest.
History
Date User Action Args
2019-10-02 22:14:19db3lsetrecipients: + db3l, paul.moore, vstinner, tim.golden, zach.ware, eryksun, steve.dower, ammar2, miss-islington, LorenzMende, skoslowski, heckad
2019-10-02 22:14:19db3lsetmessageid: <1570054459.13.0.0669928774781.issue36670@roundup.psfhosted.org>
2019-10-02 22:14:19db3llinkissue36670 messages
2019-10-02 22:14:19db3lcreate