FWIW... I do not know the rules about how these slaves spin up, but in the
10+ minutes since I kicked off that job it is still waiting in queue. And
there is actually a job (Debezium Deploy Snapshots) in front of it that has
been waiting over 3.5 hours
On Fri, Jan 5, 2018 at 6:20 AM Steve Ebersole <steve(a)hibernate.org> wrote:
I went to manually kick off the main ORM job, but saw that you
already had
- however it had failed with GC/memory problems[1]. I kicked off a new
run...
[1]
http://ci.hibernate.org/job/hibernate-orm-master-h2-main/951/console
On Fri, Jan 5, 2018 at 4:59 AM Sanne Grinovero <sanne(a)hibernate.org>
wrote:
> On 4 January 2018 at 23:52, Steve Ebersole <steve(a)hibernate.org> wrote:
> > Awesome Sanne! Great work.
> >
> > Anything you need us to do to our jobs?
>
> No changes *should* be needed. It would help me if you could all
> manually trigger the jobs you consider important and highlight
> suspucious problems so that we get awareness of regressions in short
> time.
>
> I've already triggered some ~20 jobs last night; saw no problems so
> far but haven't tested any release yet, nor website related tasks.
>
> Thanks,
> Sanne
>