Version : %I-version='06.42-0626-23022024'
TestData: test.1
In most cases the output is as expected, io started and completed in one relative second interval is output in that interval. But there are cases where it fails. In the following, relative second 00:24 has no io present -- the next event after 23.* events is at second 25.*. Here we see the trailing io from 23.* being incorrectly displayed in the 25.* time interval.
In the example below, we see four io started and completed within the 23.* second interval are incorrectly output in the 25.* interval.
Find and fix this bug so all 23.* events are output in the 23.* interval and count towards its summary information. This is shown in the test.1 data.
Version : %I-version='06.42-0626-23022024' TestData: test.1
In most cases the output is as expected, io started and completed in one relative second interval is output in that interval. But there are cases where it fails. In the following, relative second 00:24 has no io present -- the next event after 23.* events is at second 25.*. Here we see the trailing io from 23.* being incorrectly displayed in the 25.* time interval.
In the example below, we see four io started and completed within the 23.* second interval are incorrectly output in the 25.* interval.
Find and fix this bug so all 23.* events are output in the 23.* interval and count towards its summary information. This is shown in the test.1 data.