#491: Fedora 25 i18n test day on 28th Sept
--+
Reporter: pravins | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 25
Component: Test Day | Version:
Keywords:| Blocked By:
Blocki
#491: Fedora 25 i18n test day on 28th Sept
---+---
Reporter: pravins | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 25
Component: Test Day |Version:
Resolution:| Keywords:
Blocked
#491: Fedora 25 i18n test day on 28th Sept
---+---
Reporter: pravins | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 25
Component: Test Day |Version:
Resolution:| Keywords:
Blocked
Missing expected images:
Cloud_base raw-xz i386
Atomic raw-xz x86_64
Failed openQA tests: 8/93 (x86_64), 3/17 (i386), 1/2 (arm)
ID: 35180 Test: x86_64 Workstation-live-iso base_selinux
URL: https://openqa.fedoraproject.org/tests/35180
ID: 35181 Test: x86_64 Workstation-live-iso base_
Missing expected images:
Xfce raw-xz armhfp
Cloud_base raw-xz i386
Atomic raw-xz x86_64
Failed openQA tests: 3/93 (x86_64), 1/17 (i386), 1/2 (arm)
ID: 35302 Test: x86_64 Atomic-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/35302
ID: 35311 Test: arm Minimal-raw_
Missing expected images:
Cloud_base raw-xz i386
Atomic raw-xz x86_64
Failed openQA tests: 8/93 (x86_64), 3/17 (i386), 1/2 (arm)
ID: 35180 Test: x86_64 Workstation-live-iso base_selinux
URL: https://openqa.fedoraproject.org/tests/35180
ID: 35181 Test: x86_64 Workstation-live-iso base_
The page BugZappers/BugStatusWorkFlow displays the work flow which applies to a
Fedora bug. However, no policy is given about reopening a closed bug. At the
bottom of the page, the reader is referred to "A Bug's Life Cycle" for further
information. Here, we read
"CLOSED
This bug fix has been r
Hi folks
My name is Thirumalesh H S. I have been using linux for the past 2 years.
Recently I switched to Fedora 25 alpha release. I would like to be a part
of the QA team and contribute in making fedora better. I have taken initial
steps in creating an FAS account and requested to join Fedora QA
Prezado(a): Senhor(a)
Declaração
número: 23122921
O CPF cadastrado para
este email possui nova pendência financeira.
Pedimos que verifique para evitar a inclusão no Serasa e
(ou) SPC.
Segue abaixo o extrato de débitos para maiores
esclarecimentos.
Link par
The following Fedora 23 Security updates need testing:
Age URL
367 https://bodhi.fedoraproject.org/updates/FEDORA-2015-16240
nagios-4.0.8-1.fc23
325 https://bodhi.fedoraproject.org/updates/FEDORA-2015-81ded368fe
miniupnpc-1.9-6.fc23
298 https://bodhi.fedoraproject.org/updates/FEDORA-2
The following Fedora 24 Security updates need testing:
Age URL
44 https://bodhi.fedoraproject.org/updates/FEDORA-2016-32eaf0c41e
redis-3.2.3-1.fc24
27 https://bodhi.fedoraproject.org/updates/FEDORA-2016-0ef628998f
chicken-4.11.0-3.fc24
5 https://bodhi.fedoraproject.org/updates/FED
On Wed, 2016-09-21 at 18:40 +, Joachim Frieben wrote:
> The page BugZappers/BugStatusWorkFlow displays the work flow which
> applies to a Fedora bug. However, no policy is given about reopening
> a closed bug. At the bottom of the page, the reader is referred to "A
> Bug's Life Cycle" for furth
Hi Adam,
this bug I should possibly have routed to Anaconda and not to Dracut. Because
so far it's not possible to make a F25 build an an USB connected medium, in my
opinion this bug is blocking for Beta Final.
Kind regards
___
test mailing list -- tes
Unfortunately, I still ignore the current policy for reopening a closed bug, in
particular those resolved as ERRATA. The documentation page "BugStatusWorkFlow"
should get really amended in this respect.
___
test mailing list -- test@lists.fedoraproject.
14 matches
Mail list logo