From Fedora Project Wiki
- | style="color: #4d4d93" | Nah just had a meeting that ran 2 hours longer than expected. ...36 KB (4,156 words) - 08:44, 18 September 2016
- ...ref>All regression tests passed, except libhugetlbfs which was skipped. I ran the tests with sudo. Performance tests passed, too.</ref> ...23 KB (3,052 words) - 10:39, 16 April 2019
- | {{result|pass}}<ref>Both machines ran default and performance tests, which worked fine. No other problems spotted ...g after "Latency measurements" displayed in the terminal. The default test ran successfully.</ref> ...47 KB (6,388 words) - 11:55, 17 April 2023
- ...the benchmarks can be found in the readme of the fpbench repository as we ran into formatting issues trying to add the results to the wiki. ...22 KB (3,500 words) - 22:50, 6 January 2023
- ...nsaction has completed, it should succeed. If the other process is one you ran yourself, it should be easy to identify, but it may be harder if it is an a ...20 KB (3,205 words) - 01:31, 25 September 2019
- ...ments. Responding to a request from TomCallaway for specifics, KevinKofler ran a quick <code>repoquery --whatrequires autodownloader</code> and listed[14] I ran across this article[1] this week. it's not too shabby explaining how SELi ...41 KB (5,924 words) - 21:09, 20 September 2016
- | {{result|pass}}<ref>Ran both default and performance tests and both passed. For the vulnerabilities | {{result|pass}}<ref>1. Ran with nouveau ...48 KB (6,573 words) - 12:10, 17 April 2023
- | {{result|pass}}<ref>Successfully ran scrubs, defragments (including enabling/disabling compression on the filesy ...35 KB (4,438 words) - 15:31, 25 August 2020
- ...2 machine and it installed OK. did an upgrade on ppc64 (G5) and ran into the /boot issue</td><td class="time"><a href="#t10:11:44" class="time" ...64 KB (10,163 words) - 15:11, 18 September 2016
- ...the system would install and boot fine but would break as soon as the user ran 'yum update', that may well be covered by these criteria.|headerstyle=backg ...33 KB (4,559 words) - 22:34, 1 August 2017
- * Reviving Bug Days (this was missed as we ran out of time, but will be on the agenda for the next meeting.) ...46 KB (5,419 words) - 07:53, 18 September 2016
- ...ssarily know that I found any "failures" in terms of QA ... I just think I ran into issues with hardware that's older and likely wasn't used in other test ...40 KB (4,890 words) - 09:05, 18 September 2016
- | style="color: #407a40" | but he just ran in to the very reason we stopped :) ...36 KB (4,769 words) - 08:37, 18 September 2016
- ...is required, it would likely be easier to have a plugin (if required) that ran things in a temp dir kind of how we do with libtaskotron today ...25 KB (3,909 words) - 16:30, 18 June 2017
- ...the system would install and boot fine but would break as soon as the user ran 'yum update', that may well be covered by these criteria.|headerstyle=backg ...33 KB (4,701 words) - 18:43, 11 June 2015
- ...the system would install and boot fine but would break as soon as the user ran 'yum update', that may well be covered by these criteria.|headerstyle=backg ...34 KB (4,798 words) - 21:14, 23 March 2016
- ...the system would install and boot fine but would break as soon as the user ran 'yum update', that may well be covered by these criteria.|headerstyle=backg ...34 KB (4,798 words) - 19:28, 27 June 2016
- <tr><td class="other" colspan="3">[Mon Aug 4 2008] [18:43:13] <saahil>i ran rpmlint on the spec file</td></tr> ...3">[Mon Aug 4 2008] [19:54:38] <franciscod>mether: okay.. anyway.. I ran the rpmbuild..</td></tr> ...145 KB (21,818 words) - 10:25, 18 September 2016
- ...the system would install and boot fine but would break as soon as the user ran 'yum update', that may well be covered by these criteria.|headerstyle=backg ...35 KB (4,877 words) - 23:28, 18 April 2017
- ...the system would install and boot fine but would break as soon as the user ran 'yum update', that may well be covered by these criteria.|headerstyle=backg ...35 KB (4,938 words) - 01:45, 29 January 2016