Hey, folks. This is just a heads up that we're experiencing increased
levels of openQA test failures due to a few problems:
1. Various tests need to check things out from pagure.io, but lately it
is being flooded by scraper bots and frequently going unresponsive.
This causes tests to fail if
Hi folks! This is just a heads up for update maintainers. You may have
noticed failures of ostree-related tests in openQA over the last few
days - rpmostree_overlay, rpmostree_rebase, or install_default_ostree.
These were caused by
https://bugzilla.redhat.com/show_bug.cgi?id=2284276 , which is now
Hey folks! You may have noticed unpredictable openQA test failures on
Rawhide updates ATM. This is mainly because of the mass rebuild. All the
packages from the mass rebuild have been tagged into the buildroot repo
(which the openQA tests use), so now there are far more on-the-fly
updates than
Due to the ongoing FAS outage - https://status.fedoraproject.org/ - many
updates failed openQA testing, because part of the openQA web browser
test happens to be to open https://accounts.fedoraproject.org and check
it looks as expected. Obviously right now it does not.
As this is not a critica
Il 05/02/22 17:32, Adam Williamson ha scritto:
> On Sat, 2022-02-05 at 09:28 +, Richard W.M. Jones wrote:
>> "This update has been submitted for stable by bodhi"
>>
>> Thanks everyone!
> You might wanna just check after the push happens what happened to the
> package you untagged. I don't actua
On Sat, 2022-02-05 at 09:28 +, Richard W.M. Jones wrote:
> "This update has been submitted for stable by bodhi"
>
> Thanks everyone!
You might wanna just check after the push happens what happened to the
package you untagged. I don't actually know offhand what will happen to
it in this situat
"This update has been submitted for stable by bodhi"
Thanks everyone!
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripti
On Sat, Feb 05, 2022 at 09:02:17AM +, Mattia Verga via devel wrote:
> Il 05/02/22 09:49, Richard W.M. Jones ha scritto:
> > On Sat, Feb 05, 2022 at 08:10:53AM +, Mattia Verga via devel wrote:
> >> Il 05/02/22 08:31, Richard W.M. Jones ha scritto:
> >>> How do I make this update go to Rawhid
Il 05/02/22 09:49, Richard W.M. Jones ha scritto:
> On Sat, Feb 05, 2022 at 08:10:53AM +, Mattia Verga via devel wrote:
>> Il 05/02/22 08:31, Richard W.M. Jones ha scritto:
>>> How do I make this update go to Rawhide? I have already tested the
>>> important packages in the set locally.
>>>
>>>
On Fri, Feb 04, 2022 at 11:47:21PM -0800, Adam Williamson wrote:
> On Sat, 2022-02-05 at 07:31 +, Richard W.M. Jones wrote:
> > https://bodhi.fedoraproject.org/updates/FEDORA-2022-8e3a84510b
> >
> > It's really unclear why this Rawhide update isn't just being tagged
> > into Rawhide. Single b
On Sat, Feb 05, 2022 at 08:10:53AM +, Mattia Verga via devel wrote:
> Il 05/02/22 08:31, Richard W.M. Jones ha scritto:
> > How do I make this update go to Rawhide? I have already tested the
> > important packages in the set locally.
> >
> > Rich.
>
> Have you tried the "Waive test results" b
Il 05/02/22 08:31, Richard W.M. Jones ha scritto:
> How do I make this update go to Rawhide? I have already tested the
> important packages in the set locally.
>
> Rich.
Have you tried the "Waive test results" button in the right column?
Mattia
___
d
On Sat, 2022-02-05 at 07:31 +, Richard W.M. Jones wrote:
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-8e3a84510b
>
> It's really unclear why this Rawhide update isn't just being tagged
> into Rawhide. Single builds don't go through this complicated
> process.
Bodhi's UI isn't the cl
https://bodhi.fedoraproject.org/updates/FEDORA-2022-8e3a84510b
It's really unclear why this Rawhide update isn't just being tagged
into Rawhide. Single builds don't go through this complicated
process.
But let's assume it's because of the test failures.
Hey folks! Just a heads up about test failures in openQA overnight and
today. The server_cockpit_updates test was failing overnight; this was
because I switched from virtio to qxl graphics to work around a bug in
Rawhide. Unfortunately there seems to be a bug in qxl with a specific
thing that test
On 1/28/21 10:16 AM, Boian Bonev wrote:
> Hi,
>
> I just did a build (new upstream release of iotop-c) and saw a couple
> of test errors; they look like segfaults or post errors, so I suppose
> that I didn't do some stupid mistake.
>
> Posting the result here, to keep the relevant team informed;
Hi,
I just did a build (new upstream release of iotop-c) and saw a couple
of test errors; they look like segfaults or post errors, so I suppose
that I didn't do some stupid mistake.
Posting the result here, to keep the relevant team informed; in case
these are known, sorry for the noise :)
https
On Mon, 2019-09-16 at 13:19 +0200, Vít Ondruch wrote:
> Since FF 69, I observer rendering failures. To be more precise, when
> switching (by mouse?) from one tab to another, the content of previous
> tab is kept. Ctrl+Tab and Ctrl+Tab to get back typically fixes the issue.
Yeah, that's https://bug
Since FF 69, I observer rendering failures. To be more precise, when
switching (by mouse?) from one tab to another, the content of previous
tab is kept. Ctrl+Tab and Ctrl+Tab to get back typically fixes the issue.
Vít
Dne 14. 09. 19 v 17:42 Adam Williamson napsal(a):
> Hey folks! Just a heads-
Hey folks! Just a heads-up for anyone watching the openQA test results
for their updates. If you see a failure of the desktop_browser test
which seems to end on Firefox rendering
https://accounts.fedoraproject.org/ weirdly, like this:
https://openqa.fedoraproject.org/tests/450082
https://openqa.f
On Fri, 2018-10-05 at 13:21 -0700, Adam Williamson wrote:
>
> Two, the upgrade_realmd_client test seems to fail every time lately,
> like this:
>
> https://openqa.fedoraproject.org/tests/288372#step/upgrade_run/19
>
> it's failing while trying to upgrade the system, at a step where it
> tries to
Hey folks!
If anyone's looking at openQA results for their updates, you may have
noticed odd failures for several tests for updates submitted in the
last day or so.
It seems that all runs of tests that communicate with each other have
been failing on production openQA since the infra reboot that
On Mon, May 14, 2018 at 1:39 PM, Alexander Ploumistos <
alex.ploumis...@gmail.com> wrote:
>
> Well, rpmlint is the one that failed and only on two arches, that's why I
> wanted it to be run again, just in case something was off the first time. I
> thought that if library-without-ldconfig-postin we
> "AP" == Alexander Ploumistos writes:
AP> /usr/bin/python: can't open file '/usr/lib/rpm/python-macro-helper':
AP> [Errno 2] No such file or directory
For the record, this happens because rpmlint does the equivalent of:
rpm -E %python_sitearch
by calling the expandMacro() function from th
On Mon, May 14, 2018 at 11:59 AM Kamil Paral wrote:
> On Sun, May 13, 2018 at 12:22 PM, Alexander Ploumistos <
alex.ploumis...@gmail.com> wrote:
>> Hello,
>> I've just submitted an update to cmpfit[0] for f28. The automated tests
>> show errors and warnings only on x86_64 and armv7hl[1] and the
On Sun, May 13, 2018 at 12:22 PM, Alexander Ploumistos <
alex.ploumis...@gmail.com> wrote:
> Hello,
>
> I've just submitted an update to cmpfit[0] for f28. The automated tests
> show errors and warnings only on x86_64 and armv7hl[1] and the errors have
> to do with the omission of ldconfig scriptl
Hello,
I've just submitted an update to cmpfit[0] for f28. The automated tests
show errors and warnings only on x86_64 and armv7hl[1] and the errors have
to do with the omission of ldconfig scriptlets. Aren't we supposed to get
rid of these for f28+?
The warnings are:
cmpfit-devel.armv7hl: W: no-
Hi folks! Another note for anyone paying attention to openQA test
results.
Since 2017-08-09 there's been kind of a flood of failures caused by
'typing errors' - that is, when the test runner is trying to type a
string into the test VM and it doesn't get through correctly (usually
due to one or mor
updated libsearpc on rawhide. I also
> > > proposed the update of fedora 25 [1] (still in testing). After my
> > > successful build on rawhide, Dan Horak opened a bug [2] about
> > > test
> > > failures on ppc and s390 architectures with the update.
> > >
gt; successful build on rawhide, Dan Horak opened a bug [2] about test
> > failures on ppc and s390 architectures with the update.
> >
> > The previous version doesn't seem affected by this issue. I'd like
> > some inputs on how I can do to solve these issues and up
On Sun, Nov 6, 2016 at 12:06 PM, Julien Enselme wrote:
> Hi,
>
> I recently (2016-10-23) updated libsearpc on rawhide. I also proposed
> the update of fedora 25 [1] (still in testing). After my successful
> build on rawhide, Dan Horak opened a bug [2] about test failures on
Hi,
I recently (2016-10-23) updated libsearpc on rawhide. I also proposed
the update of fedora 25 [1] (still in testing). After my successful
build on rawhide, Dan Horak opened a bug [2] about test failures on ppc
and s390 architectures with the update.
The previous version doesn't seem aff
32 matches
Mail list logo
