Update fuzz.sh

[gedigi]

Description

Update nightly version to 2024-02-12 because of google/oss-fuzz#11626

Type of Change

• New feature
• Bug fix
• Breaking change
• Performance improvement
• Refactoring
• Dependency update
• Documentation update
• Tests

Which Components or Systems Does This Change Impact?

• Validator Node
• Full Node (API, Indexer, etc.)
• Move/Aptos Virtual Machine
• Aptos Framework
• Aptos CLI/SDK
• Developer Infrastructure: fuzzing infra
• Other (specify)

How Has This Been Tested?

Local oss-fuzz run

Key Areas to Review

n/a

Checklist

• I have read and followed the CONTRIBUTING doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I identified and added all stakeholders and component owners affected by this change as reviewers
• I tested both happy and unhappy path of the functionality
• I have made corresponding changes to the documentation

[trunk-io]

⏱️ 59m total CI duration on this PR

Job	Cumulative Duration	Recent Runs
forge-compat-test / forge	16m	🟩
forge-e2e-test / forge	16m	🟩
rust-doc-tests	5m	🟩
test-target-determinator	5m	🟩
execution-performance / test-target-determinator	4m	🟩
check	3m	🟩
check-dynamic-deps	2m	🟩 🟩
general-lints	2m	🟩
rust-cargo-deny	2m	🟩
rust-move-tests	1m	🟩
semgrep/ci	41s	🟩 🟩
file_change_determinator	23s	🟩 🟩
file_change_determinator	15s	⬜ 🟩
file_change_determinator	13s	🟩
permission-check	12s	🟩 🟩
permission-check	11s	🟩
execution-performance / single-node-performance	10s	🟩
Backport PR	9s	🟥 🟥
permission-check	8s	🟩 🟩
forge-framework-upgrade-test / forge	8s	🟩
permission-check	7s	🟩 🟩
permission-check	6s	🟩 🟩
determine-docker-build-metadata	3s	🟩
permission-check	2s	🟩
rust-move-tests	1s	⬜

_{settings ⋅ feedback ⋅ docs ⋅ learn more about trunk.io}

[github-actions]

✅ Forge suite realistic_env_max_load success on 2c88379b0a63d57d8468e63069bd1180dc5bdce8

two traffics test: inner traffic : committed: 11774.28 txn/s, latency: 3372.95 ms, (p50: 3300 ms, p90: 3900 ms, p99: 5700 ms), latency samples: 4476900
two traffics test : committed: 100.06 txn/s, latency: 2667.02 ms, (p50: 2500 ms, p90: 2900 ms, p99: 8700 ms), latency samples: 1740
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.242, avg: 0.220", "QsPosToProposal: max: 0.805, avg: 0.636", "ConsensusProposalToOrdered: max: 0.348, avg: 0.337", "ConsensusOrderedToCommit: max: 0.636, avg: 0.607", "ConsensusProposalToCommit: max: 0.984, avg: 0.944"]
Max non-epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 1.31s no progress at version 2343616 (avg 0.24s) [limit 15].
Max epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 7.25s no progress at version 2343614 (avg 7.25s) [limit 15].
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Validator CPU Profile
• Fullnode CPU Profile
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite compat success on 1c2ee7082d6eff8c811ee25d6f5a7d00860a75d5 ==> 2c88379b0a63d57d8468e63069bd1180dc5bdce8

Compatibility test results for 1c2ee7082d6eff8c811ee25d6f5a7d00860a75d5 ==> 2c88379b0a63d57d8468e63069bd1180dc5bdce8 (PR)
1. Check liveness of validators at old version: 1c2ee7082d6eff8c811ee25d6f5a7d00860a75d5
compatibility::simple-validator-upgrade::liveness-check : committed: 7289.21 txn/s, latency: 3794.47 ms, (p50: 3000 ms, p90: 5100 ms, p99: 25700 ms), latency samples: 314100
2. Upgrading first Validator to new version: 2c88379b0a63d57d8468e63069bd1180dc5bdce8
compatibility::simple-validator-upgrade::single-validator-upgrading : committed: 6898.48 txn/s, latency: 4091.37 ms, (p50: 4600 ms, p90: 5100 ms, p99: 5300 ms), latency samples: 127800
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 6266.88 txn/s, latency: 4731.31 ms, (p50: 4800 ms, p90: 5100 ms, p99: 6700 ms), latency samples: 240420
3. Upgrading rest of first batch to new version: 2c88379b0a63d57d8468e63069bd1180dc5bdce8
compatibility::simple-validator-upgrade::half-validator-upgrading : committed: 6911.18 txn/s, latency: 3949.81 ms, (p50: 4400 ms, p90: 4800 ms, p99: 5000 ms), latency samples: 127820
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 7405.32 txn/s, latency: 4293.05 ms, (p50: 4500 ms, p90: 4800 ms, p99: 5000 ms), latency samples: 246380
4. upgrading second batch to new version: 2c88379b0a63d57d8468e63069bd1180dc5bdce8
compatibility::simple-validator-upgrade::rest-validator-upgrading : committed: 10385.58 txn/s, latency: 2663.90 ms, (p50: 2600 ms, p90: 3600 ms, p99: 3900 ms), latency samples: 195800
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 9171.22 txn/s, latency: 3338.02 ms, (p50: 2800 ms, p90: 5200 ms, p99: 6100 ms), latency samples: 321740
5. check swarm health
Compatibility test for 1c2ee7082d6eff8c811ee25d6f5a7d00860a75d5 ==> 2c88379b0a63d57d8468e63069bd1180dc5bdce8 passed
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Validator CPU Profile
• Fullnode CPU Profile
• Test runner output
• Test run is land-blocking