I don't think anything needs to be done, a malformed timestamp only causes that line to be parsed badly. I was wondering if this behavior was intentional, now that I see it was, I'm happy to leave this as an FYI for anybody else being lazy with their test case generation.