# Fedora Quality Assurance Meeting
# Date: 2014-09-18
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
It's time again for another QA meeting! It's probably going to be quick, the
major and maybe only
# F21 Blocker Review meeting
# Date: 2014-08-20
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net
It's the time again for another blocker bug meeting, and it's happening today!
At the moment there are 3 proposed blockers and 1 proposed freeze
==
#fedora-blocker-review: F21-blocker-review
==
Meeting started by kparal at 16:00:37 UTC. The full logs are available
at
==
#fedora-meeting: Fedora QA meeting
==
Meeting started by kparal at 15:02:27 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2014-09-01/fedora-qa.2014-09-01-15.02.log.html
.
Meeting summary
Hmm, so the subject should have read Fedora QA Meeting Minutes, of course.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
# F21 Blocker Review meeting
# Date: 2014-09-03
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net
Greetings testers and developers! It's time again for another blocker review
meeting!
Currently there are 6 proposed blockers a 1 proposed freeze
==
#fedora-blocker-review: F21-blocker-review
==
Meeting started by kparal at 16:01:12 UTC. The full logs are available
at
Hi.
There is planned Fedora testday for new feature:
*** Cockpit ***
It is new web MonitoringManagement interface (system, services,
journal, network, storage, containers, users)
http://cockpit-project.org/
When: 2014-09-16
Where:
If I knew why someone thought 21_Alpha_TC6 was better than F21a-TC1 and
21-Alpha-TC3 I could do better. I never put underscores or whitespace in
filenames or directory names. Names of downloads that do either get trashed
or renamed. What's wrong with 21AlphaTC6, kdeRuntimeLibs or
, the best idea would be to add something like .composeinfo file
inside the directory, which would contain all the metadata in a
ini-style or json-style syntax.
can it please at least be the same syntax as *either* buildstamp *or*
treeinfo ? I'm sure there's a good reason why we have
In the base installation matrix
https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_RC1_Base#Test_Matrix
we have this test case:
https://fedoraproject.org/wiki/QA:Testcase_base_startup
It it is marked as Alpha in the matrix. However, it depends on disk
encryption, which is a Beta
Date: Thu, 18 Sep 2014 06:42:07 -0400
From: kpa...@redhat.com
To: test@lists.fedoraproject.org
Subject: problems with QA:Testcase_base_startup
In the base installation matrix
https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_RC1_Base#Test_Matrix
we have this test case:
Well, I set out this morning to move the rescue mode test case from
Alpha to Beta and somehow wound up doing this instead.
Opening a release validation test page 'template', copy 'n' pasting the
contents into a new page, and hand-editing bits until your eyes glaze
over? That's the old
Hi Guys,
I've been sitting on this one for a while as I was just hoping it would
get fixed, but after trying the 21 alpha release its still an issue so I
thought I'd try get it some attention.
Any I have an issue that makes Fedora 20 and 21 unusable with my Radeon
6670. As soon as fedora
I've also tried to find reports of people having the same issue but
haven't found any. The card is a PowerColor Radeon 6670 1GB.
I realized we have Radeon 6570 in our office. I booted F21 Live a left it
running for 2 hours - no artifacts, no freezes, no error messages in kernel log.
--
test
Hey, folks!
I spent some time today fiddling around with the installation validation
matrix. I haven't applied the changes to Beta TC1 to give us some time
to review/tweak them, but they're in the template:
https://fedoraproject.org/wiki/Template:Installation_test_matrix
I like the new
Hello,
I am emailing in regards of a bug that I have detected with Fedora 21 Alpha.
Right off the bat I have noticed during the installation that when you are
creating the root password it continuously says that the passwords do not
match no matter what passwords I put in. I had to leave it
Error mounting /dev/sda4 at /run/media/joerg/Acer: Command-line `mount -t
ntfs -o
uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177
/dev/sda4 /run/media/joerg/Acer' exited with non-zero exit status 14:
Windows is hibernated, refused to mount.
Failed to mount '/dev/sda4':
My Google foo is getting me nowhere fast. I want to follow-up on
https://bugs.freedesktop.org/show_bug.cgi?id=85016#c4 but need an
xorg-x11-drv-intel git 3.0.0 version to do it. How can I find out if and
where such an rpm package exists for F21 and/or F22?
$ pkgwat releases xorg-x11-drv-intel
As per the Fedora 21 schedule [1], Fedora 21 Beta Release Candidate 1
(RC1) is now available for testing. Content information, including
changes, can be found at
https://fedorahosted.org/rel-eng/ticket/6010#comment:11 . Please see the
following pages for download links (including delta ISOs)
On Fri, Oct 24, 2014 at 9:31 AM, Kamil Paral kpa...@redhat.com wrote:
As per the Fedora 21 schedule [1], Fedora 21 Beta Release Candidate 1
(RC1) is now available for testing. Content information, including
changes, can be found at
https://fedorahosted.org/rel-eng/ticket/6010#comment:11
I have a proposal regarding installation matrix [1] related to environments.
Adam did a truly stellar job in his latest results table restructuring, he
eliminated a lot of duplicated testing and simplified the tables a lot (for
example, there's no point in testing additional HTTP repos in
1. Testcase_Anaconda_User_Interface_Basic_Video_Driver was changed to
a generic x86 test. In this case, it is problematic, because BIOS and
UEFI fallback video driver are completely different code paths. I have
a personal experience from that past when one of those worked and the
other
===
When installing to a system containing an existing installation of
either the same Fedora release or either of the two previous releases,
the installer must configure the new installation's bootloader such that
it can successfully boot the existing installation.
[Footnote]
If you want my guess, I guess I'd suggest we make VNC non-arch-specific,
keep serial console split ARM/x86, and make text non-interface-specific,
it seems like as long as you get a console at all, that ought to work.
Adjusted in
In relation to my video problems under 21 Beta
is there ANY way to deal with the locked up desktop other
than hitting the power switch? When it's locked-up, ctrl-alt-F
keys don't work..ctrl-alt-del doesn't work...and the last resort
alt-sysreq doesn't work. I am really afraid of totally
Hi,
I'd like add https://bugzilla.redhat.com/show_bug.cgi?id=1088619
as blocker to release 21 . Please read last comments #95 still #101
Hello, you can always do that using
https://qa.fedoraproject.org/blockerbugs/propose_bug
However, that bug is quite a mess. When proposing as a blocker,
I notice that TC2 is built with anaconda-21-48.14-1 so I assume there
are other packages updated also. This anaconda package (and I assume
the others) are not currently on the mirrors. When can we expect this
packages to appear on the mirrors? Is 24 hours a reasonable expectation?
It's in
I maintain local mirrors for the actgive versions I use here via rsync.
But now it is past time for me to test F21 x86 on a notebook I have
assigned to this task (a Lenovo x120e with a clean SSD). Where do I get
the OS and updates? If I pull them down, and build an dvd of the iso
netinstall,
Eh, it's OK, just seems slightly inconsistent to be specifying
environment 'horizontally' for some tests and 'vertically' for others.
Why not just another table with the two tests that use the GUI/text
distinction and those as the columns?
Hmm, I guess there were two reasons:
1. I didn't
On Thu, 2014-11-13 at 05:42 -0500, Kamil Paral wrote:
If I have understood the remaining problem well when skimming that
bug, there is a delay before rebooting/shutting down. I agree that's
inconvenient, but it doesn't seem to violate any of our criteria.
On my system shutdown often just
On 11/23/2014 02:10 PM, Vadim Rutkovsky wrote:
Hi,
Orion Poplawski or...@cora.nwra.com wrote:
Can taskotron run rpmlint on packages? Seems like this would be a
useful thing to get into place.
It does already - see
On Fedora 21, looks like there's a new systemd unit fstrim.timer
which is disabled by default. Easily enabled with 'systemctl enable
fstrim.timer' and will issue trim for all mounted trim supporting
volumes once per week.
Shiny!
Thanks for info.
--
test mailing list
Hello,
was anyone else hit by this bug?
https://bugzilla.redhat.com/show_bug.cgi?id=702650
Basically if you have an encrypted partition that is not unlocked as soon as
root partition is, but only later in the boot process, the password prompt is
stuck and you can't input any text.
Thanks,
As per the Fedora 15 schedule [1], Fedora 15 Final Release Candidate 1
(RC1) is now available for testing. Please see the following pages for
download links and testing instructions.
Installation:
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
Desktop:
AutoQA 0.5.0 has just been released and deployed. Package maintainers will see
some notable changes. Please read the whole description here:
http://kparal.wordpress.com/2011/06/29/autoqa-0-5-0-released/
Comments welcome.
Kamil
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
There is an Independence Day Holiday in the USA today, I don't expect our QA
meeting [1] to be happening today. But if you have any updates, feel free to
provide them here in the mailing list.
Thanks,
Kamil
[1] https://fedoraproject.org/wiki/QA/Meetings
--
test mailing list
Honestly, I don't know. On the one hand, I have some scripts that
are good for fedora
QE in general. For example, the shell error test...why would anyone
purposely write
shell script that does not work? This can always be fixed before a
release. Some tests
are still under development
Please read:
https://kparal.wordpress.com/2011/08/05/autoqa-0-6-released/
Kamil
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Hi,
Anybody sees this too:
After downloading the F16/TC2 x86_64 desktop ISO and burning it, I
booted from the CD media: No GDM after boot, the last messsage on the
console is Started D-Bus System Message Bus. The ribbon on the
buttom
of the screen is completely white (this took much
I don't know how Steve's tests behave, but:
1. We can't run destructive tests (uninstalling packages, deleting
system
files, stopping services).
All are read only. I have several more that do stuff like start each
servoce and scan
the audit logs for AVCS, then stop all services. But
Also, need a tag for 16-Alpha in bugzilla,
for auto reporting of tracebacks.
Not sure what you mean by that.
That's this one:
https://bugzilla.redhat.com/show_bug.cgi?id=730887
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://bugzilla.redhat.com/show_bug.cgi?id=727814
--- Comment #8 from Tim Flink tfl...@redhat.com 2011-09-01 13:18:54 EDT ---
Discussed in the 2011-08-26 blocker review meeting. Rejected as a Fedora 16
beta blocker because it doesn't violate any of the beta release criteria [1].
Accepted
WHAT: Fedora QA Meeting
WHEN: 15:00 UTC (11:00 EDT, 08:00 PDT)
WHERE: #fedora-meeting
So it's meeting time again on Monday, except that it's a vacation in
both Canada and the U.S., so myself and Tim Flink, and perhaps some of
our North American community members, won't be present. If
WHAT: Fedora QA Meeting
WHEN: 15:00 UTC (11:00 EDT, 08:00 PDT)
WHERE: #fedora-meeting
So it's meeting time again on Monday, except that it's a vacation in
both Canada and the U.S., so myself and Tim Flink, and perhaps some
of
our North American community members, won't be present.
AutoQA:
1. We will decommission initscripts test, because Fedora 14 EOL is
nearing and systemd replaced sysvinit in later releases.
systemd may have replaced upstart, but many packages are still using
sysv-style init scripts, not systemd-native ones...
That might be true, but service
It means if you're doing a fresh install, you've got to format
wherever
/ is going. You can't install over top of an existing /. Is that
what
you thought it meant?
- Chris
I imagine this could be very inconvenient for me when switching distributions.
I always have / and /home on the
- Chen Gang-Cuble fou...@sina.com.cn wrote:
Hi:
I'm a Chinese man, I'm a software engineer. Familiar with C/C++. I
have
about 7 years experience on software developing.
I'm new to Linux. I have read a few books before, but just began to
use
it a few days ago. I have just learned
- Michael Schwendt mschwe...@gmail.com wrote:
$ yum repolist
[...]
updates-testingFedora 14 - i386 - Test Updates
4,079
4079 test updates?
# yum repolist --enablerepo=updates-testing
fedora Fedora 14 - x86_64
- Kevin Fenzi ke...@scrye.com wrote:
* have a way to get interested testers notified on bodhi updates for
packages
they care about.
I think that's this one:
https://fedorahosted.org/bodhi/ticket/339
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
Today I discovered that I cannot use 'scp' to transfer files when the remote
site has only 'openssh-server' package installed. I can ssh to it, but I
can't scp to it. I spits this error message:
bash: scp: command not found
lost connection
When I install 'openssh-clients' package on the remote
- Original Message -
# Fedora Quality Assurance Meeting
# Date: 2011-02-07
# Time: 16:00 UTC (11:00 EST, 17:00 CET) [1]
# Location: #fedora-meeting on irc.freenode.net
Greetings folks,
This is a reminder that we have a QA meeting scheduled every Monday at
16:00UTC. If you are
- Original Message -
On 02/07/2011 10:13 AM, Kamil Paral wrote:
- Original Message -
# Fedora Quality Assurance Meeting
# Date: 2011-02-07
# Time: 16:00 UTC (11:00 EST, 17:00 CET) [1]
# Location: #fedora-meeting on irc.freenode.net
Greetings folks
- Original Message -
On 02/07/2011 10:29 AM, Kamil Paral wrote:
Well, for desktop validation it is clear that fallback mode creates
quite different environment from gnome-shell. For installation
testing
it is true that mostly we test anaconda, but a lot of our test cases
- Original Message -
I'm hitting an issue with netinstall and DVD install on F15 i386
(tried
TC2, 20110220 nightly) that I can't reproduce on a VM. I'm going to
try
another physical machine to verify that it isn't HW specific but I was
wondering if anyone else has seen it:
I get
- Original Message -
Hey, all. Can anyone who was hit by the bug of GNOME failing to run
unless they removed at-spi2* please test this update?
https://admin.fedoraproject.org/updates/gsettings-desktop-schemas-0.1.7-2.fc15
for me, it fixes the issue. The best way to test is to
- Original Message -
On Mon, 2011-03-21 at 09:12 -0400, James Laska wrote:
# Fedora Quality Assurance Meeting
# Date: 2011-03-21
# Time: 15:00 UTC (11:00 EDT, 17:00 CET) [1]
# Location: #fedora-meeting on irc.freenode.net
Note: Europe still didn't move to summer time, so it
Is it OK if I change the time on the Fedora meeting page to match
this?
I had just checked and the start time was still listed as 1600.
Just hit Refresh or clean the cache. It was already updated.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
Fedora QA holds Test Day regarding ABRT 2 and Retrace Server
on March 31:
https://fedoraproject.org/wiki/Test_Day:2011-03-31_ABRT_Retrace_Server
This test day will focus on Retrace Server feature [1] in
Fedora 15 as well as ABRT 2.0. Refreshed and bright new
test cases are prepared for your
- Original Message -
Hi guys
Gnome release team has rescheduled gnome 3 for September 2011
(http://www.gnome.org/press/releases/2011-04-gnome-3.0-rescheduled.html)
What about in f 15 ?
I suspect
http://en.wikipedia.org/wiki/April_Fools'_Day
--
test mailing list
Previously I posted instructions for temporarily upgrading the xz
compression on a F14 box to be able to work with deltaisos for F15 and
later:
http://lists.fedoraproject.org/pipermail/test/2011-February/097009.html
Michael Young's method at
How is Gnome 3 going to work with VNC, which does not do 3D?
I think you can log in into Gnome Shell, start VNC, and connect from another
machine to view/control the desktop.
But you can't start the session over VNC on a client without 3D hardware
support, that will fall back to Gnome 2.
--
If you have a moment, and spare hardware/guest, please add karma
feedback to:
*
https://admin.fedoraproject.org/updates/anaconda-15.26-1.fc15
*
https://admin.fedoraproject.org/updates/filesystem-2.4.40-1.fc15
*
2. The system won't boot without selinux=0.
3. With selinux=0 the system boots, but firstboot crashes on last
page (send hardware profile) and thus restarts on every boot.
Looks like we'll need a bug against firstboot. Is there a firstboot
traceback file in /tmp ?
Interesting.
Please read:
http://kparal.wordpress.com/2011/04/29/autoqa-0-4-7-released/
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Would it be too much to have Anaconda check for the
repodata files it wants before scribbling on the hard drive(s)?
--
Chuck Forsberg WA7KGX N2469R c...@omen.com www.omen.com
Developer of Industrial ZMODEM(Tm) for Embedded Applications
Omen Technology Inc The High
I imagine this could be very inconvenient for me when switching
distributions. I always have / and /home on the same partition. If
I
want hypothetically to go from let's say Ubuntu to Fedora, I delete
all files except /home and then select that partition for /. If you
force me to
Um, yes it is? The only concern I ever had for my layout is
whether the next distro installer would be smart enough to
let me skip formatting of the / partition.
I belive that ...
you talk about the action itself
Kamil talks about *allowing* the action
Speaking for myself: if the
Taking into consideration the list feedback, and some issues that
came
up at the meeting, we agreed to accept this substantially modified
text
during the blocker review meeting today:
All critical path actions on release-blocking desktop environments
should correctly display all
Dennis,
you replied to the email into the test-list. You have to reply to this ticket
itself at:
https://fedorahosted.org/fedora-qa/ticket/246
- Original Message -
Hi Mcloaked
Thanks for taking me on as you Padawan
I read though the wiki, and I understand it, still I would like
On Mon, 2011-10-24 at 08:41 -0400, Kamil Paral wrote:
All critical path actions on release-blocking desktop
environments
should correctly display all sufficiently complete translations
available for use
As usual I'm providing feedback only after it has been agreed on.
Sorry
In that case everything's perfect and I just misunderstood it.
What confused me most is probably the phrase all sufficiently
complete translations. I am not sure about its purpose. Does it
mean
that if German has 90% complete GNOME translations, but Nautilus
(even
though fully
Quick question,
how do rel-eng guys know which updates are OK to push to stable during freeze
and which are not? For example we have the final freeze now. Some packages like
this:
https://admin.fedoraproject.org/updates/FEDORA-2011-14932
are needed to be pushed to stable repo, so they have an
WHAT: Fedora QA Meeting
WHEN: 15:00 UTC (12:00 EST, 09:00 PST)
WHERE: #fedora-meeting
It's meeting time again! It's the first meeting of the post-Fedora 16
era, so time to dust off anything you've been sitting on through the
release crunch. Also note that clocks went back in North America
On Thu, 27 Oct 2011 07:59:12 -0400 (EDT)
Kamil Paral kpa...@redhat.com wrote:
Quick question,
how do rel-eng guys know which updates are OK to push to stable
during freeze and which are not? For example we have the final
freeze
now. Some packages like this:
https
Hi,
I'm trying to blank *uncompletely burned* rewritable CD's with
brasero:
brasero waits until such a CD is inserted, but nothing happens if I
insert the CD (Brasero does not recognize resp. has no access to such
a
CD in the CD drive).
I'm using nautilus as file manager inside
For years I have used /etc/rc.d/rc.local for this and that
including launching VNC screens.
[root@gpib rc.d]# cat rc.local
su -l caf -c vncserver
su -l root -c vncserver
date | mail -s boot c...@omen.com
But it seems 32 bit Verne doesn't like it:
Starting Login
On Tue, 2011-10-11 at 18:44 -0700, Adam Williamson wrote:
Hey, folks. So, currently the Beta criteria state:
The installer must be able to use all kickstart delivery methods
This is probably over-ambitious for Beta. We have some pretty odd
kickstart delivery methods:
A straightforward release criterion proposal: we should have a
criterion
just to specify that the anaconda betanag screen (and any others we
put
in) should be removed for final. Right now this is one of those
things
that's just obvious but that we ought to write down somewhere. How
about,
On Wed, Nov 30, 2011 at 02:51, Andre Robatino
robat...@fedoraproject.org wrote:
17Alpha
17AlphaNTH
17Beta
17BetaNTH
17Final (or alternatively 17)
17FinalNTH (or alternatively 17NTH)
Why not:
17AlphaBlocker
17AlphaNTH
17BetaBlocker
17BetaNTH
17FinalBlocker
17FinalNTH
...
https://kparal.wordpress.com/2011/11/29/autoqa-0-7-released/
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
On Fri, Feb 3, 2012 at 5:38 AM, Jens Petersen peter...@redhat.com
wrote:
I noticed that my recent package updates posted to Bodhi
don't seem to have received autoqa testing.
eg
https://admin.fedoraproject.org/updates/FEDORA-2012-0762/redhat-rpm-config-9.1.0-16.fc15
I am not sure
On Fri, Feb 3, 2012 at 5:38 AM, Jens Petersen peter...@redhat.com
wrote:
I noticed that my recent package updates posted to Bodhi
don't seem to have received autoqa testing.
eg
https://admin.fedoraproject.org/updates/FEDORA-2012-0762/redhat-rpm-config-9.1.0-16.fc15
I am
Several tests in the install test matrix require the above option,
but when
anaconda attempts to start after downloading the file, I get the
text-based
traceback (not the expected GUI error) at
http://robatino.fedorapeople.org/traceback.xwd.gz
Did you already reported the bug against
Kamil Paral kparal at redhat.com writes:
Several tests in the install test matrix require the above
option,
but when
anaconda attempts to start after downloading the file, I get the
text-based
traceback (not the expected GUI error) at
http://robatino.fedorapeople.org
Kamil Paral kparal at redhat.com writes:
Several tests in the install test matrix require the above
option,
but when
anaconda attempts to start after downloading the file, I get
the
text-based
traceback (not the expected GUI error) at
http
Any idea on Xfce?
http://dl.fedoraproject.org/pub/alt/stage/17-Alpha.TC2/Live/i686/
https://fedorahosted.org/rel-eng/ticket/5054#comment:8
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
2. Ask Anaconda team to provide us with their official and
supported solution.
After inspecting updates.img, there is a lot of code copied from
(some old version of) anaconda. That doesn't seem to me as a good
solution, because we might get completely unrelated problems in the
PXEBOOT fails on a Gigabyte GA-P55A-UD3 and on a NFORCEE6M-A
with a kernel panic about no or empty root.
https://bugzilla.redhat.com/show_bug.cgi?id=785815
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
The new feature is implemented and should be part of the next
anaconda release
(17.9 probably). We just use
'traceback' boot option. Once a new compose with the new anaconda
is ready,
I'll re-write the test cases.
The 'traceback' boot option does NOT appear to be implemented in 17
QA:Testcase_Anaconda_save_traceback_to_remote_system
QA:Testcase_Anaconda_save_traceback_to_bugzilla (Alpha)
QA:Testcase_Anaconda_save_traceback_to_disk (Alpha)
QA:Testcase_Anaconda_traceback_debug_mode
Test cases updated. However, for save_traceback_to_bugzilla we used to have
the option to
Kamil Paral kparal at redhat.com writes:
QA:Testcase_Anaconda_save_traceback_to_remote_system
QA:Testcase_Anaconda_save_traceback_to_bugzilla (Alpha)
QA:Testcase_Anaconda_save_traceback_to_disk (Alpha)
QA:Testcase_Anaconda_traceback_debug_mode
I have tried Alpha RC4 (anaconda
Almost all FC17 kernels are debug kernels. A quick way to tell if
you're
using one is:
grep -i CONFIG_ACPI_DEBUG /boot/config-`uname -r`
'not set' = release kernel. 'Y' = debug kernel.
The kernel team is building one kernel per upstream kernel release (I
think that's it) as 'release'
I copied a squashfs.img to the the tftpd directory along with
vmlinuz
and initrd.img.
Pxeboot fails claiming it can't handle root=squashfs.img.
V'ger does not know.
prompt 1
default linux
timeout 100
label linux
kernel vmlinuz
append initrd=initrd.img
We have these two test cases:
https://fedoraproject.org/wiki/QA:Testcase_Install_to_Current_KVM
https://fedoraproject.org/wiki/QA:Testcase_Install_to_Previous_KVM
In the test results matrix [1] they are split according to the architecture.
Now, does it talk about HOST architecture or GUEST
Hey, folks. I've drafted up my proposal for adding EFI testing to the
installation matrix here:
https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_Fedora_17_Install_Results_Template
Compare to the current:
https://fedoraproject.org/wiki/QA:Fedora_17_Install_Results_Template
It's
Because there are some objections for serial interface being in final
criterion, I'd like to start discussion again. There was discussion
on
blocker bug meeting [1] (17:40) and it didn't end with unanimous
decision. So, let the flame war begin. Do you want serial interface
in
beta
There will be a GNOME Shell and Extensions Test Day on Thursday!
https://fedoraproject.org/wiki/Test_Day:2012-03-15_Gnome_Shell_and_Extensions
Here's an introduction from Vitezslav Humpa, who's in charge of this event from
QA perspective:
While Fedora 17 Test Day cycle is starting to take
Hey, folks.
So I've been doing the TC / RC requests for a while, and James did
them
before that. It occurred to me that while it's theoretically
'obvious'
how this happens, and mostly defined by the release validation
process,
in practice it's probably worth having an explicit SOP to
If certain wifi cards (using certain kernel module) don't work in F17, should I
propose that as a blocker? I'm not sure about that. Other wifi cards work.
https://bugzilla.redhat.com/show_bug.cgi?id=802106
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
1 - 100 of 1134 matches
Mail list logo
