-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
FreeBSD failures on v4.x #9013
Comments
/cc @nodejs/platform-freebsd |
Logs? |
|
Thanks! |
That's: spawn('echo', ['fhqwhgads'], {uid: 0}) That is expected to throw EPERM. |
the error is that it isn't throwing |
@thealphanerd oh, I was just stating what happens in test. Sorry! |
@thealphanerd is it running under root (or superuser)? Is it running in jail? |
@thealphanerd what is the output of |
when I was manually running it @jbergstroem may know more about how things are setup during CI |
@jbergstroem I wonder if this box may be running tests with effective user id set to |
@thealphanerd thanks! |
@jbergstroem further question, do we use https://www.freebsd.org/doc/handbook/mac.html ? |
@indutny no, we run as regular user: $ id
uid=1002(iojs) gid=1002(iojs) groups=1002(iojs) re mac: this is stock freebsd 10.3p9 -- I recall mac modules being optional so I'd say no. |
Currently having failures on CI for this on v4.x This is including failures on previously passing versions tracking issue nodejs#9013
@MylesBorins is this fixed? |
yup |
This is a very odd one
parallel/test-child-process-uid-gid
started failing today when I was testing v4.x.This test has not failed in the past, but is now failing the current head of
v4.x-staging
,v4.6.0
, andv4.5.0
I am unsure if this is an env issue or not... I have attempted to ssh into one of our BSD machines, manually compile and test, and see no failures.
I've also attempted to manually in the artifact directory that jenkins used both with the commands
$ ./node test/parallel/test-child-process-uid-gid.js
and
$ python tools/test.py parallel/test-child-process-uid-gid
neither of these attempts fail either.
The text was updated successfully, but these errors were encountered: