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

[Fix][e2e] Fix e2e failed due to server overload. #15578

Closed
wants to merge 14 commits into from

Conversation

jackyyyyyssss
Copy link
Contributor

@jackyyyyyssss jackyyyyyssss commented Feb 6, 2024

Purpose of the pull request

fix #15579
fix e2e sometimes error Reduce the probability of e2e errors. Currently, it has been found that some cases of e2e errors are as follows: 1. Because the automated testing browser cannot click on the switch, switch to a different writing method for clicking. 2. the resource is overloaded, increase the load parameter, first modify a few core methods to reduce the failure rate, and then modify based on the failed cases
image
image

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.

(or)

This pull request is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(or)

If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

@codecov-commenter
Copy link

codecov-commenter commented Feb 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 39.11%. Comparing base (c0435e5) to head (07463e0).
Report is 1 commits behind head on dev.

❗ Current head 07463e0 differs from pull request most recent head 7fc8f45. Consider uploading reports for the commit 7fc8f45 to get more accurate results

Additional details and impacted files
@@            Coverage Diff            @@
##                dev   #15578   +/-   ##
=========================================
  Coverage     39.11%   39.11%           
  Complexity     4887     4887           
=========================================
  Files          1326     1326           
  Lines         45206    45206           
  Branches       4818     4818           
=========================================
  Hits          17683    17683           
  Misses        25635    25635           
  Partials       1888     1888           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jackyyyyyssss jackyyyyyssss changed the title [fix][e2e]:Fix e2e sometime error [fix][e2e]:Fix e2e sometimes error Feb 6, 2024
@SbloodyS SbloodyS added improvement make more easy to user or prompt friendly minor Chore Chores about the project, like code clean, typo, etc. and removed bug Something isn't working labels Feb 7, 2024
@SbloodyS SbloodyS added this to the 3.2.1 milestone Feb 7, 2024
@github-actions github-actions bot removed the e2e e2e test label Feb 7, 2024
@mergeable mergeable bot added the e2e e2e test label Feb 7, 2024
@github-actions github-actions bot removed the e2e e2e test label Feb 7, 2024
@@ -191,7 +191,7 @@ master:
server-load-protection:
enabled: true
# Master max cpu usage, when the master's cpu usage is smaller then this value, master server can execute workflow.
max-cpu-usage-percentage-thresholds: 0.9
max-cpu-usage-percentage-thresholds: 1.5
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
max-cpu-usage-percentage-thresholds: 1.5
max-cpu-usage-percentage-thresholds: 1.0

The max value of this parameter shouldld be 1.0.

@@ -216,7 +216,7 @@ worker:
server-load-protection:
enabled: true
# Worker max cpu usage, when the worker's cpu usage is smaller then this value, worker server can be dispatched tasks.
max-cpu-usage-percentage-thresholds: 0.9
max-cpu-usage-percentage-thresholds: 1.5
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
max-cpu-usage-percentage-thresholds: 1.5
max-cpu-usage-percentage-thresholds: 1.0

Copy link
Contributor Author

@jackyyyyyssss jackyyyyyssss Feb 18, 2024

Choose a reason for hiding this comment

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

@ruanwenjun Hello Sometimes the utilization rate of underlying resources can be greater than 1, so setting it to 1.5 can overload and cause e2e failure if set to 1
image

Copy link
Member

Choose a reason for hiding this comment

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

This should be a bug, we may need to use getTotalCpuUsedPercentage() to compare with maxCpuUsagePercentageThresholds at ServerLoadProtection

@ruanwenjun ruanwenjun changed the title [fix][e2e]:Fix e2e sometimes error [Fix][e2e] Fix e2e failed due to server overload. Feb 13, 2024
@ruanwenjun ruanwenjun removed this from the 3.2.1 milestone Feb 13, 2024
@ruanwenjun ruanwenjun added e2e e2e test and removed 3.2.1 labels Feb 13, 2024
@ruanwenjun
Copy link
Member

Due to 3.2.1 has been released, and this will not affect the release package, I removed the 3.2.1 milestone.

Copy link

sonarcloud bot commented Feb 13, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

Copy link

sonarcloud bot commented Apr 3, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@ruanwenjun
Copy link
Member

Since this PR is no longer updated, I submit #15803 to fix this problem, thanks for your PR.

@ruanwenjun ruanwenjun closed this Apr 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend improvement make more easy to user or prompt friendly minor Chore Chores about the project, like code clean, typo, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Fix][e2e] Fix e2e failed due to server overload.
6 participants