And its probably down again. Last notification I received was at
2022-04-20 16:37:08 UTC
Vít
Dne 20. 04. 22 v 17:04 Vít Ondruch napsal(a):
Dne 19. 04. 22 v 20:35 Kevin Fenzi napsal(a):
On Tue, Apr 19, 2022 at 07:48:56PM +0200, Vít Ondruch wrote:
I think this is broken again. Last
Dne 19. 04. 22 v 20:35 Kevin Fenzi napsal(a):
On Tue, Apr 19, 2022 at 07:48:56PM +0200, Vít Ondruch wrote:
I think this is broken again. Last notification I have received was at
03:50:49 UTC.
Yep. Restarted it.
Thank you. It works as of today.
In other news, we now have the upstream
On Tue, Apr 19, 2022 at 07:48:56PM +0200, Vít Ondruch wrote:
> I think this is broken again. Last notification I have received was at
> 03:50:49 UTC.
Yep. Restarted it.
In other news, we now have the upstream python3 version deployed in
staging and are testing it/fixing issues. After f36 is out
I think this is broken again. Last notification I have received was at
03:50:49 UTC.
Vít
Dne 22. 03. 22 v 12:56 Vít Ondruch napsal(a):
Actually, just moments ago 11:44 UTC I have received more messages,
this time stamped 2022-03-21 17:35:45 UTC. So while the service is not
completely
Actually, just moments ago 11:44 UTC I have received more messages, this
time stamped 2022-03-21 17:35:45 UTC. So while the service is not
completely dead, the delay is getting bigger.
Vít
Dne 22. 03. 22 v 12:34 Vít Ondruch napsal(a):
No notifications again. The last notification I have
On Tue, Mar 22, 2022 at 12:35 PM Vít Ondruch wrote:
>
> No notifications again. The last notification I have received was today
> on 6:38 UTC originally sent 2022-03-21 15:55:21 UTC.
At this point, I wonder if it wouldn't be more productive to just add
a cron job to restart that service once a
No notifications again. The last notification I have received was today
on 6:38 UTC originally sent 2022-03-21 15:55:21 UTC.
Vít
Dne 19. 03. 22 v 22:50 Kevin Fenzi napsal(a):
On Thu, Mar 17, 2022 at 10:29:37AM +0100, Vít Ondruch wrote:
Dne 07. 03. 22 v 19:12 Kevin Fenzi napsal(a):
I
On Thu, Mar 17, 2022 at 10:29:37AM +0100, Vít Ondruch wrote:
>
> Dne 07. 03. 22 v 19:12 Kevin Fenzi napsal(a):
> > I watched it over the weekend, and now it's only 3 days behind. ;(
> > Hopefully it will finish catching up... I'm continuing to watch it.
>
>
> It eventually caught up and I have
Dne 07. 03. 22 v 19:12 Kevin Fenzi napsal(a):
I watched it over the weekend, and now it's only 3 days behind. ;(
Hopefully it will finish catching up... I'm continuing to watch it.
It eventually caught up and I have received the notifications on time up
until 2022-03-16 15:49:09 UTC. After
On Sat, Mar 05, 2022 at 10:58:53AM +, Dan Čermák wrote:
>
>
> On March 5, 2022 9:03:54 AM UTC, Gary Buhrmaster
> wrote:
> >On Mon, Feb 28, 2022 at 5:25 PM Kevin Fenzi wrote:
> >
> >> No, there's things we can do and are trying to do. ;)
> >
> >I seem to remember that one of the issues
>
On March 5, 2022 9:03:54 AM UTC, Gary Buhrmaster
wrote:
>On Mon, Feb 28, 2022 at 5:25 PM Kevin Fenzi wrote:
>
>> No, there's things we can do and are trying to do. ;)
>
>I seem to remember that one of the issues
>identified was (for those of us using gmail
>for the notifications) was that
On Mon, Feb 28, 2022 at 5:25 PM Kevin Fenzi wrote:
> No, there's things we can do and are trying to do. ;)
I seem to remember that one of the issues
identified was (for those of us using gmail
for the notifications) was that google could
end up throttling emails.
I have a vague recollection
Am 28.02.22 um 14:45 schrieb Richard Shaw:
I almost wrote this a week ago but decided not to as it's been recently
discussed but this is really annoying. 6 days later is more than useless.
FWIW: I just received a bunch (ca. 10) of notifications with 5 days of
delay.
Don't know if somebody
On Tue, Mar 01, 2022 at 10:42:38AM +0100, Vít Ondruch wrote:
>
> Dne 28. 02. 22 v 18:24 Kevin Fenzi napsal(a):
> > On Mon, Feb 28, 2022 at 07:45:27AM -0600, Richard Shaw wrote:
> > > I almost wrote this a week ago but decided not to as it's been recently
> > > discussed but this is really
On Tue, Mar 01, 2022 at 08:04:14PM -, Peter Oliver wrote:
> > I almost wrote this a week ago but decided not to as it's been recently
> > discussed but this is really annoying. 6 days later is more than useless.
> > ...
> > Is there really nothing we can do about this?
>
> I think getting
On 28. 02. 22 18:24, Kevin Fenzi wrote:
On Mon, Feb 28, 2022 at 07:45:27AM -0600, Richard Shaw wrote:
I almost wrote this a week ago but decided not to as it's been recently
discussed but this is really annoying. 6 days later is more than useless.
Previously it was blamed, at least
> I almost wrote this a week ago but decided not to as it's been recently
> discussed but this is really annoying. 6 days later is more than useless.
> ...
> Is there really nothing we can do about this?
I think getting https://github.com/fedora-infra/fmn/pull/294 merged would help
a little,
Dne 28. 02. 22 v 18:24 Kevin Fenzi napsal(a):
On Mon, Feb 28, 2022 at 07:45:27AM -0600, Richard Shaw wrote:
I almost wrote this a week ago but decided not to as it's been recently
discussed but this is really annoying. 6 days later is more than useless.
Previously it was blamed, at least
On Mon, Feb 28, 2022 at 11:25 AM Kevin Fenzi wrote:
> On Mon, Feb 28, 2022 at 07:45:27AM -0600, Richard Shaw wrote:
> > I almost wrote this a week ago but decided not to as it's been recently
> > discussed but this is really annoying. 6 days later is more than useless.
> >
> > Previously it was
On Mon, Feb 28, 2022 at 07:45:27AM -0600, Richard Shaw wrote:
> I almost wrote this a week ago but decided not to as it's been recently
> discussed but this is really annoying. 6 days later is more than useless.
>
> Previously it was blamed, at least partially, on the mass rebuild, but
> clearly
I almost wrote this a week ago but decided not to as it's been recently
discussed but this is really annoying. 6 days later is more than useless.
Previously it was blamed, at least partially, on the mass rebuild, but
clearly that should no longer be an issue by now?
I know I can turn them off,
21 matches
Mail list logo
