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

citgm-smoker-nobuild not working #2125

Closed
sam-github opened this issue Jan 3, 2020 · 7 comments
Closed

citgm-smoker-nobuild not working #2125

sam-github opened this issue Jan 3, 2020 · 7 comments

Comments

@sam-github
Copy link
Contributor

I'm not sure if it used to.

Last failed:

Earliest fail with a log:

All are:

20:44:20 Building remotely on test-packetnet-ubuntu1604-x64-1 (Ubuntu Ubuntu-16.04 amd64-Ubuntu jenkins-workspace amd64-Ubuntu-16.04 16.04 amd64) in workspace /home/iojs/build/workspace/citgm-smoker-nobuild
20:44:20 FATAL: null
20:44:20 java.lang.NullPointerException
20:44:20 	at hudson.plugins.templateproject.ProxySCM.checkout(ProxySCM.java:92)
20:44:20 	at hudson.scm.SCM.checkout(SCM.java:504)
20:44:20 	at hudson.model.AbstractProject.checkout(AbstractProject.java:1209)
20:44:20 	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
20:44:20 	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
20:44:20 	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
20:44:20 	at hudson.model.Run.execute(Run.java:1816)
20:44:20 	at hudson.matrix.MatrixBuild.run(MatrixBuild.java:323)
20:44:20 	at hudson.model.ResourceController.execute(ResourceController.java:97)
20:44:20 	at hudson.model.Executor.run(Executor.java:429)

This might be related to a change @richardlau made on2019-12-19_20-14-05 :

@sam-github
Copy link
Contributor Author

Screenshot 2020-01-03 at 16 21 21

Changed that to None, will try a build, see if that helps.

@sam-github
Copy link
Contributor Author

@AshCripps
Copy link
Member

AshCripps commented Jan 3, 2020

is that job working properly? looks like the builds fail immediately after one test failure?

EDIT:
examples:
https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker-nobuild/nodes=rhel7-s390x/704/
https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker-nobuild/nodes=aix61-ppc64/704/

Is this intended behaviour?

@sam-github
Copy link
Contributor Author

I don't know, but doesn't look right to me, either. At this point, perhaps we should wait for the people with more experience setting the citgm jobs up to step in.

@BethGriggs
Copy link
Member

@AshCripps that was the expected behaviour for that run - I wanted to check whether moment was failing on all platforms before skipping it in nodejs/citgm#777

Parameters now working as expected - https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker-nobuild/nodes=rhel7-s390x/704

@richardlau
Copy link
Member

This might be related to a change @richardlau made on2019-12-19_20-14-05 :

Sorry about that — I must have inadvertently clicked the radio button.

@sam-github
Copy link
Contributor Author

OK, I was worried something else would break. It sounds like switching back to an scm of none was the right fix.

@BethGriggs can you close if this is now working as expected?

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

4 participants