Le mardi 12 mars 2019 à 16:44 +0530, Deepshikha Khandelwal a écrit :
> It is now fixed.
This was likely caused by the bugzilla upgrade, who logged the bot out.
To prevent that from happening, we have now a script to log with cron
(every hour), and I am also moving the bugzilla script node inside
On Wed, Mar 13, 2019 at 3:03 PM Yaniv Kaul wrote:
> On Wed, Mar 13, 2019, 3:53 AM Sankarshan Mukhopadhyay
> wrote:
>>
>> What I am essentially looking to understand is whether there are
>> regular Glusto runs and whether the tests receive refreshes. However,
>> if there is no available Glusto se
On Wed, Mar 13, 2019, 3:53 AM Sankarshan Mukhopadhyay <
sankarshan.mukhopadh...@gmail.com> wrote:
> What I am essentially looking to understand is whether there are
> regular Glusto runs and whether the tests receive refreshes. However,
> if there is no available Glusto service running upstream -
