-
Notifications
You must be signed in to change notification settings - Fork 83
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
pjdfstest: fix basic OSX support #10
Conversation
Only define HAS_MKFIFOAT/HAS_MKNODAT if not using OSX. Fixes issue # 5
Print out the last column in the df output, instead of column # 6
This makes pjdfstest work for me on 10.11.6 (El Capitan)
Darwin functions like Linux/Solaris, not FreeBSD
@@ -96,8 +96,10 @@ | |||
#define HAS_FSTATAT | |||
#define HAS_LINKAT | |||
#define HAS_MKDIRAT | |||
#ifndef __APPLE__ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This nests the OSX defines within the "other" list. I think it would be more clear if the defines went one OS at a time, eg
#ifdef __FreeBSD_version
...
#else ifdef __APPLE__
...
# else //all others
...
#endif
Though really, I think autoconf would be preferable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't want to be too invasive here with autoconf in the pull request. I'll do it in the next stage.
@@ -63,6 +63,12 @@ for type in regular fifo block char socket symlink; do | |||
create_file ${type} ${n1} 0640 65534 65534 | |||
expect 0 symlink ${n1} ${n2} | |||
case "${os}" in | |||
Darwin) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This could be Darwin|Linux)
and combine it with the Linux
block below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but there aren't any guarantees that this will remain that way >_>... Just one step to making OS X work with pjdfstest.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sidenote: I still need to run the tests with OS X Sierra (10.12.x). I would assume that they "just work", but I'm not willing to bank on that 100%.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be fine with me if pjdfstest only passes on the latest version of each supported OS. Managing expected failures should be the responsibility of downstream consumers, IMHO.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your explanations make sense. This PR LGTM.
This test asserts that chflags will fail if securelevel=1 and certain flags are already set. Since it requires changing securelevel, we do it in a jail, using the jail-rs crate. Since we can't fork in a multithreaded program, we instead execute /bin/chflags within the jail. Issue pjd#10
This test asserts that chflags will fail if securelevel=1 and certain flags are already set. Since it requires changing securelevel, we do it in a jail, using the jail-rs crate. Since we can't fork in a multithreaded program, we instead execute /bin/chflags within the jail. Issue pjd#10
This test asserts that chflags will fail if securelevel=1 and certain flags are already set. Since it requires changing securelevel, we do it in a jail, using the jail-rs crate. Since we can't fork in a multithreaded program, we instead execute /bin/chflags within the jail. Issue pjd#10
This addresses some base issues which prevented pjdfstest from being compiled/run on OS X clients.
There are 14 failed test programs that need to be fixed on OS X still, in part due to:
Tested on: El Capitan (10.11.6)
Sponsored by: Dell EMC Isilon