BugFix: Random test failure when tracking compilation time #1713
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
When running the full test suite, it would randomly fail an activesupport_instrumentation test. On re-running the suite several times, everything would pass.
Test:
Source:
The Problem:
The test would fail roughly once in every 30 runs , always with a :time_to_execute of 0:
The Cause
The cause, was that "factory_bot.compile_factory" instrumentation triggered twice, not just once.
The :configuration compilation time, which can indeed be 0, is the last one triggered, so that's the elapsed time recorded by :time_to_execute.
The Solution
By changing :time_to_execute to a hash, and recording the individual compilations, we can check just the :user compilation time with
time_to_execute[:user]
.