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

test: make sure that WindowPoSt also works on read-only files #1630

Merged
merged 3 commits into from
Sep 19, 2022

Conversation

vmx
Copy link
Contributor

@vmx vmx commented Sep 15, 2022

This commit adapts the test to make the generated files read-only before a WindowPoSt is performed. This simulates the use case when you mount your sectors read-only after generation.

This commit adapts the test to make the generated files read-only
before a WindowPoSt is performed. This simulates the use case when
you mount your sectors read-only after generation.
cryptonemo
cryptonemo previously approved these changes Sep 15, 2022
@storojs72 storojs72 self-requested a review September 16, 2022 15:29
Copy link
Contributor

@storojs72 storojs72 left a comment

Choose a reason for hiding this comment

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

We also need to test winning_post similarly - as it was mentioned in the original issue: #1629 (comment)

@cryptonemo
Copy link
Collaborator

Kicked off the CI again now that merkletree has been released

@cryptonemo
Copy link
Collaborator

We also need to test winning_post similarly - as it was mentioned in the original issue: #1629 (comment)

Not a bad idea, but not a requirement for this PR

The Window PoSt tests were already working on read-only files where
possible, do the same for Winning PoSt.
@vmx
Copy link
Contributor Author

vmx commented Sep 19, 2022

It now makes the replica files read-only and also tests Winning PoSt the same way.

Copy link
Contributor

@storojs72 storojs72 left a comment

Choose a reason for hiding this comment

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

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants