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

[not for review][run on forge] Igor/different expiration for account #5931

Closed
wants to merge 4 commits into from

Conversation

igor-aptos
Copy link
Contributor

Description

Test Plan

@igor-aptos igor-aptos added the CICD:run-e2e-tests when this label is present github actions will run all land-blocking e2e tests from the PR label Dec 19, 2022
@igor-aptos igor-aptos force-pushed the igor/different_expiration_for_account branch from 3168db9 to a1dee43 Compare December 19, 2022 22:28
@igor-aptos igor-aptos force-pushed the igor/different_expiration_for_account branch from a1dee43 to 6f23514 Compare December 19, 2022 22:46
@github-actions

This comment has been minimized.

@github-actions
Copy link
Contributor

❌ Forge suite land_blocking failure on performance_6f2351418cd46b098723455d94e39e89ca597c2b

performance benchmark with full nodes : 10482 TPS, 6509 ms latency, 13200 ms p99 latency,(!) expired 8098 out of 4483980 txns
Test Failed: check for success

Caused by:
    "cpu" metric violated threshold of 12, max_breach_pct: 30, breach_pct: 75 
Trailing Log Lines:

Caused by:
    "cpu" metric violated threshold of 12, max_breach_pct: 30, breach_pct: 75 
Test Statistics: 
performance benchmark with full nodes : 10482 TPS, 6509 ms latency, 13200 ms p99 latency,(!) expired 8098 out of 4483980 txns
Test Failed: check for success

Caused by:
    "cpu" metric violated threshold of 12, max_breach_pct: 30, breach_pct: 75 


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:280"},"thread_name":"main","hostname":"forge-e2e-pr-5931-1671494864-performance-6f2351418cd46b09872345","timestamp":"2022-12-20T00:23:35.671992Z","message":"Deleting namespace forge-e2e-pr-5931: Some(NamespaceStatus { phase: Some(\"Terminating\") })"}
{"level":"INFO","source":{"package":"aptos_forge","file":"testsuite/forge/src/backend/k8s/cluster_helper.rs:388"},"thread_name":"main","hostname":"forge-e2e-pr-5931-1671494864-performance-6f2351418cd46b09872345","timestamp":"2022-12-20T00:23:35.672009Z","message":"aptos-node resources for Forge removed in namespace: forge-e2e-pr-5931"}

failures:
    performance benchmark with full nodes

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

Failed to run tests:
Tests Failed
Error: Tests Failed
Debugging output:
NAME                                    READY   STATUS      RESTARTS   AGE
aptos-node-0-fullnode-eforge104-0       1/1     Running     0          14m
aptos-node-0-validator-0                1/1     Running     0          14m
aptos-node-1-fullnode-eforge104-0       1/1     Running     0          14m
aptos-node-1-validator-0                1/1     Running     0          14m
aptos-node-10-fullnode-eforge104-0      1/1     Running     0          14m
aptos-node-10-validator-0               1/1     Running     0          14m
aptos-node-11-fullnode-eforge104-0      1/1     Running     0          14m
aptos-node-11-validator-0               1/1     Running     0          14m
aptos-node-12-fullnode-eforge104-0      1/1     Running     0          14m
aptos-node-12-validator-0               1/1     Running     0          14m
aptos-node-13-fullnode-eforge104-0      1/1     Running     0          14m
aptos-node-13-validator-0               1/1     Running     0          14m
aptos-node-14-fullnode-eforge104-0      1/1     Running     0          14m
aptos-node-14-validator-0               1/1     Running     0          14m
aptos-node-15-fullnode-eforge104-0      1/1     Running     0          14m
aptos-node-15-validator-0               1/1     Running     0          14m
aptos-node-16-fullnode-eforge104-0      1/1     Running     0          14m
aptos-node-16-validator-0               1/1     Running     0          14m
aptos-node-17-fullnode-eforge104-0      1/1     Running     0          14m
aptos-node-17-validator-0               1/1     Running     0          14m
aptos-node-18-fullnode-eforge104-0      1/1     Running     0          14m
aptos-node-18-validator-0               1/1     Running     0          14m
aptos-node-19-fullnode-eforge104-0      1/1     Running     0          14m
aptos-node-19-validator-0               1/1     Running     0          14m
aptos-node-2-fullnode-eforge104-0       1/1     Running     0          14m
aptos-node-2-validator-0                1/1     Running     0          14m
aptos-node-3-fullnode-eforge104-0       1/1     Running     0          14m
aptos-node-3-validator-0                1/1     Running     0          14m
aptos-node-4-fullnode-eforge104-0       1/1     Running     0          14m
aptos-node-4-validator-0                1/1     Running     0          14m
aptos-node-5-fullnode-eforge104-0       1/1     Running     0          14m
aptos-node-5-validator-0                1/1     Running     0          14m
aptos-node-6-fullnode-eforge104-0       1/1     Running     0          14m
aptos-node-6-validator-0                1/1     Running     0          14m
aptos-node-7-fullnode-eforge104-0       1/1     Running     0          14m
aptos-node-7-validator-0                1/1     Running     0          14m
aptos-node-8-fullnode-eforge104-0       1/1     Running     0          14m
aptos-node-8-validator-0                1/1     Running     0          14m
aptos-node-9-fullnode-eforge104-0       1/1     Running     0          14m
aptos-node-9-validator-0                1/1     Running     0          14m
genesis-aptos-genesis-eforge104-rw6gp   0/1     Completed   0          15m

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants