-
Notifications
You must be signed in to change notification settings - Fork 47
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
ATF is incompatible with capsicum #45
Comments
I discovered and fixed this in 2017: cemeyer@317c806 . Jmmv won't take my change because I can't sign Google's CLA on my employer's behalf. |
That's lame. Do we need to fork atf? |
Sure, a freebsd/atf fork is fine with me. If jmmv's fork has activity (it's pretty idle) we can always pull new material down. |
Who has the authority to create new repos in the freebsd organization? |
Not me. I'd ask Ed. |
What is new with this fork? In NetBSD I would love to rely on plain C rather than fancy C++. C++ creates some burden on the system. It happened to be harder to get C++ right, sanitized etc than execute some preexisting regression tests that are mostly C code. |
I doubt we would make any immediate move away from C++. |
Fix #45: Preopen result files before running testcases
@jansucan discovered that if an ATF test case enters capability mode with
cap_enter
, then it won't be able to write the results file. It seems like this would be easy to fix, but simply opening up the results file at the top ofatf_tc_run
. Thoughts? cc @jmmv @ngie-eign .The text was updated successfully, but these errors were encountered: