Skip to content
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

node-test-commit-osx consistently failing with NullPointerException #681

Closed
aqrln opened this issue Apr 11, 2017 · 2 comments
Closed

node-test-commit-osx consistently failing with NullPointerException #681

aqrln opened this issue Apr 11, 2017 · 2 comments

Comments

@aqrln
Copy link

aqrln commented Apr 11, 2017

...
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Run condition [Always] enabling perform for step [Builder to mark whether executed]
Triggering node-test-commit-osx » osx1010
FATAL: null
java.lang.NullPointerException
	at java.util.HashSet.<init>(HashSet.java:118)
	at hudson.model.ParametersAction.shouldSchedule(ParametersAction.java:228)
	at hudson.model.Queue.scheduleInternal(Queue.java:615)
	at hudson.model.Queue.schedule2(Queue.java:585)
	at hudson.matrix.MatrixConfiguration.scheduleBuild(MatrixConfiguration.java:512)
...

https://ci.nodejs.org/job/node-test-commit-osx/8928/console
https://ci.nodejs.org/job/node-test-commit-osx/8929/console
https://ci.nodejs.org/job/node-test-commit-osx/8930/console

@aqrln aqrln changed the title node-test-commit-osx consistently failing with NullPointerException node-test-commit-osx consistently failing with NullPointerException Apr 11, 2017
@jbergstroem
Copy link
Member

ping @rvagg

@Trott
Copy link
Member

Trott commented Apr 11, 2017

Looks like this has been resolved. Would be great to get a comment describing the fix if someone knows what fixed it. In any event, closing...

@Trott Trott closed this as completed Apr 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants