Re: cannot delete workspace ... invoker-reports/BUILD-***.xml

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: cannot delete workspace ... invoker-reports/BUILD-***.xml

Enrico Olivelli
Il sab 12 gen 2019, 11:39 Tibor Digana <[hidden email]> ha scritto:

> Such a drastic change?
>

If that version is buggy we should fix it or drop it.

Do we have already released that buggy version to users?


How did you see our processes on Jenkins slave? Do you have access to
slaves console?

Enrico


First we should get the confidence using Jenkins CI for a long time run.

>
> On Sat, Jan 12, 2019 at 11:20 AM Enrico Olivelli <[hidden email]>
> wrote:
>
> > Can't we rollback to the previous version instead of a snapshot?
> >
> > Enrico
> >
> > Il sab 12 gen 2019, 09:23 Tibor Digana <[hidden email]> ha
> > scritto:
> >
> > > I think we should downgrade maven-shared-utils to 3.1.0 in the
> > m-invoker-p
> > > because we found the same problem in surefire:3.0.0-M1.
> > > We did not have time to fix it and I have realized the connection to
> the
> > > Invoker just now.
> > > Faster than a release is to deploy SNAPSHOT version of the Invoker and
> > use
> > > it in JAR plugin and we will see again fully working Jenkins build
> > >
> >
> https://builds.apache.org/job/maven-box/job/maven-jar-plugin/job/MJAR-238/
> > > The precondition is to ask the INFRA to restart all Windows or kill all
> > > Java processes.
> > > T
> > >
> > --
> >
> >
> > -- Enrico Olivelli
> >
>
--


-- Enrico Olivelli
Reply | Threaded
Open this post in threaded view
|

Re: cannot delete workspace ... invoker-reports/BUILD-***.xml

rfscholte
I want to do a release of the plugin very soon. Cleaning up the workspace  
is mostly caused by an invoker-report. I also noticed that some  
input/outputstreams weren't closed properly, that has been fixed already.
If maven-shared-utils 3.2.1 is a likely cause too, then I'll downgrade  
that one. Stable jobs are much more important to me.

thanks,
Robert

On Sat, 12 Jan 2019 09:23:20 +0100, Tibor Digana <[hidden email]>  
wrote:

> I think we should downgrade maven-shared-utils to 3.1.0 in the  
> m-invoker-p
> because we found the same problem in surefire:3.0.0-M1.
> We did not have time to fix it and I have realized the connection to the
> Invoker just now.
> Faster than a release is to deploy SNAPSHOT version of the Invoker and  
> use
> it in JAR plugin and we will see again fully working Jenkins build
> https://builds.apache.org/job/maven-box/job/maven-jar-plugin/job/MJAR-238/
> The precondition is to ask the INFRA to restart all Windows or kill all
> Java processes.
> T

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: cannot delete workspace ... invoker-reports/BUILD-***.xml

Tibor Digana-3
In reply to this post by Enrico Olivelli
>> which commit could have broken shared utils ?

I have picked up three candidate commits:

362805fbf6341523edfdf509905812acb42f6a97
fd082c077c78f8ce83fce2a92f0265e83599a42f
f2246e0653b185297451902ee278e6aec1ff470e

Those devs who have Windows should run the build of maven-jar-plugin (mvn
verify -P run-its) and list all Java processes after the build.
This process should repeat with maven-shared-utils:3.1.0 and again list all
Java processes.
Logically there should not be any Java processes alive after the build has
completed.

Then we can decide whether we will find the commit and release a new
version of maven-shared-utils or we will downgrade it in all
usages/projects/branches together with testing on Jenkins.
Cheers
T




On Sat, Jan 12, 2019 at 11:50 AM Enrico Olivelli <[hidden email]>
wrote:

> Il giorno sab 12 gen 2019 alle ore 11:45 Enrico Olivelli
> <[hidden email]> ha scritto:
> >
> >
> >
> > Il sab 12 gen 2019, 11:39 Tibor Digana <[hidden email]> ha
> scritto:
> >>
> >> Such a drastic change?
> >
> >
> > If that version is buggy we should fix it or drop it.
> >
> > Do we have already released that buggy version to users?
> >
> >
> > How did you see our processes on Jenkins slave? Do you have access to
> slaves console?
> >
>
> b.q.
> which commit could have broken shared utils ?
> https://github.com/apache/maven-shared-utils/commits/master
>
>
> Enrico
>
>
> > Enrico
> >
> >
> >> First we should get the confidence using Jenkins CI for a long time run.
> >>
> >> On Sat, Jan 12, 2019 at 11:20 AM Enrico Olivelli <[hidden email]>
> >> wrote:
> >>
> >> > Can't we rollback to the previous version instead of a snapshot?
> >> >
> >> > Enrico
> >> >
> >> > Il sab 12 gen 2019, 09:23 Tibor Digana <[hidden email]> ha
> >> > scritto:
> >> >
> >> > > I think we should downgrade maven-shared-utils to 3.1.0 in the
> >> > m-invoker-p
> >> > > because we found the same problem in surefire:3.0.0-M1.
> >> > > We did not have time to fix it and I have realized the connection
> to the
> >> > > Invoker just now.
> >> > > Faster than a release is to deploy SNAPSHOT version of the Invoker
> and
> >> > use
> >> > > it in JAR plugin and we will see again fully working Jenkins build
> >> > >
> >> >
> https://builds.apache.org/job/maven-box/job/maven-jar-plugin/job/MJAR-238/
> >> > > The precondition is to ask the INFRA to restart all Windows or kill
> all
> >> > > Java processes.
> >> > > T
> >> > >
> >> > --
> >> >
> >> >
> >> > -- Enrico Olivelli
> >> >
> >
> > --
> >
> >
> > -- Enrico Olivelli
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
Cheers
Tibor
Reply | Threaded
Open this post in threaded view
|

Re: cannot delete workspace ... invoker-reports/BUILD-***.xml

rfscholte
Using the following line to see all java.exe processes

tasklist /FI "IMAGENAME eq java.exe"

current maven-jar-plugin (master) is using maven-shared-utils-3.2.1
After running this, I don't see new/hanging java processes

Robert

On Sat, 12 Jan 2019 12:59:08 +0100, Tibor Digana  
<[hidden email]> wrote:

>>> which commit could have broken shared utils ?
>
> I have picked up three candidate commits:
>
> 362805fbf6341523edfdf509905812acb42f6a97
> fd082c077c78f8ce83fce2a92f0265e83599a42f
> f2246e0653b185297451902ee278e6aec1ff470e
>
> Those devs who have Windows should run the build of maven-jar-plugin (mvn
> verify -P run-its) and list all Java processes after the build.
> This process should repeat with maven-shared-utils:3.1.0 and again list  
> all
> Java processes.
> Logically there should not be any Java processes alive after the build  
> has
> completed.
>
> Then we can decide whether we will find the commit and release a new
> version of maven-shared-utils or we will downgrade it in all
> usages/projects/branches together with testing on Jenkins.
> Cheers
> T
>
>
>
>
> On Sat, Jan 12, 2019 at 11:50 AM Enrico Olivelli <[hidden email]>
> wrote:
>
>> Il giorno sab 12 gen 2019 alle ore 11:45 Enrico Olivelli
>> <[hidden email]> ha scritto:
>> >
>> >
>> >
>> > Il sab 12 gen 2019, 11:39 Tibor Digana <[hidden email]> ha
>> scritto:
>> >>
>> >> Such a drastic change?
>> >
>> >
>> > If that version is buggy we should fix it or drop it.
>> >
>> > Do we have already released that buggy version to users?
>> >
>> >
>> > How did you see our processes on Jenkins slave? Do you have access to
>> slaves console?
>> >
>>
>> b.q.
>> which commit could have broken shared utils ?
>> https://github.com/apache/maven-shared-utils/commits/master
>>
>>
>> Enrico
>>
>>
>> > Enrico
>> >
>> >
>> >> First we should get the confidence using Jenkins CI for a long time  
>> run.
>> >>
>> >> On Sat, Jan 12, 2019 at 11:20 AM Enrico Olivelli  
>> <[hidden email]>
>> >> wrote:
>> >>
>> >> > Can't we rollback to the previous version instead of a snapshot?
>> >> >
>> >> > Enrico
>> >> >
>> >> > Il sab 12 gen 2019, 09:23 Tibor Digana <[hidden email]> ha
>> >> > scritto:
>> >> >
>> >> > > I think we should downgrade maven-shared-utils to 3.1.0 in the
>> >> > m-invoker-p
>> >> > > because we found the same problem in surefire:3.0.0-M1.
>> >> > > We did not have time to fix it and I have realized the connection
>> to the
>> >> > > Invoker just now.
>> >> > > Faster than a release is to deploy SNAPSHOT version of the  
>> Invoker
>> and
>> >> > use
>> >> > > it in JAR plugin and we will see again fully working Jenkins  
>> build
>> >> > >
>> >> >
>> https://builds.apache.org/job/maven-box/job/maven-jar-plugin/job/MJAR-238/
>> >> > > The precondition is to ask the INFRA to restart all Windows or  
>> kill
>> all
>> >> > > Java processes.
>> >> > > T
>> >> > >
>> >> > --
>> >> >
>> >> >
>> >> > -- Enrico Olivelli
>> >> >
>> >
>> > --
>> >
>> >
>> > -- Enrico Olivelli
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: cannot delete workspace ... invoker-reports/BUILD-***.xml

Enrico Olivelli
Il sab 12 gen 2019, 14:09 Robert Scholte <[hidden email]> ha scritto:

> Using the following line to see all java.exe processes
>
> tasklist /FI "IMAGENAME eq java.exe"
>

How do you do this on slave Jenkins machines?

Enrico

