Marcin Sobczyk writes:
> On 3/21/22 13:30, Marcin Sobczyk wrote:
>>
>> On 3/21/22 11:53, Milan Zamazal wrote:
>>> Milan Zamazal writes:
>>>
Hi,
/ost failed in
https://github.com/oVirt/vdsm/pull/99/checks?check_run_id=5605825076,
apparently because it thinks there are
On 3/21/22 13:30, Marcin Sobczyk wrote:
On 3/21/22 11:53, Milan Zamazal wrote:
Milan Zamazal writes:
Hi,
/ost failed in
https://github.com/oVirt/vdsm/pull/99/checks?check_run_id=5605825076,
apparently because it thinks there are no artifacts. But the artifacts
are there:
On 3/21/22 11:53, Milan Zamazal wrote:
Milan Zamazal writes:
Hi,
/ost failed in
https://github.com/oVirt/vdsm/pull/99/checks?check_run_id=5605825076,
apparently because it thinks there are no artifacts. But the artifacts
are there: https://github.com/oVirt/vdsm/actions/runs/2005557814.
Package maintainers please focus on closing open issues without trying to
push for new last minute features: those can wait for 4.5.1.
Remind that 4.5.0 GA is planned for 2022-04-12 so there will be space for
only one release candidate.
Testers: please continue testing the released Alpha and
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART;VALUE=DATE:20220331
DTEND;VALUE=DATE:20220401
DTSTAMP:20220321T110333Z
ORGANIZER;CN=sbona...@redhat.com:mailto:sbona...@redhat.com
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20220329T15Z
DTEND:20220329T155000Z
DTSTAMP:20220321T110007Z
ORGANIZER;CN=sbona...@redhat.com:mailto:sbona...@redhat.com
Milan Zamazal writes:
> Hi,
>
> /ost failed in
> https://github.com/oVirt/vdsm/pull/99/checks?check_run_id=5605825076,
> apparently because it thinks there are no artifacts. But the artifacts
> are there: https://github.com/oVirt/vdsm/actions/runs/2005557814.
The same happens when running OST
Sandro Bonazzola writes:
> Il giorno ven 18 mar 2022 alle ore 20:20 Milan Zamazal
> ha scritto:
>
>> Hi,
>>
>> reportedly some Vdsm contributors (non-maintainers?) cannot set labels
>> on their own pull requests on GitHub. Could anybody with the required
>> permissions check the settings and
Il giorno ven 18 mar 2022 alle ore 20:20 Milan Zamazal
ha scritto:
> Hi,
>
> reportedly some Vdsm contributors (non-maintainers?) cannot set labels
> on their own pull requests on GitHub. Could anybody with the required
> permissions check the settings and if it is indeed the case then permit
>
