Apparently when the strings are created, the `'\n'` is converted to the
platform's natural new line indicator, which is CR+LF on Windows. But
upon reading back with `sscanf`, the CRs caused a matching failure.
int count1, count2;
ASSERT_EQ(
6, sscanf(ss.GetData(),
- "%lf sec (total: %lfs; child: %lfs; count: %d) for CAT1%*[\n ]"
+ "%lf sec (total: %lfs; child: %lfs; count: %d) for CAT1%*[\n\r ]"
"%lf sec (total: %*fs; child: %*fs; count: %d) for CAT2",
&seconds1, &total1, &child1, &count1, &seconds2, &count2))
<< "String: " << ss.GetData();