-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test failure in bdlmt_eventscheduler.t #288
Comments
internal tracking 170729958 |
Hi, I haven't been able to reproduce this yet. May I know what build configuration you are using? |
The UFID is set to zhl6k25qlxsb60m5z4342n1jn17pw7-bloomberg-bde-3.110.0.3.drv.gz Hardware is an AWS r6i.xlarge with 4 vCPU running Amazon Linux 2. I have now seen errors on case 4 (as above) and case 2. Running the test executable directly so as to capture the verbose output (and ignoring successful results; the failures are highly intermittent):
|
I think I know the cause of the test failure you're seeing on case 4. However, I can't reproduce the test failure you reported on case 2. One theory is that it's related to the fact that the test driver computes Can you add the following at the beginning of if constexpr (std::is_same<CLOCK, std::chrono::system_clock>::value) {
static_assert(std::is_same<typename CLOCK::period, std::nano>::value);
const Tp adjustedStartTime = std::chrono::ceil<std::chrono::microseconds>(d_startTime);
if (veryVerbose) {
cout << "adjusting d_startTime from " << d_startTime.time_since_epoch().count() << " to " << adjustedStartTime.time_since_epoch().count() << '\n';
}
d_startTime = adjustedStartTime;
} |
bde 3.110.0.3
bde-tools 3.110.0.0
This failure is very intermittent. Only the output from the failed execution is copied below.
The text was updated successfully, but these errors were encountered: