You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pretty much clear from the title. We currently have no real good way to determine which tests in a package are particularly slow to compile so it would be helpful to have a readout of the time taken for each one.
This would be useful for tracking potential regressions in compilation speed in the noir compiler or when it would be sensible to split up a test into smaller components.
The text was updated successfully, but these errors were encountered:
Do we want to always show the times, or just when a flag is passed?
Also, with many tests it can be hard to spot the slowest ones, so we could list the 10 slowest at the end of the run (maybe if they take more than a threshold, for example 1 second).
Pretty much clear from the title. We currently have no real good way to determine which tests in a package are particularly slow to compile so it would be helpful to have a readout of the time taken for each one.
This would be useful for tracking potential regressions in compilation speed in the noir compiler or when it would be sensible to split up a test into smaller components.
The text was updated successfully, but these errors were encountered: