-
Notifications
You must be signed in to change notification settings - Fork 411
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
Try to fix unstable unittests. #8344
Conversation
/run-unit-test |
/run-unit-test |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JaySon-Huang, Lloyd-Pottiger The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
/run-all-tests |
/run-integration-test |
1 similar comment
/run-integration-test |
cherry-pick to release-7.5 in #8363 |
cherry-pick to release-7.1 in #8346 |
What problem does this PR solve?
Issue Number: ref #6233
Problem Summary:
Unittests TestDateTimeDayMonthYear.dayMonthYearTest is unstable, due to "std::exception. Code: 1001, type: std::__1::system_error, e.what() = random_device failed to open /dev/urandom: Operation not permitted".
What is changed and how it works?
std::random_device
withstd::chrono::system_clock
here to avoid exceptions like 'random_device failed to open /dev/urandom: Operation not permitted'.Check List
Tests
Side effects
Documentation
Release note