Bug#917119: [Qa-jenkins-dev] Bug#917119: jenkins.debian.org: Lintian test jobs have not run since 21st November 2018

[Chris Lamb]

Mattia Rizzolo wrote:

> Could you please check on salsa if there is anything written in the
> webhook delivery log?  (click on the "edit" button of the webhook).

It's indeed failing with a HTTP 500 error:

"Response body:"
  
  


Jenkins [Jenkins]var isRunAsTest=false; var rootURL=""; 
var resURL="/static/75d12a2e";crumb.init("Jenkins-Crumb", 
"da0294a50bc2cf9f8273ef7c6fcb9b9d");https://jenkins.debian.net/userContent/theme/debian.css"/>Skip to content log 
in https://jenkins.io/redirect/search-box;>createSearchBox("/search/");Jenkinshttps://jenkins.io/; class="task-icon-link"> https://jenkins.io/; class="task-link">Jenkins projecthttps://jenkins.io/redirect/report-an-issue; 
class="task-icon-link"> https://jenkins.io/redirect/report-an-issue; class="task-link">Bug 
trackerhttps://jenkins.io/redirect/mailing-lists; class="task-icon-link"> https://jenkins.io/redirect/mailing-lists; 
class="task-link">Mailing Listshttps://twitter.com/jenkinsci; class="task-icon-link"> https://twitter.com/jenkinsci; class="task-link">Twitter: 
@jenkinsci Oops!A problem occurred while processing the request.
Please check https://jenkins.io/redirect/issue-tracker;>our 
bug tracker to see if a similar problem has already been reported.
If it is already reported, please vote and put a comment on it to let 
us gauge the impact of the problem.
If you think this is a new issue, please file a new issue.
When you file an issue, make sure to add the entire stack trace, along 
with the version of Jenkins and relevant plugins.
https://jenkins.io/redirect/users-mailing-list;>The users 
list might be also useful in understanding what has happened.Stack 
tracejava.lang.NullPointerException
at 
com.dabsquared.gitlabjenkins.trigger.handler.AbstractWebHookTriggerHandler.setCommitStatusPendingIfNecessary(AbstractWebHookTriggerHandler.java:67)
at 
com.dabsquared.gitlabjenkins.trigger.handler.AbstractWebHookTriggerHandler.handle(AbstractWebHookTriggerHandler.java:53)
at 
com.dabsquared.gitlabjenkins.trigger.handler.push.PushHookTriggerHandlerImpl.handle(PushHookTriggerHandlerImpl.java:30)
at 
com.dabsquared.gitlabjenkins.trigger.handler.push.PushHookTriggerHandlerImpl.handle(PushHookTriggerHandlerImpl.java:23)
at 
com.dabsquared.gitlabjenkins.trigger.handler.push.PushHookTriggerHandlerList.handle(PushHookTriggerHandlerList.java:24)
at 
com.dabsquared.gitlabjenkins.trigger.handler.push.PushHookTriggerHandlerList.handle(PushHookTriggerHandlerList.java:13)
at 
com.dabsquared.gitlabjenkins.GitLabPushTrigger.onPost(GitLabPushTrigger.java:442)
at 
com.dabsquared.gitlabjenkins.webhook.build.PushBuildAction$1.performOnPost(PushBuildAction.java:86)
at 
com.dabsquared.gitlabjenkins.webhook.build.BuildWebHookAction$TriggerNotifier.run(BuildWebHookAction.java:54)
at hudson.security.ACL.impersonate(ACL.java:273)
at 
com.dabsquared.gitlabjenkins.webhook.build.PushBuildAction.execute(PushBuildAction.java:83)
at 
com.dabsquared.gitlabjenkins.webhook.build.BuildWebHookAction.execute(BuildWebHookAction.java:31)
at 
com.dabsquared.gitlabjenkins.webhook.GitLabWebHook.getDynamic(GitLabWebHook.java:44)
at 
java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)
at 
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)
at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:456)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)
Caused: javax.servlet.ServletException
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870)
at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154)
at 
hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)
at hudson.plugins.locale.LocaleFilter.doFilter(LocaleFilter.java:42)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)
at 

Bug#917119: [Qa-jenkins-dev] Bug#917119: jenkins.debian.org: Lintian test jobs have not run since 21st November 2018

[Mattia Rizzolo]

Control: reopen -1

On Sun, Dec 23, 2018 at 03:22:20PM +0100, Mattia Rizzolo wrote:
> I haven't manually triggered the job. I expect any new push that
> temporarely happened after I closed this bug to be able to correctly
> trigger it, however I don't see any.

Turns out I was blind.

> > What am I missing? Should I re-open this bug? :)

Doing so now, as something went wrong somewhere.  I see the jenkins log
changed, as there is now a a traceback after each correctly
authenticated hook invocation.

Could you please check on salsa if there is anything written in the
webhook delivery log?  (click on the "edit" button of the webhook).

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#917119: [Qa-jenkins-dev] Bug#917119: jenkins.debian.org: Lintian test jobs have not run since 21st November 2018

[Mattia Rizzolo]

On Sun, 23 Dec 2018, 3:03 p.m. Chris Lamb  I'm afraid I'm a little lost in the detail here. However, you appear
> to have closed this bug but the last test run on Jenkins is still from
> November (despite multiple pushes this morning):
>

I haven't manually triggered the job. I expect any new push that
temporarely happened after I closed this bug to be able to correctly
trigger it, however I don't see any.

What am I missing? Should I re-open this bug? :)
>

If you try to push something it should just work again.
Sorry for being unclear on what perhaps is the most interesting detail!`

Bug#917119: [Qa-jenkins-dev] Bug#917119: jenkins.debian.org: Lintian test jobs have not run since 21st November 2018

[Chris Lamb]

Gentile Mattia,

> On Sat, Dec 22, 2018 at 10:30:41PM +, Chris Lamb wrote:
> >  Any pointers on why https://jenkins.debian.net/job/lintian-
> > tests_sid/ has not run in ~1 mo ?
> 
> Usual thing due to the lintian job being my guinea pig for special
> gitlab<->jenkins integration, whereas the secret token gets overwritten
> every time the packages-tests set of jobs is deployed.

I'm afraid I'm a little lost in the detail here. However, you appear
to have closed this bug but the last test run on Jenkins is still from
November (despite multiple pushes this morning):

  Permalinks:
  
Last build (#3433), 1 mo 2 days ago
Last stable build (#3433), 1 mo 2 days ago
Last successful build (#3433), 1 mo 2 days ago
Last failed build (#3424), 1 mo 4 days ago
Last unsuccessful build (#3424), 1 mo 4 days ago
Last completed build (#3433), 1 mo 2 days ago

-- 

What am I missing? Should I re-open this bug? :)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#917119: [Qa-jenkins-dev] Bug#917119: jenkins.debian.org: Lintian test jobs have not run since 21st November 2018

[Mattia Rizzolo]

Control: owner -1 !

On Sat, Dec 22, 2018 at 10:30:41PM +, Chris Lamb wrote:
>  Any pointers on why https://jenkins.debian.net/job/lintian-
> tests_sid/ has not run in ~1 mo ?
> no idea, no

I know what's going on, I'm very sorry for not noticying this earlier
(as somebody may have guessed I haven't kept a tight look over jenking
in the past weeks…).

I will fix tomorrow when I'll be near my keys again.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-