aptos-core icon indicating copy to clipboard operation
aptos-core copied to clipboard

[storage] add storage genesis waypoint

Open areshand opened this issue 1 year ago • 1 comments

Description

add a storage genesis waypoint config to decouple from node base waypoint config

Test Plan

updated unit test

areshand avatar Dec 19 '23 17:12 areshand

⏱️ 19h 3m total CI duration on this PR
Job Cumulative Duration Recent Runs
forge-framework-upgrade-test / forge 4h 7m 🟥🟥🟥🟥🟥 (+1 more)
rust-unit-tests 3h 24m 🟩🟩🟩🟩🟩 (+3 more)
rust-smoke-tests 2h 34m 🟥🟥🟥🟥🟩
windows-build 2h 29m 🟩🟩🟩🟩🟩 (+3 more)
rust-lints 1h 4m 🟩🟩🟩🟩🟩 (+3 more)
execution-performance / single-node-performance 1h 1m 🟩🟩🟩
forge-e2e-test / forge 56m 🟩🟥🟩🟩
forge-compat-test / forge 37m 🟩🟩🟩
run-tests-main-branch 34m 🟩🟩🟩🟩🟩 (+3 more)
rust-images / rust-all 32m 🟩🟩🟩
check 30m 🟩🟩🟩🟩🟩 (+3 more)
cli-e2e-tests / run-cli-tests 29m 🟩🟩🟩
general-lints 18m 🟩🟩🟩🟩🟩 (+3 more)
check-dynamic-deps 16m 🟩🟩🟩🟩🟩 (+3 more)
semgrep/ci 3m 🟩🟩🟩🟩🟩 (+3 more)
node-api-compatibility-tests / node-api-compatibility-tests 3m 🟩🟩🟩
file_change_determinator 1m 🟩🟩🟩🟩🟩 (+3 more)
file_change_determinator 1m 🟩🟩🟩🟩🟩 (+3 more)
execution-performance / file_change_determinator 37s 🟩🟩🟩
file_change_determinator 31s 🟩🟩🟩
permission-check 26s 🟩🟩🟩🟩🟩 (+3 more)
execution-performance / parallel-execution-performance 22s 🟩🟩🟩
execution-performance / sequential-execution-performance 21s 🟩🟩🟩
permission-check 21s 🟩🟩🟩🟩🟩 (+3 more)
permission-check 20s 🟩🟩🟩🟩🟩 (+3 more)
permission-check 19s 🟩🟩🟩🟩🟩 (+3 more)
permission-check 6s 🟩🟩🟩
determine-docker-build-metadata 6s 🟩🟩🟩

settingsfeedbackdocs ⋅ learn more about trunk.io

trunk-io[bot] avatar Dec 19 '23 17:12 trunk-io[bot]

@msmouse one more look?

areshand avatar Jan 03 '24 19:01 areshand

I mean, shall we put genesis_waypoint under ExecutionConfig, where genesis_file_location resides?

msmouse avatar Jan 03 '24 19:01 msmouse

genesis_file_location

done

areshand avatar Jan 03 '24 23:01 areshand

Forge is running suite framework_upgrade on aptos-node-v1.8.3 ==> 06bb91f443367bed0f13212415d4b72cd7d59cac

github-actions[bot] avatar Jan 08 '24 18:01 github-actions[bot]

Forge is running suite realistic_env_max_load on 06bb91f443367bed0f13212415d4b72cd7d59cac

github-actions[bot] avatar Jan 08 '24 18:01 github-actions[bot]

Forge is running suite compat on aptos-node-v1.8.3 ==> 06bb91f443367bed0f13212415d4b72cd7d59cac

github-actions[bot] avatar Jan 08 '24 18:01 github-actions[bot]

:white_check_mark: Forge suite realistic_env_max_load success on 06bb91f443367bed0f13212415d4b72cd7d59cac

two traffics test: inner traffic : committed: 7533 txn/s, latency: 5159 ms, (p50: 4800 ms, p90: 6500 ms, p99: 12000 ms), latency samples: 3247040
two traffics test : committed: 100 txn/s, latency: 2313 ms, (p50: 2100 ms, p90: 2700 ms, p99: 6700 ms), latency samples: 1760
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.235, avg: 0.201", "QsPosToProposal: max: 0.169, avg: 0.154", "ConsensusProposalToOrdered: max: 0.584, avg: 0.554", "ConsensusOrderedToCommit: max: 0.521, avg: 0.490", "ConsensusProposalToCommit: max: 1.090, avg: 1.044"]
Max round gap was 1 [limit 4] at version 1656068. Max no progress secs was 4.185267 [limit 10] at version 1656068.
Test Ok

github-actions[bot] avatar Jan 08 '24 18:01 github-actions[bot]

:white_check_mark: Forge suite compat success on aptos-node-v1.8.3 ==> 06bb91f443367bed0f13212415d4b72cd7d59cac

Compatibility test results for aptos-node-v1.8.3 ==> 06bb91f443367bed0f13212415d4b72cd7d59cac (PR)
1. Check liveness of validators at old version: aptos-node-v1.8.3
compatibility::simple-validator-upgrade::liveness-check : committed: 5047 txn/s, latency: 6494 ms, (p50: 6500 ms, p90: 9600 ms, p99: 12600 ms), latency samples: 186740
2. Upgrading first Validator to new version: 06bb91f443367bed0f13212415d4b72cd7d59cac
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 1758 txn/s, latency: 16284 ms, (p50: 18900 ms, p90: 21600 ms, p99: 22700 ms), latency samples: 89700
3. Upgrading rest of first batch to new version: 06bb91f443367bed0f13212415d4b72cd7d59cac
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 1383 txn/s, latency: 20858 ms, (p50: 21400 ms, p90: 30500 ms, p99: 32000 ms), latency samples: 66400
4. upgrading second batch to new version: 06bb91f443367bed0f13212415d4b72cd7d59cac
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 3504 txn/s, latency: 8934 ms, (p50: 9600 ms, p90: 12700 ms, p99: 13500 ms), latency samples: 143700
5. check swarm health
Compatibility test for aptos-node-v1.8.3 ==> 06bb91f443367bed0f13212415d4b72cd7d59cac passed
Test Ok

github-actions[bot] avatar Jan 08 '24 18:01 github-actions[bot]

:x: Forge suite framework_upgrade failure on aptos-node-v1.8.3 ==> 06bb91f443367bed0f13212415d4b72cd7d59cac

