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="";
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
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
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
On Sat, Dec 22, 2018 at 11:37:45PM +0100, Mattia Rizzolo wrote:
> 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…).
would you please share what's wrong, so that eventually others
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
Package: jenkins.debian.org
Severity: normal
Hey,
Any pointers on why https://jenkins.debian.net/job/lintian-
tests_sid/ has not run in ~1 mo ?
no idea, no
other lintian jobs have run?
No, https://jenkins.debian.net/job/lintian-tests_buster/
(for
7 matches
Mail list logo