chore: regression test #7195 #7233
Conversation
… test of expected trace when stepping through test that was failing in #7195
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'Test Suite Duration'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.
| Benchmark suite | Current: 3e80dd5 | Previous: d5d6cb7 | Ratio |
|---|---|---|---|
noir-lang_noir_string_search_ |
1 s |
0 s |
+∞ |
noir-lang_noir_bigcurve_ |
331 s |
275 s |
1.20 |
This comment was automatically generated by workflow using github-action-benchmark.
CC: @TomAFrench
There was a problem hiding this comment.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'Execution Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.
| Benchmark suite | Current: b19100f | Previous: 6d319af | Ratio |
|---|---|---|---|
global_var_regression_entry_points |
0.009 s |
0.007 s |
1.29 |
This comment was automatically generated by workflow using github-action-benchmark.
CC: @TomAFrench
|
Haven't looked at this in depth but we'll also want to make some brillig calls to make sure that we stitch the ACIR and brillig callstacks together properly. |
…ger-indicated lines
Description
Problem*
Resolves #7207
Summary*
Additional Context
Documentation*
Check one:
PR Checklist*
cargo fmton default settings.