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

Address the empty tarball issue #119

Merged
merged 1 commit into from
Jul 18, 2023
Merged

Conversation

cole-miller
Copy link
Contributor

@cole-miller cole-miller commented Jul 18, 2023

Closes #105. The basic issue is that the tar process was getting SIGPERM while trying to read the data directory -- this is fixed by invoking with sudo. The failure was masked by a use of str instead of info or another function that prints to the log.

With this change, I sometimes see tar complaining about the data directory changing during archival, because the app process is still running while Jepsen runs log-files. I'm not sure how to deal with that, because we don't control the order of events during shutdown, but I think it can be left to a follow-up PR in any case.

Signed-off-by: Cole Miller cole.miller@canonical.com

Signed-off-by: Cole Miller <cole.miller@canonical.com>
@cole-miller
Copy link
Contributor Author

Confirmed that a proper tarball is uploaded with the failure artifact for the failed CI jobs for this PR 🎊

@cole-miller cole-miller merged commit 752b074 into canonical:master Jul 18, 2023
77 of 79 checks passed
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.

data.tar.bz2 seems to be empty
1 participant