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

2018-12-23 Thread 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="";

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

2018-12-23 Thread 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

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

2018-12-23 Thread 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

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

2018-12-23 Thread 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

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

2018-12-22 Thread 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