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

[cli 4.2.4] Preparing for CLI release #15027

Merged
merged 1 commit into from
Oct 22, 2024
Merged

[cli 4.2.4] Preparing for CLI release #15027

merged 1 commit into from
Oct 22, 2024

Conversation

wrwg
Copy link
Contributor

@wrwg wrwg commented Oct 21, 2024

  • Updating CHANGELOG
  • Marking Move 2.1 stable and the default

Description

How Has This Been Tested?

Key Areas to Review

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

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

Copy link

trunk-io bot commented Oct 21, 2024

⏱️ 6h 21m total CI duration on this PR
Slowest 15 Jobs Cumulative Duration Recent Runs
execution-performance / single-node-performance 2h 38m 🟩🟩🟥🟥🟩 (+2 more)
execution-performance / test-target-determinator 22m 🟩🟩🟩🟩🟩 (+1 more)
test-target-determinator 19m 🟩🟩🟩🟩 (+1 more)
rust-targeted-unit-tests 18m 🟩
rust-cargo-deny 17m 🟩🟩🟩🟩 (+5 more)
check 15m 🟩🟩🟩🟩
rust-move-tests 12m 🟥🟩
check-dynamic-deps 12m 🟩🟩🟩🟩🟩 (+5 more)
fetch-last-released-docker-image-tag 10m 🟩🟩🟩🟩 (+1 more)
rust-move-tests 10m 🟩
rust-move-tests 10m 🟩
rust-move-tests 9m 🟩
rust-move-tests 9m 🟩
rust-move-tests 9m 🟩
rust-move-tests 9m 🟥

settingsfeedbackdocs ⋅ learn more about trunk.io

Copy link
Contributor Author

wrwg commented Oct 21, 2024

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

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

@rahxephon89
Copy link
Contributor

rahxephon89 commented Oct 21, 2024

Should we use language version 2.1 when specifying move-2?

/// Defaults to `1`, or `2` if `--move-2` is selected.
@wrwg @brmataptos

Copy link
Contributor

@0xmaayan 0xmaayan left a comment

Choose a reason for hiding this comment

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

LGTM

@wrwg wrwg marked this pull request as ready for review October 22, 2024 00:31
@wrwg wrwg added CICD:run-e2e-tests when this label is present github actions will run all land-blocking e2e tests from the PR CICD:run-forge-e2e-perf Run the e2e perf forge only labels Oct 22, 2024

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

@wrwg wrwg enabled auto-merge (squash) October 22, 2024 20:17

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

- Updating CHANGELOG
- Marking Move 2.1 stable and the default

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

