-
Notifications
You must be signed in to change notification settings - Fork 60
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
O_TMPFILE test failing #217
Comments
So you are saying yuo have a system where this fails with |
EOPNOTSUPP, I think: assertion failed (errno == 0): (95 == 0) |
OK, so your kernel supports |
Or it means that the redirection is not working and it opened the real |
Possibly, but I'd expect an EPERM/EACCESS then, as the user is hopefully not allowed to write into /dev
|
Either way, @cazfi please let me know some details here --- OS, build environment, how you built, and please run the whole thing through |
It might be that "usually" is the key word here. This is a NixOS build, so things might live in unusual places. |
Ah, NixOS! Do you have |
I don't have that particular setup any more, and on other kind of setups I have everything works. |
OK, thanks for reporting back. I'll commit the g_get_tmpdir() thing, can't hurt. |
This ensures that the emulated /dev (which is created in `g_get_tmp_dir()` via `DirUtils.make_tmp()` and the feature check are done in the same directory. If `$TMPDIR` is set, that may not be the case. Fixes #217
This ensures that the emulated /dev (which is created in `g_get_tmp_dir()` via `DirUtils.make_tmp()` and the feature check are done in the same directory. If `$TMPDIR` is set, that may not be the case. Fixes #217
I have O_TMPFILE test failing. More precisely, it's the "errno == 0" assert that fails. Likely the problem is that you don't have as strict checks for whether it's even supposed to work as actual tests are:
The text was updated successfully, but these errors were encountered: