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

Don't say tests are successful when they are not #53

Merged
merged 1 commit into from
Mar 9, 2024

Conversation

hhartzer
Copy link
Contributor

@hhartzer hhartzer commented Mar 8, 2024

Fixes: #52

@hhartzer
Copy link
Contributor Author

hhartzer commented Mar 8, 2024

It looks like there have been a few changes lately that have broken tests in interesting ways.

This includes:

All good changes, but it would be good if we can get the tests to catch up to the code. Would appreciate contributions to this PR if anyone is up for it.

@emikulic
Copy link
Owner

emikulic commented Mar 9, 2024

I just fixed TestDirList, I'll try to do a few more. 3a72fc4

@emikulic
Copy link
Owner

emikulic commented Mar 9, 2024

Try now.

@hhartzer hhartzer changed the title Draft: Don't say tests are successful when they are not Don't say tests are successful when they are not Mar 9, 2024
@hhartzer
Copy link
Contributor Author

hhartzer commented Mar 9, 2024

Awesome, thank you!

It works for me as long as I'm not root. If I'm root, the forbidden tests don't respond properly.

I think this should be good now.

@emikulic
Copy link
Owner

emikulic commented Mar 9, 2024

I'm ok with run-tests requiring non-root. :)

@emikulic emikulic merged commit b7e6163 into emikulic:master Mar 9, 2024
@hhartzer
Copy link
Contributor Author

hhartzer commented Mar 9, 2024

Me too. Thank you!

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.

Tests don't pass, but say they do
2 participants