FAIL: test/run-tests

[jacob008]

ok 373 - we_get_signals
ok 374 - we_get_signals_mixed
FAIL: test/run-tests

1 of 1 test failed
Please report to https://github.com/libuv/libuv/issues

make[1]: *** [check-TESTS] Error 1
make[1]: Leaving directory `/root/c++/libuv/libuv'
make: *** [check-am] Error 2
[root@localhost libuv]#

我也不知道是干什么，它叫我report 到这里 ，我也不知道有什么用！

[jacob008]

ok 47 - fs_chown
not ok 48 - fs_copyfile

exit code 6

Output from process fs_copyfile:

Assertion failed in test/test-fs-copyfile.c on line 202: req.result == UV_EACCES

ok 49 - fs_event_close_in_callback

补充一下。。

[sffc]

+1, this is reproducible on CentOS 7 with unmodified code built with autotools from the v1.x branch:

...
ok 46 - fs_chmod
ok 47 - fs_chown
not ok 48 - fs_copyfile
# exit code 134
# Output from process `fs_copyfile`:
# Assertion failed in test/test-fs-copyfile.c on line 202: req.result == UV_EACCES
ok 49 - fs_event_close_in_callback
ok 50 - fs_event_close_with_pending_event
...

[sffc]

The test failure reproduces on v1.32.0 but not v1.24.1. I didn't check all the versions between v1.24.1 and v1.32.0.

[cjihrig]

Are you able to provide the value of req.result here? That test was added in c7b87b0, when it was discovered that macOS wasn't respecting file permissions in its copyfile() function. Hopefully you're just bumping into a different error code.

[richardlau]

make[1]: Leaving directory `/root/c++/libuv/libuv'

I think test failures are expected if running as root?

[cjihrig]

I think test failures are expected if running as root?

Yes, that too. The issue template explicitly calls that out, and has since before this issue was created.