-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
br/lightning: fix the integration test cases #29062
br/lightning: fix the integration test cases #29062
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/run-br-integration-tests |
/run-integration-br-test |
/run-integration-br-test |
/run-integration-br-test |
/run-integration-br-test |
/run-integration-br-test |
/run-integration-br-test |
/run-integration-br-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rest lgtm
@@ -16,6 +16,8 @@ | |||
|
|||
set -eux | |||
|
|||
#skip for temporary. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe also add the reason and log to stdout?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, add the simple reason.
Actually, this case failed due to ERRORCODE is 0(success), but we have insert some value before lightning starts, so we expect the checksum failed and ERRORCODE is not 0.
/run-integration-br-test |
please file issues for the two skipped tests. |
sure, I'll do it |
Add in PR description. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 554e2f3
|
@3pointer: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
What problem does this PR solve?
Problem Summary:
Fix ci cases for br/lightning.
What is changed and how it works?
This PR tried to fix these test cases:
max-pending-peer-count
andmax-snapshot-count
raised to 64. so I think we can ignore these configs in test case.lightning-checkpoint-dirty-tableid
failed. due to some checks still enable even --check-requirements=false.Check List
Tests
Release note