action #59363
closed
[desktop] test fails in firefox_urlsprotocols - ftp://mirror.bej.suse.com/ unreachable
Added by ggardet_arm over 4 years ago.
Updated almost 3 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-aarch64-desktopapps-firefox-x11@aarch64 fails in
firefox_urlsprotocols
Test suite description¶
Reproducible¶
Fails since (at least) Build 20191109 (current job)
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
- Subject changed from test fails in firefox_urlsprotocols - ftp://mirror.bej.suse.com/ unreachable to [desktop] test fails in firefox_urlsprotocols - ftp://mirror.bej.suse.com/ unreachable
- Assignee set to yfjiang
- Priority changed from Normal to High
- Assignee changed from yfjiang to zcjia
Hello Zhaocong,
Would you help to handle it please.
Hi @ggardet_arm, can you tell me why the firefox tests is added for arm please?
Let me explain some background: I originally added the firefox tests to TW, because I need to migrate the testcases for firefox ESR 68 for SLE15SP2. Now firefox ESR 68 is released and the tests are upgraded and passed, so I removed the firefox testcases from TW -- because firefox changes too quickly in TW, it'll be too much burden to maintain it.
So, do you have any particular reason to run this test on arm? If not, we should remove this firefox@aarch64 test.
@zcjia I added this test to aarch64 (in Development > Tumbleweed) because it was added for x86_64 in Development > Tumbleweed on o3, and I find it useful.
Does it really change too quickly on Tumbleweed? It seems there is an update in Tumbleweed every 3-4 weeks on average.
@ggardet_arm Firefox now releases every 4 weeks, it'll be too much work to keep up with new version while maintain compatibility with old versions, even if just to adjust new needles for new versions -- as you can see, other that this "URL unreachable" error, there are many needles mismatch already.
So if you are OK with removing this test, please go ahead.
- Status changed from New to Resolved
This testcases is unmaintained and was added to the jobgroup "development". I close this ticket. If somebody wants to pcik up the testcase again it needs a complete review.
- Status changed from Resolved to New
tests that are in the "test development" job group still take resources and should be worked on, or disabled from schedule and removed from code.
@zcjia as you are assigned to the ticket, please decide which steps you want to take.
- Status changed from New to Resolved
Closing.
I have removed this firefox-on-aarch64 test from TW development section.
Also available in: Atom
PDF