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

chore: delete testnode home dir during cleanup #1411

Merged
merged 1 commit into from
Feb 22, 2023

Conversation

rach-id
Copy link
Member

@rach-id rach-id commented Feb 22, 2023

Overview

Deletes testnode home directory during cleanup.

In fact, we have the following structure when creating the testnode: /tmp/TestOrchestrator3541559682/001/.celestia-app/config:

  • we will delete /tmp/TestOrchestrator3541559682/001/.celestia-app ourselves in the cleanup (this PR)
  • the testing package will delete /tmp/TestOrchestrator3541559682 automatically

This would leave the created t.tempDir() empty and hopefully reduce the frequency we see this flakiness https://github.com/celestiaorg/celestia-app/actions/runs/4242679413/jobs/7374501607

Checklist

  • New and updated code has appropriate documentation
  • New and updated code has new and/or updated testing
  • Required CI checks are passing
  • Visual proof for any user facing features like CLI or documentation updates
  • Linked issues closed with keywords

@rach-id rach-id added the testing items that are strictly related to adding or extending test coverage label Feb 22, 2023
@rach-id rach-id self-assigned this Feb 22, 2023
@MSevey MSevey requested review from a team and rootulp and removed request for a team February 22, 2023 12:40
@rach-id
Copy link
Member Author

rach-id commented Feb 22, 2023

The CI is failing because of this #1413

@rach-id rach-id merged commit 1a22bee into celestiaorg:main Feb 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing items that are strictly related to adding or extending test coverage
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants