From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alassane Yattara <alassane.yattara@savoirfairelinux.com>,
toaster@lists.yoctoproject.org
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [Toaster] [PATCH 1/3] toaster/test: Bug-fix on TestProjectConfigTab::test_image_recipe_show_rows
Date: Mon, 08 Jan 2024 13:32:51 +0000 [thread overview]
Message-ID: <5461f08d3c4e37e49c775e26fac8784fbc4ffaf8.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240105142218.542729-1-alassane.yattara@savoirfairelinux.com>
Hi Alassane,
On Fri, 2024-01-05 at 15:22 +0100, Alassane Yattara wrote:
> Check some rows are visible in table instead of compare table row to
> row_to_show, because recipe image table sometime doesn't display full avaiblable
> images
>
> Signed-off-by: Alassane Yattara <alassane.yattara@savoirfairelinux.com>
> ---
> lib/toaster/tests/functional/test_project_page_tab_config.py | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Thanks, I've merged this series and run more tests. It is definitely
improving, in the run of seven there was one failed build (4 tests):
https://autobuilder.yoctoproject.org/typhoon/#/builders/161/builds/132/steps/11/logs/stdio
FAILED ../bitbake/lib/toaster/tests/browser/test_new_custom_image_page.py::TestNewCustomImagePage::test_new_duplicates_non_image_recipe
FAILED ../bitbake/lib/toaster/tests/browser/test_new_custom_image_page.py::TestNewCustomImagePage::test_new_duplicates_other_project_image
FAILED ../bitbake/lib/toaster/tests/browser/test_new_custom_image_page.py::TestNewCustomImagePage::test_new_duplicates_project_image
FAILED ../bitbake/lib/toaster/tests/browser/test_new_custom_image_page.py::TestNewCustomImagePage::test_new_image
and in a separate batch of 5 runs, there was also one failed build:
https://autobuilder.yoctoproject.org/typhoon/#/builders/161/builds/124
FAILED ../bitbake/lib/toaster/tests/browser/test_builddashboard_page.py::TestBuildDashboardPage::test_criticals_show_as_errors
which is much better than the previous failure rates.
Cheers,
Richard
prev parent reply other threads:[~2024-01-08 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 14:22 [PATCH 1/3] toaster/test: Bug-fix on TestProjectConfigTab::test_image_recipe_show_rows Alassane Yattara
2024-01-05 14:22 ` [PATCH 2/3] toaster/test: Bug-fix element click intercepted Alassane Yattara
2024-01-05 14:22 ` [PATCH 3/3] toaster/test: Delay driver first action on create new project page Alassane Yattara
2024-01-08 13:32 ` Richard Purdie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5461f08d3c4e37e49c775e26fac8784fbc4ffaf8.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alassane.yattara@savoirfairelinux.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=toaster@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).