[vepadulano]

This is a re-write of the cpp11Containers-unorderedMap test as a compiled C++ program based on gtest. Given the recent intermittent CI failures, the new test could help identify in a more fine-grained way the root cause. It is an addition rather than a substitution because there is no guarantee that the cause of the CI failure is in the test itself.

[github-actions]

Test Results

    23 files      23 suites   3d 16h 12m 32s ⏱️
 3 862 tests  3 859 ✅ 0 💤 3 ❌
78 699 runs  78 695 ✅ 1 💤 3 ❌

For more details on these failures, see this check.

Results for commit 7bab764.

♻️ This comment has been updated with latest results.

[vepadulano]

I've seen the unorderedMap macro-based test fail already a couple of times in this PR and at the same time the equivalent gtest-based test introduced by these changes was not failing. I propose we merge this extra test and see in the long-term if it fails over multiple CI runs, and if not we could just remove the macro-based one.

[pcanal]

Closing and re-opening to see if the new test is sturdier than the old one.

[pcanal]

Closing and re-opening to see if the new test is sturdier than the old one.

[pcanal]

and if not we could just remove the macro-based one.

Until proven otherwise we have to assume that the failure are indicative of a real problem that might affect users. Consequently we can not simply remove the test. However we could/should disable by default and re-open a PR that turns it back and where we can continue investigating the underlying cause.

[pcanal]

Thanks.