They asked me to create a JIRA for the job scheduling glitch: 
<https://issues.apache.org/jira/browse/INFRA-14007>.

--
Steve
www.lucidworks.com

> On Apr 25, 2017, at 11:38 AM, Steve Rowe <[email protected]> wrote:
> 
> Infra has rebooted the lucene node, no luck.  Jobs are still not getting 
> enqueued.
> 
> There is a general idea that it might have something to do with the 
> *.apache.org wildcard cert that was installed yesterday.  They’re looking 
> into it.
> 
> Also they made an issue for an additional Jenkins node for Lucene/Solr jobs: 
> <https://issues.apache.org/jira/browse/INFRA-14004>.
> 
> --
> Steve
> www.lucidworks.com
> 
>> On Apr 25, 2017, at 10:00 AM, Steve Rowe <[email protected]> wrote:
>> 
>> Looks like jobs are not getting put on the queue, so the lucene node goes to 
>> sleep.
>> 
>> Not sure why jobs’ schedules aren’t being respected, e.g. the non-nightly 
>> test jobs are scheduled to build @hourly.
>> 
>> I clicked the button to start the agent on the lucene node, then manually 
>> kicked off the “Lucene-Solr-Tests-master” job, which seems to be running 
>> fine.
>> 
>> I’ll go chat with Infra on hipchat.
>> 
>> --
>> Steve
>> www.lucidworks.com
>> 
>>> On Apr 25, 2017, at 9:23 AM, Mikhail Khludnev <[email protected]> wrote:
>>> 
>>> Hi, Dev!
>>> 
>>> It seems it's offline https://builds.apache.org/computer/lucene/ 
>>> 
>>> -- 
>>> Sincerely yours
>>> Mikhail Khludnev
>> 
> 


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

Reply via email to