Skip to content
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

fix: noir test incorrect reporting #4925

Merged
merged 4 commits into from
Mar 4, 2024
Merged

Conversation

Maddiaa0
Copy link
Member

@Maddiaa0 Maddiaa0 commented Mar 4, 2024

fixes noir's incorrect test reporting

fixes: #4912

Copy link
Member Author

Maddiaa0 commented Mar 4, 2024

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Maddiaa0 and the rest of your teammates on Graphite Graphite

@@ -116,10 +116,10 @@ pub(crate) fn run(
};
}

if test_report.iter().any(|(_, status)| !matches!(status, TestStatus::Fail { .. })) {
Copy link
Member Author

@Maddiaa0 Maddiaa0 Mar 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Previously if any tests passed it would report a pass status code

@kevaundray kevaundray requested a review from TomAFrench March 4, 2024 17:25
Copy link
Contributor

@vezenovm vezenovm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add a regression to test_programs/noir_test_failure

noir/noir-repo/tooling/nargo/src/ops/test.rs Outdated Show resolved Hide resolved
@Maddiaa0 Maddiaa0 marked this pull request as ready for review March 4, 2024 17:53
@Maddiaa0 Maddiaa0 enabled auto-merge (squash) March 4, 2024 17:53
@Maddiaa0 Maddiaa0 merged commit d98db3a into master Mar 4, 2024
72 of 73 checks passed
@Maddiaa0 Maddiaa0 deleted the md/03-04-noir-test-fail branch March 4, 2024 18:32
@AztecBot
Copy link
Collaborator

AztecBot commented Mar 4, 2024

Benchmark results

No metrics with a significant change found.

Detailed results

All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.

This benchmark source data is available in JSON format on S3 here.

Values are compared against data from master at commit cd1ca2e1 and shown if the difference exceeds 1%.

L2 block published to L1

Each column represents the number of txs on an L2 block published to L1.

Metric 8 txs 32 txs 64 txs
l1_rollup_calldata_size_in_bytes 5,700 18,884 36,452
l1_rollup_calldata_gas 66,156 239,048 469,808
l1_rollup_execution_gas 194,104 500,354 909,066
l2_block_processing_time_in_ms 1,197 4,522 8,978
note_successful_decrypting_time_in_ms 202 542 (+1%) 996 (+1%)
note_trial_decrypting_time_in_ms 9.86 (+31%) 65.9 (+11%) 131 (+5%)
l2_block_building_time_in_ms 16,139 (+1%) 63,586 127,197 (-1%)
l2_block_rollup_simulation_time_in_ms 12,144 48,472 (+1%) 96,911 (-1%)
l2_block_public_tx_process_time_in_ms 3,895 (+3%) 15,040 (-3%) 30,112

L2 chain processing

Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric 5 blocks 10 blocks
node_history_sync_time_in_ms 14,085 (-1%) 27,035 (+1%)
note_history_successful_decrypting_time_in_ms 1,231 (-3%) 2,398 (-2%)
note_history_trial_decrypting_time_in_ms 84.7 (-15%) 152 (-10%)
node_database_size_in_bytes 18,763,856 35,270,736
pxe_database_size_in_bytes 29,923 59,478

Circuits stats

Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit circuit_simulation_time_in_ms circuit_input_size_in_bytes circuit_output_size_in_bytes
private-kernel-init 247 44,736 28,001
private-kernel-ordering 177 (-1%) 52,625 14,627
base-rollup 1,286 (-1%) 177,932 933
root-rollup 70.1 (-1%) 4,192 825
private-kernel-inner 313 73,715 28,001
public-kernel-app-logic 192 32,254 25,379
merge-rollup 5.74 2,712 933

Tree insertion stats

The duration to insert a fixed batch of leaves into each tree type.

Metric 1 leaves 2 leaves 8 leaves 16 leaves 32 leaves 64 leaves 128 leaves 512 leaves 1024 leaves 2048 leaves 4096 leaves
batch_insert_into_append_only_tree_16_depth_ms 9.89 10.5 12.5 (-8%) 16.3 22.1 (+1%) 35.4 N/A N/A N/A N/A N/A
batch_insert_into_append_only_tree_16_depth_hash_count 16.9 17.5 23.0 31.6 47.0 79.0 N/A N/A N/A N/A N/A
batch_insert_into_append_only_tree_16_depth_hash_ms 0.574 0.583 0.531 (-8%) 0.502 (+1%) 0.463 (+1%) 0.440 N/A N/A N/A N/A N/A
batch_insert_into_append_only_tree_32_depth_ms N/A N/A N/A N/A N/A 47.1 (+3%) 72.1 (-1%) 230 443 (-1%) 866 1,723
batch_insert_into_append_only_tree_32_depth_hash_count N/A N/A N/A N/A N/A 96.0 159 543 1,055 2,079 4,127
batch_insert_into_append_only_tree_32_depth_hash_ms N/A N/A N/A N/A N/A 0.484 (+3%) 0.445 0.420 0.415 0.413 0.413
batch_insert_into_indexed_tree_20_depth_ms N/A N/A N/A N/A N/A 53.8 107 (-1%) 334 (-1%) 658 (-1%) 1,313 2,606
batch_insert_into_indexed_tree_20_depth_hash_count N/A N/A N/A N/A N/A 104 207 691 1,363 2,707 5,395
batch_insert_into_indexed_tree_20_depth_hash_ms N/A N/A N/A N/A N/A 0.479 0.482 (-1%) 0.455 (-1%) 0.453 (-1%) 0.456 0.452
batch_insert_into_indexed_tree_40_depth_ms N/A N/A N/A N/A 61.1 (-1%) N/A N/A N/A N/A N/A N/A
batch_insert_into_indexed_tree_40_depth_hash_count N/A N/A N/A N/A 109 N/A N/A N/A N/A N/A N/A
batch_insert_into_indexed_tree_40_depth_hash_ms N/A N/A N/A N/A 0.534 N/A N/A N/A N/A N/A N/A

Miscellaneous

Transaction sizes based on how many contracts are deployed in the tx.

Metric 0 deployed contracts
tx_size_in_bytes 19,179

Transaction processing duration by data writes.

Metric 0 new note hashes 1 new note hashes
tx_pxe_processing_time_ms 2,601 1,349
Metric 0 public data writes 1 public data writes
tx_sequencer_processing_time_ms 0.0293 (-10%) 468

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

investigate: test failure, ci pass?
4 participants