Critical Description
With the fixes from TS-168, the logging regressions can fail if you run the traffic_server -R 1 more than once. The first run always succeeds, but the 2nd and subsequent run can fail. What seems to happen is that the (small) log is not flushed, and the log is not created until the first flush happens. So, everything looks like it works, up until we (5s after log creation) try to read the log. The log then doesn't exist, and the regression in log_test_handler() fails (since, the file can't be open nor read).
I've tracked this down to the commit for TS-168, and also traced through the test in gdb, and as far as I can tell, the flush never happens, which means the log write never happens, and hence, the log file creation never happens either.