>
> current maven-jar-plugin (master) is using maven-shared-utils-3.2.1
> After running this, I don't see new/hanging java processes
>
> Robert
>
> On Sat, 12 Jan 2019 12:59:08 +0100, Tibor Digana
> <[hidden email]> wrote:
>
> >>> which commit could have broken shared utils ?
> >
> > I have picked up three candidate commits:
> >
> > 362805fbf6341523edfdf509905812acb42f6a97
> > fd082c077c78f8ce83fce2a92f0265e83599a42f
> > f2246e0653b185297451902ee278e6aec1ff470e
> >
> > Those devs who have Windows should run the build of maven-jar-plugin (mvn
> > verify -P run-its) and list all Java processes after the build.
> > This process should repeat with maven-shared-utils:3.1.0 and again list
> > all
> > Java processes.
> > Logically there should not be any Java processes alive after the build
> > has
> > completed.
> >
> > Then we can decide whether we will find the commit and release a new
> > version of maven-shared-utils or we will downgrade it in all
> > usages/projects/branches together with testing on Jenkins.
> > Cheers
> > T
> >
> >
> >
> >
> > On Sat, Jan 12, 2019 at 11:50 AM Enrico Olivelli <[hidden email]>
> > wrote:
> >
> >> Il giorno sab 12 gen 2019 alle ore 11:45 Enrico Olivelli
> >> <[hidden email]> ha scritto:
> >> >
> >> >
> >> >
> >> > Il sab 12 gen 2019, 11:39 Tibor Digana <[hidden email]> ha
> >> scritto:
> >> >>
> >> >> Such a drastic change?
> >> >
> >> >
> >> > If that version is buggy we should fix it or drop it.
> >> >
> >> > Do we have already released that buggy version to users?
> >> >
> >> >
> >> > How did you see our processes on Jenkins slave? Do you have access to
> >> slaves console?
> >> >
> >>
> >> b.q.
> >> which commit could have broken shared utils ?
> >> https://github.com/apache/maven-shared-utils/commits/master
> >>
> >>
> >> Enrico
> >>
> >>
> >> > Enrico
> >> >
> >> >
> >> >> First we should get the confidence using Jenkins CI for a long time
> >> run.
> >> >>
> >> >> On Sat, Jan 12, 2019 at 11:20 AM Enrico Olivelli
> >> <[hidden email]>
> >> >> wrote:
> >> >>
> >> >> > Can't we rollback to the previous version instead of a snapshot?
> >> >> >
> >> >> > Enrico
> >> >> >
> >> >> > Il sab 12 gen 2019, 09:23 Tibor Digana <[hidden email]> ha
> >> >> > scritto:
> >> >> >
> >> >> > > I think we should downgrade maven-shared-utils to 3.1.0 in the
> >> >> > m-invoker-p
> >> >> > > because we found the same problem in surefire:3.0.0-M1.
> >> >> > > We did not have time to fix it and I have realized the connection
> >> to the
> >> >> > > Invoker just now.
> >> >> > > Faster than a release is to deploy SNAPSHOT version of the
> >> Invoker
> >> and
> >> >> > use
> >> >> > > it in JAR plugin and we will see again fully working Jenkins
> >> build
> >> >> > >
> >> >> >
> >>
> https://builds.apache.org/job/maven-box/job/maven-jar-plugin/job/MJAR-238/
> >> >> > > The precondition is to ask the INFRA to restart all Windows or
> >> kill
> >> all
> >> >> > > Java processes.
> >> >> > > T
> >> >> > >
> >> >> > --
> >> >> >
> >> >> >
> >> >> > -- Enrico Olivelli
> >> >> >
> >> >
> >> > --
> >> >
> >> >
> >> > -- Enrico Olivelli
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
> --


-- Enrico Olivelli
Reply | Threaded
Open this post in threaded view
|

Re: cannot delete workspace ... invoker-reports/BUILD-***.xml

olamy
In reply to this post by Enrico Olivelli
Yup I updated https://issues.apache.org/jira/browse/INFRA-17514 with some
details.
so we have to wait next Jenkins plugins upgrade before reactivate it.
Note there is always a bloody committer who do not use bloody windauze to
develop... :)

On Tue, 15 Jan 2019 at 06:54, Robert Scholte <[hidden email]> wrote:

> I've removed the invokerPublisher() calls in our Jenkins scripts, this
> seems to be the cause of the hanging Java processes.
> Within a couple of hours I expect all Windows nodes to be restarted by
> INFRA and then we should be good again.
>
> thanks,
> Robert
>
> On Sat, 12 Jan 2019 09:23:20 +0100, Tibor Digana <[hidden email]>
>
> wrote:
>
> > I think we should downgrade maven-shared-utils to 3.1.0 in the
> > m-invoker-p
> > because we found the same problem in surefire:3.0.0-M1.
> > We did not have time to fix it and I have realized the connection to the
> > Invoker just now.
> > Faster than a release is to deploy SNAPSHOT version of the Invoker and
> > use
> > it in JAR plugin and we will see again fully working Jenkins build
> >
> https://builds.apache.org/job/maven-box/job/maven-jar-plugin/job/MJAR-238/
> > The precondition is to ask the INFRA to restart all Windows or kill all
> > Java processes.
> > T
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy