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

nextest smoke-test profile #12922

Merged
merged 1 commit into from
Apr 18, 2024
Merged

Conversation

brianolson
Copy link
Contributor

Description

Add nextest profile for smoke-test with 30 minute timeout for long tests.

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
  • Other (specify)

How Has This Been Tested?

Ran locally, will need to pass in GHA too

Key Areas to Review

Is this the setting we want?

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

@brianolson brianolson requested review from a team as code owners April 17, 2024 21:10
Copy link

trunk-io bot commented Apr 17, 2024

@brianolson brianolson enabled auto-merge (squash) April 18, 2024 16:50

This comment has been minimized.

This comment has been minimized.

Copy link
Contributor

✅ Forge suite realistic_env_max_load success on cb54a7d5efc52b1007d3830f3b2d3111f5c516eb

two traffics test: inner traffic : committed: 8017 txn/s, latency: 4894 ms, (p50: 4500 ms, p90: 5700 ms, p99: 10500 ms), latency samples: 3463740
two traffics test : committed: 100 txn/s, latency: 1940 ms, (p50: 1900 ms, p90: 2200 ms, p99: 5000 ms), latency samples: 1720
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.211, avg: 0.203", "QsPosToProposal: max: 0.311, avg: 0.227", "ConsensusProposalToOrdered: max: 0.465, avg: 0.425", "ConsensusOrderedToCommit: max: 0.409, avg: 0.370", "ConsensusProposalToCommit: max: 0.851, avg: 0.796"]
Max round gap was 1 [limit 4] at version 1510565. Max no progress secs was 4.23835 [limit 15] at version 1510565.
Test Ok

Copy link
Contributor

✅ Forge suite compat success on aptos-node-v1.10.1 ==> cb54a7d5efc52b1007d3830f3b2d3111f5c516eb

Compatibility test results for aptos-node-v1.10.1 ==> cb54a7d5efc52b1007d3830f3b2d3111f5c516eb (PR)
1. Check liveness of validators at old version: aptos-node-v1.10.1
compatibility::simple-validator-upgrade::liveness-check : committed: 6674 txn/s, latency: 4964 ms, (p50: 4800 ms, p90: 8400 ms, p99: 9900 ms), latency samples: 233620
2. Upgrading first Validator to new version: cb54a7d5efc52b1007d3830f3b2d3111f5c516eb
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 1707 txn/s, latency: 17005 ms, (p50: 18700 ms, p90: 24400 ms, p99: 24700 ms), latency samples: 92180
3. Upgrading rest of first batch to new version: cb54a7d5efc52b1007d3830f3b2d3111f5c516eb
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 1534 txn/s, latency: 18591 ms, (p50: 17700 ms, p90: 28700 ms, p99: 29200 ms), latency samples: 82860
4. upgrading second batch to new version: cb54a7d5efc52b1007d3830f3b2d3111f5c516eb
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 3315 txn/s, latency: 9377 ms, (p50: 9800 ms, p90: 12600 ms, p99: 12900 ms), latency samples: 142560
5. check swarm health
Compatibility test for aptos-node-v1.10.1 ==> cb54a7d5efc52b1007d3830f3b2d3111f5c516eb passed
Test Ok

@brianolson brianolson merged commit 7fbdedc into aptos-labs:main Apr 18, 2024
84 checks passed
@brianolson brianolson deleted the nextest-smoke-test branch April 18, 2024 17:31
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.

3 participants