After the last Jenkins restart, the jobs run now fine.
Thanks
Jan
> -Ursprüngliche Nachricht-
> Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
> Gesendet: Dienstag, 10. Juli 2018 09:12
> An: builds@apache.org
> Betreff: AW: Build hangs
>
> Our nightly job is no
Our nightly job is not working right since 30.06.2018 ...
https://builds.apache.org/view/A/view/Ant/job/Ant_Nightly
#934 30.06.2018 16:54 @H21 last successful build
job config changed
2018-07-01_09-22-35
by: SYSTEM
what: update plugins: rebuild@1.27->1.28, git@3.7.0->3.
i 2018 10:03
> An: builds
> Betreff: Re: Build hangs
>
> Ok you should all have Cancel job perms again.
>
> HTH
>
> Gav...
>
> On Mon, Jul 2, 2018 at 8:51 AM, Gav wrote:
>
> > Hi,
> >
> > We upgraded the main Jenkins yesterday to 2.121.1.
://jenkins.io/changelog-stable/
>
>
> On Mon, Jul 2, 2018 at 6:55 AM, Jan Matèrne (jhm)
> wrote:
>
>> > > Our nightly build hangs for seven hours [1].
>> > >
>> > > Could someone kill that so the next could start?
>> >
>> >
>> >
&g
rage everyone to read
the upgrade docs.
Thanks
Gav...
[1] - https://jenkins.io/changelog-stable/
On Mon, Jul 2, 2018 at 6:55 AM, Jan Matèrne (jhm) wrote:
> > > Our nightly build hangs for seven hours [1].
> > >
> > > Could someone kill that so the next could start?
&
> > Our nightly build hangs for seven hours [1].
> >
> > Could someone kill that so the next could start?
>
>
>
> Cancelled via the UI. Did you try that? That’s ordinarily self-service.
>
Yes - no 'abort job' for me (jhm).
Neither on the concrete
> On Jul 1, 2018, at 12:32 PM, Jan Matèrne wrote:
>
> Our nightly build hangs for seven hours [1].
>
> Could someone kill that so the next could start?
Cancelled via the UI. Did you try that? That’s ordinarily self-service.
-Chris
>
>
>
> [WARNINGS] Com
Our nightly build hangs for seven hours [1].
Could someone kill that so the next could start?
[WARNINGS] Computing warning deltas based on reference build #934
Archiving artifacts
[Fast Archiver] Compressed 59.48 MB of artifacts by 10.1% relative to #934
>>> no activity <&
Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:662)
>>
>> Is this a configuration issue?
>>
>> Cheers,
>>
>> Frank
>>
>> On Thu, May 3, 2012 at 11:09 AM, Frank Scholten
>> wrote:
>>>
utor.java:908)
> at java.lang.Thread.run(Thread.java:662)
>
> Is this a configuration issue?
>
> Cheers,
>
> Frank
>
> On Thu, May 3, 2012 at 11:09 AM, Frank Scholten
> wrote:
>> Hi,
>>
>> The Whirr-Ubuntu continuous build hangs has b
lExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
>
> Is this a configuration issue?
>
> Cheers,
>
> Frank
>
> On Thu, May 3, 2012 at 11:09 AM, Frank Scholten
> wrote:
>> Hi,
>>
>> The Whirr-Ubuntu continuous build hangs
The Whirr-Ubuntu continuous build hangs has been running for almost a
> day and we are not authorized to stop the build or reconfigure it.
>
> Can you have a look at it?
>
> Cheers,
>
> Frank
Hi,
I just run one build.
See logs https://builds.apache.org/job/Whirr-Ubuntu/338/console
2012/5/3 Frank Scholten :
> Hi,
>
> The Whirr-Ubuntu continuous build hangs has been running for almost a
> day and we are not authorized to stop the build or reconfigure it.
>
> Can you
Hi,
The Whirr-Ubuntu continuous build hangs has been running for almost a
day and we are not authorized to stop the build or reconfigure it.
Can you have a look at it?
Cheers,
Frank
I cannot stop this build anymore:
https://builds.apache.org/pview/job/River-trunk-QA-windows/5/
Can one of the build admins forcibly kill this build?
Gr. Sim
I see the reason for this. The pre-commit admin builds failed as the
jira host was not reachable
curl: (22) The requested URL returned error: 503
On 12/31/11 7:53 AM, Ted Yu wrote:
Hi,
I couldn't stop the build:
https://builds.apache.org/view/G-L/view/HBase/job/HBase-0.92/222/console
Please
Hi,
I couldn't stop the build:
https://builds.apache.org/view/G-L/view/HBase/job/HBase-0.92/222/console
Please take a look.
Thanks
17 matches
Mail list logo