Compatibility test results for aptos-node-v1.8.3 ==> 06bb91f443367bed0f13212415d4b72cd7d59cac (PR)
Upgrade the nodes to version: 06bb91f443367bed0f13212415d4b72cd7d59cac
framework_upgrade::framework-upgrade::full-framework-upgrade : committed: 220 txn/s, submitted: 272 txn/s, expired: 51 txn/s, latency: 4321 ms, (p50: 4800 ms, p90: 5100 ms, p99: 9600 ms), latency samples: 169870
Test Failed: Unknown error error sending request for url (http://aptos-node-2-validator.forge-framework-upgrade-pr-11420.svc:8080/v1/): error trying to connect: dns error: failed to lookup address information: Name or service not known

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: __libc_start_main
   9: <unknown>
Trailing Log Lines:
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: __libc_start_main
   9: <unknown>


Swarm logs can be found here: See fgi output for more information.
thread 'main' panicked at testsuite/forge/src/backend/k8s/swarm.rs:676:18:
called `Result::unwrap()` on an `Err` value: ApiError: namespaces "forge-framework-upgrade-pr-11420" not found: NotFound (ErrorResponse { status: "Failure", message: "namespaces \"forge-framework-upgrade-pr-11420\" not found", reason: "NotFound", code: 404 })

Caused by:
    namespaces "forge-framework-upgrade-pr-11420" not found: NotFound

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: __libc_start_main
  15: <unknown>
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Debugging output:

github-actions[bot] avatar Jan 08 '24 18:01 github-actions[bot]

Forge is running suite realistic_env_max_load on 74b00fc54b381f3c4ef02942a6000227223689b6

github-actions[bot] avatar Jan 08 '24 21:01 github-actions[bot]

Forge is running suite compat on aptos-node-v1.8.3 ==> 74b00fc54b381f3c4ef02942a6000227223689b6

github-actions[bot] avatar Jan 08 '24 21:01 github-actions[bot]

Forge is running suite framework_upgrade on aptos-node-v1.8.3 ==> 74b00fc54b381f3c4ef02942a6000227223689b6

github-actions[bot] avatar Jan 08 '24 21:01 github-actions[bot]

:white_check_mark: Forge suite compat success on aptos-node-v1.8.3 ==> 74b00fc54b381f3c4ef02942a6000227223689b6

Compatibility test results for aptos-node-v1.8.3 ==> 74b00fc54b381f3c4ef02942a6000227223689b6 (PR)
1. Check liveness of validators at old version: aptos-node-v1.8.3
compatibility::simple-validator-upgrade::liveness-check : committed: 3403 txn/s, latency: 6400 ms, (p50: 6600 ms, p90: 9300 ms, p99: 11100 ms), latency samples: 187180
2. Upgrading first Validator to new version: 74b00fc54b381f3c4ef02942a6000227223689b6
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 1848 txn/s, latency: 15594 ms, (p50: 18400 ms, p90: 22000 ms, p99: 22300 ms), latency samples: 92420
3. Upgrading rest of first batch to new version: 74b00fc54b381f3c4ef02942a6000227223689b6
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 1336 txn/s, latency: 20891 ms, (p50: 20400 ms, p90: 27700 ms, p99: 28800 ms), latency samples: 66840
4. upgrading second batch to new version: 74b00fc54b381f3c4ef02942a6000227223689b6
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 3258 txn/s, latency: 9120 ms, (p50: 9900 ms, p90: 12600 ms, p99: 14200 ms), latency samples: 143360
5. check swarm health
Compatibility test for aptos-node-v1.8.3 ==> 74b00fc54b381f3c4ef02942a6000227223689b6 passed
Test Ok

github-actions[bot] avatar Jan 08 '24 21:01 github-actions[bot]

:x: Forge suite realistic_env_max_load failure on 74b00fc54b381f3c4ef02942a6000227223689b6

two traffics test: inner traffic : committed: 6552 txn/s, latency: 5911 ms, (p50: 5700 ms, p90: 7500 ms, p99: 13200 ms), latency samples: 2830620
Test Failed: test NetworkLoadTest

Caused by:
    TPS requirement for inner traffic failed. Average TPS 6552, minimum TPS requirement 7000. Full stats: committed: 6552 txn/s, latency: 5911 ms, (p50: 5700 ms, p90: 7500 ms, p99: 13200 ms), latency samples: 2830620

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: __libc_start_main
  14: <unknown>
Trailing Log Lines:
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: __libc_start_main
  14: <unknown>


Swarm logs can be found here: See fgi output for more information.
{"level":"INFO","source":{"package":"aptos_forge","file":"testsuite/forge/src/backend/k8s/cluster_helper.rs:292"},"thread_name":"main","hostname":"forge-e2e-pr-11420-1704749777-74b00fc54b381f3c4ef02942a60002272","timestamp":"2024-01-08T21:47:05.876212Z","message":"Deleting namespace forge-e2e-pr-11420: Some(NamespaceStatus { conditions: None, phase: Some(\"Terminating\") })"}
{"level":"INFO","source":{"package":"aptos_forge","file":"testsuite/forge/src/backend/k8s/cluster_helper.rs:400"},"thread_name":"main","hostname":"forge-e2e-pr-11420-1704749777-74b00fc54b381f3c4ef02942a60002272","timestamp":"2024-01-08T21:47:05.876247Z","message":"aptos-node resources for Forge removed in namespace: forge-e2e-pr-11420"}

failures:
    CompositeNetworkTest

test result: FAILED. 0 passed; 1 failed; 0 filtered out

Failed to run tests:
Tests Failed
Error: Tests Failed

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: __libc_start_main
   7: <unknown>
Debugging output:
NAME                                   READY   STATUS      RESTARTS   AGE
aptos-node-0-fullnode-eforge25-0       1/1     Running     0          10m
aptos-node-0-validator-0               1/1     Running     0          10m
aptos-node-1-fullnode-eforge25-0       1/1     Running     0          10m
aptos-node-1-validator-0               1/1     Running     0          10m
aptos-node-2-fullnode-eforge25-0       1/1     Running     0          10m
aptos-node-2-validator-0               1/1     Running     0          10m
aptos-node-3-fullnode-eforge25-0       1/1     Running     0          10m
aptos-node-3-validator-0               1/1     Running     0          10m
aptos-node-4-fullnode-eforge25-0       1/1     Running     0          10m
aptos-node-4-validator-0               1/1     Running     0          10m
aptos-node-5-validator-0               1/1     Running     0          10m
aptos-node-6-validator-0               1/1     Running     0          10m
genesis-aptos-genesis-eforge25-x9vpj   0/1     Completed   0          10m

github-actions[bot] avatar Jan 08 '24 21:01 github-actions[bot]

:x: Forge suite framework_upgrade failure on aptos-node-v1.8.3 ==> 74b00fc54b381f3c4ef02942a6000227223689b6

Compatibility test results for aptos-node-v1.8.3 ==> 74b00fc54b381f3c4ef02942a6000227223689b6 (PR)
Upgrade the nodes to version: 74b00fc54b381f3c4ef02942a6000227223689b6
Test Failed: API error: Unknown error error sending request for url (http://aptos-node-3-validator.forge-framework-upgrade-pr-11420.svc:8080/v1/estimate_gas_price): error trying to connect: dns error: failed to lookup address information: Name or service not known

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: __libc_start_main
  15: <unknown>
Trailing Log Lines:
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: __libc_start_main
  15: <unknown>


Swarm logs can be found here: See fgi output for more information.
thread 'main' panicked at testsuite/forge/src/backend/k8s/swarm.rs:676:18:
called `Result::unwrap()` on an `Err` value: ApiError: namespaces "forge-framework-upgrade-pr-11420" not found: NotFound (ErrorResponse { status: "Failure", message: "namespaces \"forge-framework-upgrade-pr-11420\" not found", reason: "NotFound", code: 404 })

Caused by:
    namespaces "forge-framework-upgrade-pr-11420" not found: NotFound

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: __libc_start_main
  16: <unknown>
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Debugging output:

github-actions[bot] avatar Jan 08 '24 22:01 github-actions[bot]

Forge is running suite realistic_env_max_load on 74b00fc54b381f3c4ef02942a6000227223689b6

github-actions[bot] avatar Jan 09 '24 17:01 github-actions[bot]

Forge is running suite framework_upgrade on aptos-node-v1.8.3 ==> 74b00fc54b381f3c4ef02942a6000227223689b6

github-actions[bot] avatar Jan 09 '24 17:01 github-actions[bot]

:white_check_mark: Forge suite realistic_env_max_load success on 74b00fc54b381f3c4ef02942a6000227223689b6

two traffics test: inner traffic : committed: 8171 txn/s, latency: 4748 ms, (p50: 4500 ms, p90: 5700 ms, p99: 12300 ms), latency samples: 3521740
two traffics test : committed: 100 txn/s, latency: 2260 ms, (p50: 2200 ms, p90: 2400 ms, p99: 7600 ms), latency samples: 1740
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.328, avg: 0.218", "QsPosToProposal: max: 0.185, avg: 0.135", "ConsensusProposalToOrdered: max: 0.568, avg: 0.536", "ConsensusOrderedToCommit: max: 0.501, avg: 0.471", "ConsensusProposalToCommit: max: 1.037, avg: 1.007"]
Max round gap was 2 [limit 4] at version 1555312. Max no progress secs was 9.107529 [limit 10] at version 1555312.
Test Ok

github-actions[bot] avatar Jan 09 '24 17:01 github-actions[bot]

:x: Forge suite framework_upgrade failure on aptos-node-v1.8.3 ==> 74b00fc54b381f3c4ef02942a6000227223689b6

Compatibility test results for aptos-node-v1.8.3 ==> 74b00fc54b381f3c4ef02942a6000227223689b6 (PR)
Upgrade the nodes to version: 74b00fc54b381f3c4ef02942a6000227223689b6
Test Failed: API error: Unknown error error sending request for url (http://aptos-node-3-validator.forge-framework-upgrade-pr-11420.svc:8080/v1/estimate_gas_price): error trying to connect: dns error: failed to lookup address information: Name or service not known

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: __libc_start_main
  15: <unknown>
Trailing Log Lines:
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: __libc_start_main
  15: <unknown>


Swarm logs can be found here: See fgi output for more information.
thread 'main' panicked at testsuite/forge/src/backend/k8s/swarm.rs:676:18:
called `Result::unwrap()` on an `Err` value: ApiError: namespaces "forge-framework-upgrade-pr-11420" not found: NotFound (ErrorResponse { status: "Failure", message: "namespaces \"forge-framework-upgrade-pr-11420\" not found", reason: "NotFound", code: 404 })

Caused by:
    namespaces "forge-framework-upgrade-pr-11420" not found: NotFound

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: __libc_start_main
  16: <unknown>
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Debugging output:

github-actions[bot] avatar Jan 09 '24 17:01 github-actions[bot]

Forge is running suite framework_upgrade on aptos-node-v1.8.3 ==> 74b00fc54b381f3c4ef02942a6000227223689b6

github-actions[bot] avatar Jan 09 '24 18:01 github-actions[bot]

:x: Forge suite framework_upgrade failure on aptos-node-v1.8.3 ==> 74b00fc54b381f3c4ef02942a6000227223689b6

Compatibility test results for aptos-node-v1.8.3 ==> 74b00fc54b381f3c4ef02942a6000227223689b6 (PR)
Upgrade the nodes to version: 74b00fc54b381f3c4ef02942a6000227223689b6
Test Failed: API error: Unknown error error sending request for url (http://aptos-node-3-validator.forge-framework-upgrade-pr-11420.svc:8080/v1/estimate_gas_price): error trying to connect: dns error: failed to lookup address information: Name or service not known

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: __libc_start_main
  15: <unknown>
Trailing Log Lines:
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: __libc_start_main
  15: <unknown>


Swarm logs can be found here: See fgi output for more information.
thread 'main' panicked at testsuite/forge/src/backend/k8s/swarm.rs:676:18:
called `Result::unwrap()` on an `Err` value: ApiError: namespaces "forge-framework-upgrade-pr-11420" not found: NotFound (ErrorResponse { status: "Failure", message: "namespaces \"forge-framework-upgrade-pr-11420\" not found", reason: "NotFound", code: 404 })

Caused by:
    namespaces "forge-framework-upgrade-pr-11420" not found: NotFound

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: __libc_start_main
  16: <unknown>
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Debugging output:

github-actions[bot] avatar Jan 09 '24 18:01 github-actions[bot]

Forge is running suite framework_upgrade on aptos-node-v1.8.3 ==> 74b00fc54b381f3c4ef02942a6000227223689b6

github-actions[bot] avatar Jan 09 '24 23:01 github-actions[bot]

:x: Forge suite framework_upgrade failure on aptos-node-v1.8.3 ==> 74b00fc54b381f3c4ef02942a6000227223689b6

Compatibility test results for aptos-node-v1.8.3 ==> 74b00fc54b381f3c4ef02942a6000227223689b6 (PR)
Upgrade the nodes to version: 74b00fc54b381f3c4ef02942a6000227223689b6
Test Failed: API error: Unknown error error sending request for url (http://aptos-node-3-validator.forge-framework-upgrade-pr-11420.svc:8080/v1/estimate_gas_price): error trying to connect: dns error: failed to lookup address information: Name or service not known

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: __libc_start_main
  15: <unknown>
Trailing Log Lines:
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: __libc_start_main
  15: <unknown>


Swarm logs can be found here: See fgi output for more information.
thread 'main' panicked at testsuite/forge/src/backend/k8s/swarm.rs:676:18:
called `Result::unwrap()` on an `Err` value: ApiError: namespaces "forge-framework-upgrade-pr-11420" not found: NotFound (ErrorResponse { status: "Failure", message: "namespaces \"forge-framework-upgrade-pr-11420\" not found", reason: "NotFound", code: 404 })

Caused by:
    namespaces "forge-framework-upgrade-pr-11420" not found: NotFound

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: __libc_start_main
  16: <unknown>
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Debugging output:

github-actions[bot] avatar Jan 10 '24 00:01 github-actions[bot]

Forge is running suite compat on aptos-node-v1.8.3 ==> 32bdfac42b3a80324190fcfbe092bc99b1154a75

github-actions[bot] avatar Jan 10 '24 00:01 github-actions[bot]

Forge is running suite realistic_env_max_load on 32bdfac42b3a80324190fcfbe092bc99b1154a75

github-actions[bot] avatar Jan 10 '24 00:01 github-actions[bot]

Forge is running suite framework_upgrade on aptos-node-v1.8.3 ==> 32bdfac42b3a80324190fcfbe092bc99b1154a75

github-actions[bot] avatar Jan 10 '24 00:01 github-actions[bot]

:white_check_mark: Forge suite compat success on aptos-node-v1.8.3 ==> 32bdfac42b3a80324190fcfbe092bc99b1154a75

Compatibility test results for aptos-node-v1.8.3 ==> 32bdfac42b3a80324190fcfbe092bc99b1154a75 (PR)
1. Check liveness of validators at old version: aptos-node-v1.8.3
compatibility::simple-validator-upgrade::liveness-check : committed: 3952 txn/s, latency: 7020 ms, (p50: 6800 ms, p90: 10800 ms, p99: 13600 ms), latency samples: 177840
2. Upgrading first Validator to new version: 32bdfac42b3a80324190fcfbe092bc99b1154a75
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 1849 txn/s, latency: 15592 ms, (p50: 19200 ms, p90: 21900 ms, p99: 22300 ms), latency samples: 92460
3. Upgrading rest of first batch to new version: 32bdfac42b3a80324190fcfbe092bc99b1154a75
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 1806 txn/s, latency: 16175 ms, (p50: 18900 ms, p90: 22300 ms, p99: 22600 ms), latency samples: 93920
4. upgrading second batch to new version: 32bdfac42b3a80324190fcfbe092bc99b1154a75
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 3578 txn/s, latency: 8848 ms, (p50: 9600 ms, p90: 12600 ms, p99: 12900 ms), latency samples: 143120
5. check swarm health
Compatibility test for aptos-node-v1.8.3 ==> 32bdfac42b3a80324190fcfbe092bc99b1154a75 passed
Test Ok

github-actions[bot] avatar Jan 10 '24 01:01 github-actions[bot]

:white_check_mark: Forge suite realistic_env_max_load success on 32bdfac42b3a80324190fcfbe092bc99b1154a75

two traffics test: inner traffic : committed: 8265 txn/s, submitted: 8267 txn/s, expired: 2 txn/s, latency: 4676 ms, (p50: 4400 ms, p90: 5400 ms, p99: 12900 ms), latency samples: 3562464
two traffics test : committed: 100 txn/s, latency: 2472 ms, (p50: 2100 ms, p90: 2500 ms, p99: 16000 ms), latency samples: 1660
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.346, avg: 0.219", "QsPosToProposal: max: 0.185, avg: 0.134", "ConsensusProposalToOrdered: max: 0.567, avg: 0.529", "ConsensusOrderedToCommit: max: 0.470, avg: 0.448", "ConsensusProposalToCommit: max: 1.002, avg: 0.978"]
Max round gap was 1 [limit 4] at version 1708136. Max no progress secs was 4.7372837 [limit 10] at version 1708138.
Test Ok

github-actions[bot] avatar Jan 10 '24 01:01 github-actions[bot]

:x: Forge suite framework_upgrade failure on aptos-node-v1.8.3 ==> 32bdfac42b3a80324190fcfbe092bc99b1154a75

Compatibility test results for aptos-node-v1.8.3 ==> 32bdfac42b3a80324190fcfbe092bc99b1154a75 (PR)
Upgrade the nodes to version: 32bdfac42b3a80324190fcfbe092bc99b1154a75
Test Failed: API error: Unknown error error sending request for url (http://aptos-node-3-validator.forge-framework-upgrade-pr-11420.svc:8080/v1/estimate_gas_price): error trying to connect: dns error: failed to lookup address information: Name or service not known

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: __libc_start_main
  14: <unknown>
Trailing Log Lines:
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: __libc_start_main
  14: <unknown>


Swarm logs can be found here: See fgi output for more information.
thread 'main' panicked at testsuite/forge/src/backend/k8s/swarm.rs:676:18:
called `Result::unwrap()` on an `Err` value: ApiError: namespaces "forge-framework-upgrade-pr-11420" not found: NotFound (ErrorResponse { status: "Failure", message: "namespaces \"forge-framework-upgrade-pr-11420\" not found", reason: "NotFound", code: 404 })

Caused by:
    namespaces "forge-framework-upgrade-pr-11420" not found: NotFound

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: __libc_start_main
  16: <unknown>
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Debugging output:

github-actions[bot] avatar Jan 10 '24 01:01 github-actions[bot]