-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[TT-1952] Write application logs for in-memory tests to file and safe in artifacts #16029
base: develop
Are you sure you want to change the base?
Conversation
This comment was marked as spam.
This comment was marked as spam.
Flakeguard SummaryRan new or updated tests between View Flaky Detector Details | Compare Changes Found Flaky Tests ❌
ArtifactsFor detailed logs of the failed tests, please refer to the artifact failed-test-results-with-logs.json. |
Flakeguard SummaryRan new or updated tests between View Flaky Detector Details | Compare Changes Found Flaky Tests ❌
ArtifactsFor detailed logs of the failed tests, please refer to the artifact failed-test-results-with-logs.json. |
Flakeguard SummaryRan new or updated tests between View Flaky Detector Details | Compare Changes Found Flaky Tests ❌
ArtifactsFor detailed logs of the failed tests, please refer to the artifact failed-test-results-with-logs.json. |
…tt-1952-split-in-memory-logs
|
Write the logs for the cl nodes used in the environment for the in-memory tests to log files located in ./integration-tests/smoke/ccip/logs/ . These files will be available as artifacts after running the in-memory tests in CI.
e.g. in this run https://github.com/smartcontractkit/chainlink/actions/runs/13176452557/job/36776884455 the smoke/ccip/ccip_messaging_test.go failed, so you can find the logs for the nodes that ran during the test in the smoke_ccip_ccip_messaging_test_go_-test-logs artifact.