test February 2017

test@lists.fedoraproject.org

27 participants
130 discussions

NVIDIA Question
by David St.Clair 17 Jan '22

17 Jan '22

This may be a dumb question, but why can't Redhat distribute NVIDIA binary drivers? In NVIDIA's licence (http://www.nvidia.com/object/nv_swlicense.html) it says: "2.1.2 Linux Exception. Notwithstanding the foregoing terms of Section 2.1.1, SOFTWARE designed exclusively for use on the Linux operating system may be copied and redistributed, provided that the binary files thereof are not modified in any way (except for unzipping of compressed files)." So, what's keeping RedHat from putting the drivers in the distribution? If it's a GPL thing, would it be easy to just download it during installation or at least give the option to the user? Thanks, -- David St.Clair dstclair(a)cs.wcu.edu

10 20

Mouse goes crazy
by Jonathan Villa 17 Jan '22

17 Jan '22

Ok, I have had Yarrow working well for a while now, but yesterday I started experiencing some odd issues with my mouse. All of a sudden it stops working correctly. The only thing that seems to fix is to kill X and run mouse-test, then restart. Any ideas? Also, I have FC 1 running on a desktop which is hooked up to a KVM switch. Whenever I go to another PC, and return, the same thing happens, the mouse goes crazy. ???

8 7

F24 beta virt-install with kickstart fails
by Jos Vos 03 Jul '18

03 Jul '18

Hi, Did anyone succeed in virt-install'ing F24 beta using kickstart (on CentOS 6 host, if that matters)? I see lots of warnings (dracut-initqueue), then the console goes into a slowly filling bar at the bottom (plymouthd!?), then I see lots of "No space left on device" errors, then a dracut emergency shell is started. The generated rdsosreport.txt contains 34284 lines... FWIW, when *not* using kickstart I can install F24 beta on the same system with virt-install fine. Thx, -- -- Jos Vos <jos(a)xos.nl> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204

5 7

Criteria proposal: remove media part of release notes criterion
by Adam Williamson 26 Oct '17

26 Oct '17

Per https://fedorahosted.org/fedora-qa/ticket/471 and https://bugzilla.redhat.com/show_bug.cgi?id=1221920 , it seems we no longer want to require release notes to be present on all media. For simplicity's sake, I suggest we simply remove the media section of the criterion entirely. We could I suppose require that media include some kind of pointer to the release notes, but this seems difficult in the case of e.g. cloud images. Anyone have comments, alternative proposals? Thanks! For the record, the criterion is https://fedoraproject.org/wiki/Fedora_ 23_Final_Release_Criteria#Release_notes : "The final branded release notes must be present on release-blocking images and the appropriately versioned generic release notes must be available in the release repository." I propose amending it to: "The final branded and generic release notes must be present in the release repository." -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

3 10

Validation test proposal: mediawriter testing table
by Adam Williamson 24 Apr '17

24 Apr '17

Hi folks! So I finally got around to that 'think about USB test coverage' item that's been on my todo list forever. I propose we add a table to the Installation Validation page. The purpose is simply to check that writing images is working with mediawriter in the major supported environments: Windows, macOS , and the supported stable Fedora releases. So it could just look like this: Windows macOS Fedora 24 Fedora 25 QA:Testcase_USB_fmw with the intent being that we at least check that writing any one release blocking image with mediawriter in each environment. We could split Windows into 7, 8 and 10 or something, but not sure if it's really necessary... Thoughts? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

8 30

Release validation testers: a question
by Adam Williamson 11 Mar '17

11 Mar '17

Hi folks! I've got a question for everyone who helps out with release validation testing. It's related to the project to build a new system for submitting those results. We have a ticket for designing that system: https://pagure.io/design/issue/483 and as part of the discussion there, we're wondering something. Given that it's part of the new design that there's some kind of step where you specify which particular image you're testing, does it make more sense to you if you choose things in this order: 1. Pick a test to run 2. Pick an image to run the test on Or this order: 1. Pick an image to test 2. Pick a test to run on the image ? It's pretty important to the design approach. Thanks! (Please do feel free to read the ticket and mention any other thoughts you have on the design, too.) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

10 10

Introduction: Raymond Chung
by Yongsub Chung 07 Mar '17

07 Mar '17

First of all, Thank you for making Fedora Linux great. And, I am sure the QA team's contribution is essential to keep Fedora in high quality distribution. My name is Raymond Chung, and I have been in the industry around 15 years, but I still feel that I don't know enough. I used Linux since I was in college. I started with RedHat 5.5. I used it through Fedora 3, and switched to Gentoo, and FreeBSD, and, Ubuntu, and settled back to Fedora since Fedora 17, (I guess). My best interest is Kernel testing. Whenever I run into a kernel issue, such as driver, or performance, I couldn't solve efficiently, or basically give up. I want to know more about kernel, and recently joining QA team might be a good way to get more experience with kernel. Outside of working with computer, I play music. I love rock music, but jazz and classical are my interests, too. Feel free to reach me. I am glad to be part of QA team. -Ray

3 4

Introduction
by Anna Klimova 07 Mar '17

07 Mar '17

Hello everyone, My name is Anna. I've been a casual linux user for the past 10 years and I think it's about time to know how it works inside. Hope I can help with testing.

3 4

New automated test coverage: openQA tests of critical path updates
by Adam Williamson 07 Mar '17

07 Mar '17

Hi folks! I am currently rolling out some changes to the Fedora openQA deployment which enable a new testing workflow. From now on, a subset of openQA tests should be run automatically on every critpath update, both on initial submission and on any edit of the update. For the next little while, at least, this won't be incredibly visible. openQA sends out fedmsgs for all tests, so you can sign up for FMN notifications to learn about these results. They'll also be discoverable from the openQA web UI - https://openqa.fedoraproject.org . The results are also being forwarded to ResultsDB, so they'll be visible via ResultsDB API queries and the ResultsDB web UI. But for now, that's it...I think. Our intent is to set up the necessary bits so that these results will show up in the Bodhi web UI alongside the results for relevant Taskotron tests. There's an outside possibility that Bodhi is actually already set up to find these results in ResultsDB, in which case they'll just suddenly start showing up in Bodhi - we should know about that soon enough. :) But most likely Bodhi will need a bit of a tweak to find them. This is probably a good thing, because we need to let the tests run for a while to find out how reliable they are, and if there's an unacceptable number of false negatives/positives. Once we have some info on that and are happy that we can get things sufficiently reliable for the results to be useful, we'll hook up the Bodhi integration. The tests that are run are most of the tests that, on the 'compose test' workflow, get run on the Server DVD and Workstation Live images after installation. Between them they do a decent job of covering basic system functionality. They also cover FreeIPA server and client setup, and Workstation browser (Firefox) and terminal functionality. So hopefully, if your critpath update completely breaks one of those basic workflows, you'll find out about it before pushing it stable. At present it looks like the Workstation tests may sometimes fail simply because the base install gets stuck during boot for some reason; I'm going to look into that this week. In testing so far the Server tests seem fairly reliable, but I want to gather data from a few days worth of test runs to see how those look. Once we start sending results to Bodhi, I'll try and write up some basic instructions on how to interpret and debug openQA test results; QA folks will also be available in IRC and by email for help with this, of course. You can see sample runs on Server: https://openqa.stg.fedoraproject.org/tests/overview?groupid=1&build=FEDORA-… and Workstation: https://openqa.stg.fedoraproject.org/tests/overview?version=25&distri=fedor… the 'desktop_notifications_live' failure is a stale bit of data - that test isn't actually run any more because obviously it makes no sense in this context, but because it got run one time in early development, openQA continues to show it for that update (it won't show for any *other* update). The `desktop_update_graphical` fail is a good example of the kind of issue I'll have to look into this week: it seems to have failed because of an intermittent crasher bug in PackageKit, rather than an issue in the update. We'll have to look at skipping known- unreliable tests, or marking them somehow so you know the deal in Bodhi, or automatically re-running them, or things along those lines. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 1

F25 much more worse then F24, I hope F26 will be better
by Joerg Lechner 02 Mar '17

02 Mar '17

Hi, - last dnf update took far too much time - shutdown process not tolerable, takes too much time. - usb connection erroneous. i.e. after copying to flash medium or external disk connected by an usb adapter in most trials, when I try to eject the usb connected medium, there - after a copying process is finished a long time ago - comes the message "usb medium in use", this for ever. Also after shutdown of F25 in some cases I had to repair the usb connected medium with a new partition table. Things like that are not nice. Conclusion: I use F24 and if F26 will be better switch to F26 and omit F25. Kind regards

5 8

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test February 2017