@@ -1181,7 +1181,7 @@ pub struct MovePackageDir {
pub language_version: Option<LanguageVersion>,

/// Select bytecode, language version, and compiler to support Move 2:
/// Same as `--bytecode_version=7 --language_version=2.0 --compiler_version=2.0`
/// Same as `--bytecode_version=7 --language_version=2.1 --compiler_version=2.0`
Copy link
Contributor

Choose a reason for hiding this comment

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

In the attributes for the field language_version above, we have default_value_if("move_2", "true", "2.0"): should we change this to default_value_if("move_2", "true", "2.1")?

Copy link
Contributor

✅ Forge suite realistic_env_max_load success on eef61fa4491c0d1e6fcf663506561877f578d4e4

two traffics test: inner traffic : committed: 14206.23 txn/s, latency: 2795.46 ms, (p50: 2700 ms, p70: 2700, p90: 3000 ms, p99: 3300 ms), latency samples: 5401500
two traffics test : committed: 100.04 txn/s, latency: 1628.97 ms, (p50: 1500 ms, p70: 1500, p90: 1700 ms, p99: 11100 ms), latency samples: 1700
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.234, avg: 0.219", "QsPosToProposal: max: 1.202, avg: 1.162", "ConsensusProposalToOrdered: max: 0.319, avg: 0.294", "ConsensusOrderedToCommit: max: 0.384, avg: 0.374", "ConsensusProposalToCommit: max: 0.678, avg: 0.668"]
Max non-epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 0.84s no progress at version 2764259 (avg 0.20s) [limit 15].
Max epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 8.52s no progress at version 2764257 (avg 8.52s) [limit 15].
Test Ok

Copy link
Contributor

✅ Forge suite framework_upgrade success on b29f09f57e898d8d211c8bc3e303f6e50bba2266 ==> eef61fa4491c0d1e6fcf663506561877f578d4e4

Compatibility test results for b29f09f57e898d8d211c8bc3e303f6e50bba2266 ==> eef61fa4491c0d1e6fcf663506561877f578d4e4 (PR)
Upgrade the nodes to version: eef61fa4491c0d1e6fcf663506561877f578d4e4
framework_upgrade::framework-upgrade::full-framework-upgrade : committed: 1108.21 txn/s, submitted: 1110.20 txn/s, failed submission: 1.99 txn/s, expired: 1.99 txn/s, latency: 3515.42 ms, (p50: 2400 ms, p70: 3000, p90: 5100 ms, p99: 16900 ms), latency samples: 100200
framework_upgrade::framework-upgrade::full-framework-upgrade : committed: 1319.01 txn/s, submitted: 1320.96 txn/s, failed submission: 1.96 txn/s, expired: 1.96 txn/s, latency: 2521.55 ms, (p50: 2400 ms, p70: 2700, p90: 4000 ms, p99: 5700 ms), latency samples: 107840
5. check swarm health
Compatibility test for b29f09f57e898d8d211c8bc3e303f6e50bba2266 ==> eef61fa4491c0d1e6fcf663506561877f578d4e4 passed
Upgrade the remaining nodes to version: eef61fa4491c0d1e6fcf663506561877f578d4e4
framework_upgrade::framework-upgrade::full-framework-upgrade : committed: 1190.46 txn/s, submitted: 1192.69 txn/s, failed submission: 2.23 txn/s, expired: 2.23 txn/s, latency: 2514.54 ms, (p50: 2400 ms, p70: 2700, p90: 3900 ms, p99: 5700 ms), latency samples: 106780
Test Ok

Copy link
Contributor

✅ Forge suite compat success on b29f09f57e898d8d211c8bc3e303f6e50bba2266 ==> eef61fa4491c0d1e6fcf663506561877f578d4e4

Compatibility test results for b29f09f57e898d8d211c8bc3e303f6e50bba2266 ==> eef61fa4491c0d1e6fcf663506561877f578d4e4 (PR)
1. Check liveness of validators at old version: b29f09f57e898d8d211c8bc3e303f6e50bba2266
compatibility::simple-validator-upgrade::liveness-check : committed: 15211.32 txn/s, latency: 2218.15 ms, (p50: 1900 ms, p70: 2100, p90: 2600 ms, p99: 6600 ms), latency samples: 494000
2. Upgrading first Validator to new version: eef61fa4491c0d1e6fcf663506561877f578d4e4
compatibility::simple-validator-upgrade::single-validator-upgrading : committed: 6295.12 txn/s, latency: 4403.84 ms, (p50: 4600 ms, p70: 5200, p90: 5800 ms, p99: 6300 ms), latency samples: 119560
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 6352.35 txn/s, latency: 5065.33 ms, (p50: 5500 ms, p70: 5700, p90: 6000 ms, p99: 7000 ms), latency samples: 217080
3. Upgrading rest of first batch to new version: eef61fa4491c0d1e6fcf663506561877f578d4e4
compatibility::simple-validator-upgrade::half-validator-upgrading : committed: 6818.42 txn/s, latency: 4145.99 ms, (p50: 4800 ms, p70: 5000, p90: 5100 ms, p99: 5200 ms), latency samples: 124100
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 6408.06 txn/s, latency: 5072.50 ms, (p50: 5200 ms, p70: 5200, p90: 6600 ms, p99: 7000 ms), latency samples: 223140
4. upgrading second batch to new version: eef61fa4491c0d1e6fcf663506561877f578d4e4
compatibility::simple-validator-upgrade::rest-validator-upgrading : committed: 9125.98 txn/s, latency: 3027.60 ms, (p50: 3200 ms, p70: 3600, p90: 4300 ms, p99: 4500 ms), latency samples: 167280
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 8828.59 txn/s, latency: 3606.16 ms, (p50: 3600 ms, p70: 3800, p90: 5700 ms, p99: 6000 ms), latency samples: 294900
5. check swarm health
Compatibility test for b29f09f57e898d8d211c8bc3e303f6e50bba2266 ==> eef61fa4491c0d1e6fcf663506561877f578d4e4 passed
Test Ok

@wrwg wrwg merged commit 280e15b into main Oct 22, 2024
51 of 54 checks passed
@wrwg wrwg deleted the wrwg/cli_4.2.4 branch October 22, 2024 22:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CICD:run-e2e-tests when this label is present github actions will run all land-blocking e2e tests from the PR CICD:run-forge-e2e-perf Run the e2e perf forge only
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants