Fedora Rawhide 20151106 compose check report

[Fedora compose checker]

Missing expected images:

Cloud disk raw i386
Cloud disk raw x86_64
Cloud_atomic disk raw x86_64
Generic boot i386
Generic boot x86_64

No images in this compose but not Rawhide 20151105

No images in Rawhide 20151105 but not this.
-- 
Mail generated by check-compose:
https://git.fedorahosted.org/cgit/fedora-qa.git/tree/check-compose
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Fw: new message

[Allen_Hillman]

Hey!

 

New message, please read 

 

allen_hill...@technologist.com

-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Did bugzilla's redirect checking get more strict in the last few days?

[Bruno Wolff III]

I am unable to login to bugzilla today and I think it is because the redirect 
test has gotten stricter but I am not sure. I saw this happen months ago 
with a direct bookmark, but I only had to try a second time. Now I keep 
getting sent back to unable to trust my login attempt page, so I think 
some new test got added.

--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Grub Error in F23 Release? Grub stops in OS selection for Windows for ever.

[Adam Williamson]

On Fri, 2015-11-06 at 01:15 -0500, Joerg Lechner wrote:
> Hi,
> to this problem  in Grub: "when I select Win 8.1, I can wait forever" 2 
> screenshots,
> current Grub code to start Win8.1 and current Grub code to start F23.
> Kind regards

You already got a reply, from Richard Ryniker, and it was correct. The
grub timeout is cancelled as soon as you hit any key, which obviously
means it applies only to the default entry.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net


-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [F24 Criteria Change] Cockpit Release Criteria

[Lars Seipel]

On Thu, Nov 05, 2015 at 11:10:30AM -0500, Máirín Duffy wrote:
> First, on browsers - according to the W3C's w3schools site, they see about
> 60-65% of visitors on Chrome and Firefox around 20-24%. IE is 3rd at around
> 6-8%. Other browser usage statistics reports seemed to have similar numbers.

Note that W3C is not affiliated with w3schools in any way.
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

rawhide report: 20151106 changes

[Fedora Rawhide Report]

Compose started at Fri Nov  6 05:15:03 UTC 2015
Broken deps for i386
--
[IQmol]
IQmol-2.3.0-9.fc24.i686 requires libboost_serialization.so.1.58.0
IQmol-2.3.0-9.fc24.i686 requires libboost_iostreams.so.1.58.0
IQmol-2.3.0-9.fc24.i686 requires libOpenMeshCore.so.3.2
[alliance]
alliance-5.0-40.20090901snap.fc22.i686 requires libXm.so.2
[eclipse-jbosstools]
eclipse-jbosstools-as-4.2.2-1.fc22.noarch requires 
osgi(org.eclipse.tm.terminal)
[fawkes]
fawkes-core-0.5.0-26.fc24.i686 requires libmicrohttpd.so.10
fawkes-plugin-player-0.5.0-26.fc24.i686 requires libgeos-3.4.2.so
fawkes-plugin-xmlrpc-0.5.0-26.fc24.i686 requires libmicrohttpd.so.10
[gcc-python-plugin]
gcc-python2-debug-plugin-0.14-4.fc23.i686 requires gcc = 0:5.1.1-4.fc23
gcc-python2-plugin-0.14-4.fc23.i686 requires gcc = 0:5.1.1-4.fc23
gcc-python3-debug-plugin-0.14-4.fc23.i686 requires gcc = 0:5.1.1-4.fc23
gcc-python3-plugin-0.14-4.fc23.i686 requires gcc = 0:5.1.1-4.fc23
[gnash]
1:gnash-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0
1:gnash-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0
1:gnash-0.8.10-19.fc24.i686 requires libboost_serialization.so.1.58.0
1:gnash-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0
1:gnash-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0
1:gnash-0.8.10-19.fc24.i686 requires libboost_date_time.so.1.58.0
1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0
1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0
1:gnash-cygnal-0.8.10-19.fc24.i686 requires 
libboost_serialization.so.1.58.0
1:gnash-cygnal-0.8.10-19.fc24.i686 requires 
libboost_program_options.so.1.58.0
1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0
1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_date_time.so.1.58.0
1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires 
libboost_thread.so.1.58.0
1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires 
libboost_system.so.1.58.0
1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires 
libboost_program_options.so.1.58.0
1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires 
libboost_iostreams.so.1.58.0
1:gnash-extension-fileio-0.8.10-19.fc24.i686 requires 
libboost_thread.so.1.58.0
1:gnash-extension-fileio-0.8.10-19.fc24.i686 requires 
libboost_system.so.1.58.0
1:gnash-extension-fileio-0.8.10-19.fc24.i686 requires 
libboost_program_options.so.1.58.0
1:gnash-extension-fileio-0.8.10-19.fc24.i686 requires 
libboost_iostreams.so.1.58.0
1:gnash-extension-lirc-0.8.10-19.fc24.i686 requires 
libboost_thread.so.1.58.0
1:gnash-extension-lirc-0.8.10-19.fc24.i686 requires 
libboost_system.so.1.58.0
1:gnash-extension-lirc-0.8.10-19.fc24.i686 requires 
libboost_program_options.so.1.58.0
1:gnash-extension-lirc-0.8.10-19.fc24.i686 requires 
libboost_iostreams.so.1.58.0
1:gnash-extension-mysql-0.8.10-19.fc24.i686 requires 
libboost_thread.so.1.58.0
1:gnash-extension-mysql-0.8.10-19.fc24.i686 requires 
libboost_system.so.1.58.0
1:gnash-extension-mysql-0.8.10-19.fc24.i686 requires 
libboost_program_options.so.1.58.0
1:gnash-extension-mysql-0.8.10-19.fc24.i686 requires 
libboost_iostreams.so.1.58.0
1:gnash-klash-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0
1:gnash-klash-0.8.10-19.fc24.i686 requires 
libboost_program_options.so.1.58.0
1:gnash-plugin-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0
1:python-gnash-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0
1:python-gnash-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0
1:python-gnash-0.8.10-19.fc24.i686 requires 
libboost_program_options.so.1.58.0
1:python-gnash-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0
[golang-github-kraman-libcontainer]
golang-github-kraman-libcontainer-devel-0-0.4.gitd700e5b.fc24.noarch 
requires golang(github.com/docker/docker/pkg/netlink)
[golang-github-kubernetes-heapster]
golang-github-kubernetes-heapster-devel-0.16.1-1.fc24.noarch requires 
golang(github.com/google/cadvisor/info/v1)
golang-github-kubernetes-heapster-devel-0.16.1-1.fc24.noarch requires 
golang(github.com/google/cadvisor/client)
golang-github-kubernetes-heapster-devel-0.16.1-1.fc24.noarch requires 
golang(github.com/coreos/fleet/schema)
golang-github-kubernetes-heapster-devel-0.16.1-1.fc24.noarch requires 
golang(github.com/coreos/fleet/registry)
golang-github-kubernetes-heapster-devel-0.16.1-1.fc24.noarch requires 
golang(github.com/coreos/fleet/pkg)
golang-github-kubernetes-heapster-devel-0.16.1-1.fc24.noarch requires 
golang(github.com/coreos/fleet/machine)
g

Re: [F24 Criteria Change] Cockpit Release Criteria

[Stephen Gallagher]

> On Nov 5, 2015, at 5:10 PM, Máirín Duffy  wrote:
> 
> Hi!
> 
>> On 11/02/2015 08:31 AM, Stephen Gallagher wrote:
>> * All Cockpit functional criteria must be satisfied when the user is
>> running any of the following blocking browsers:
>>  - Mozilla Firefox as shipped in the same Fedora release
>>  - At least one of a) Mozilla Firefox or b) Google Chrome of the latest
>>available version on Windows at compose time.
>>  - At least one of a) Mozilla Firefox or b) Google Chrome of the latest
>>available version on OSX at compose time.
> 
> So we talked about this at the meeting yesterday [1] and I committed to 
> writing a draft that reflected what came out of that discussion.
> 
> Everything below relies on the assumption that any given issue found is an 
> issue in Fedora / Cockpit, not in the browser/platform experiencing the issue.
> 
> So first I'll put the draft, a modified version of Stephen's, then the 
> discussion / rationale behind it. Let me know what you think?
> 
> Draft
> =
> 
> * All Cockpit functional criteria must be satisfied when the user is running 
> any of the following platforms:
> 
> - Mozilla Firefox as shipped in the same Fedora release
> - Google Chrome of the latest available version at compose time on the same 
> Fedora release.
> - At least one of a) Mozilla Firefox or b) Google Chrome of the latest
> available version on Windows at compose time.
> - At least one of a) Mozilla Firefox or b) Google Chrome of the latest
> available version on OSX at compose time.
> 
> Manual testing will occur on the Firefox/Fedora platform. It will not be 
> performed on the Chrome/Fedora platform nor any of the Windows / OSX 
> platforms mentioned above, but if issues in meeting the functional criteria 
> are reported against those platforms, they may block the release.
> 
> 

I think this is basically perfect. Thank you very much for putting this 
together, particularly the detailed rationale.

The only thing I might change is "Manual testing will occur on the 
Firefox/Fedora platform" to "Mandatory testing will occur..."

I for one keep several systems around for cross-compatibility testing and will 
most likely do regular spot-checks that things aren't completely broken on the 
non-Fedora platforms. I note this because the practical effect here will be 
that any of these combinations here may indeed block the release (but I'm 
perfectly happy not requiring anyone else to use those other systems for 
testing).



> Discussion
> ==
> 
> What Platform(s) Experience the Issue?
> --
> 
> So basically we talked about how there's some different axes around browser 
> support for a web app:
> 
> 1) What specific browser is affected? Which ones do we care about?
> 
> 2) Is it on a desktop/laptop vs mobile device (tablet / phone)? Which do we 
> care about?
> 
> 3) Is the OS Fedora, a Linux, OS X, Windows? Which do we care about?
> 
> 
> Does It Block or Not?
> -
> 
> Then, at what level do we support whatever combinations we think are 
> important?
> 
> - Tier 1: Manual testing on Fedora, issues found could block release
> 
> - Tier 2: Not manually tested, but we care about them so if somebody finds an 
> issue it could block release
> 
> - Tier 3: Not manually tested, not a critical platform to us so we won't 
> block if an issue is found & reported.
> 
> 
> Platform Axis: Browsers
> ---
> 
> First, on browsers - according to the W3C's w3schools site, they see about 
> 60-65% of visitors on Chrome and Firefox around 20-24%. IE is 3rd at around 
> 6-8%. Other browser usage statistics reports seemed to have similar numbers.
> 
> Since they are the top two (and Firefox is also our default workstation 
> browser), it seems to make sense to put both Chrome and Firefox into Tier 1.
> 
> 
> Platform Axis: Laptop/desktop vs Mobile
> ---
> 
> We talked about laptop/desktop usage being more critical than mobile 
> (although Cockpit does care and think about mobile usage.)
> 
> 
> Platform Axis: OS
> -
> 
> We talked about concerns about forcing people to have to test on an OS they 
> weren't comfortable running. However, we are trying to expand our userbase 
> which means being friendly to folks who run the most popular OSes - Windows 
> and OS X. We wouldn't do manual testing of Windows or OS X, but we might care 
> if an issue was submitted to us that made Cockpit unable to meet its 
> functional criteria on that OS. Adam clarified (if I understand correctly) 
> that having this as a criteria doesn't dictate manual testing.
> 
> Summary
> ---
> 
> With respect to tiers:
> 
> Tier 1:
> Firefox on Fedora
> 
> Tier 2:
> Chrome on Fedora
> Firefox on Windows
> Chrome on Windows
> Firefox on OS X
> Chrome on OS X
> 
> Tier 3:
> Anything else.
> 
> 
> ~m
> 
> 
> [1] 
> https://meetbot.fedoraproject.org/fedora-meeting-1/2015-11-03/fedora-meeting-1.2015-11-03-16.