X86 February 2018

x86@lists.fedoraproject.org

5 participants
3 discussions

Patches for PTI on x86_32 in review
by Laura Abbott 24 Feb '18

24 Feb '18

Hi, There are now kernel patches for PTI posted for x86_32. If you are interested in this work, it would be very helpful to test and report to the upstream maintainers. https://marc.info/?l=linux-kernel&m=151612149716638 Thanks, Laura

2 1

Fwd: [Fedora-spins] Fedora 28 Spins page: spin/labs owners please test
by Stephen John Smoogen 24 Feb '18

24 Feb '18

While x86 is not a spin or a lab, it would be good to follow this also to make sure it is clear that x86 has people working on it during the beta and final times. ---------- Forwarded message ---------- From: Kevin Fenzi <kevin(a)scrye.com> Date: 23 February 2018 at 11:19 Subject: [Fedora-spins] Fedora 28 Spins page: spin/labs owners please test To: spins(a)lists.fedoraproject.org Greetings. Per this fesco ticket: https://pagure.io/fesco/issue/1714 I have created the Fedora 28 spins/labs page: https://fedoraproject.org/wiki/Releases/28/Spins All spin maintainers/owners/interested parties should test their spins and at least update this wiki page with beta/final testing. Spins that don't have at least one tester at Beta may be dropped and not shipped in Final, so PLEASE make sure at least someone tests. Spin maintainers are also encouraged to test their spin more often and make sure it's composing correctly every day for Branched f28 and rawhide. Thanks, kevin _______________________________________________ spins mailing list -- spins(a)lists.fedoraproject.org To unsubscribe send an email to spins-leave(a)lists.fedoraproject.org -- Stephen J Smoogen.

3 4

Fwd: Lines of communication: releng, automated testing
by Jeff Backus 02 Feb '18

02 Feb '18

And of course, I forgot to reply to the whole list. Sorry! ---------- Forwarded message ---------- From: Jeff Backus <jeff.backus(a)gmail.com> Date: Fri, Feb 2, 2018 at 4:59 PM Subject: Re: [X86] Lines of communication: releng, automated testing To: Adam Williamson <adamwill(a)fedoraproject.org> Hi Adam! On Wed, Jan 31, 2018 at 9:21 AM, Adam Williamson <adamwill(a)fedoraproject.org> wrote: > Hi folks! > > So, the topic of x86 came up in the Fedora panel discussion session at > Devconf this week, and one of the aspects we discussed is that there's > kind of a lack of lines of communication in a few areas. One especially > that I'm interested in is compose quality. > > It's not unusual for the status of nightly composes (for Branched and > Rawhide) to be different on i686 and x86_64. There can be actual arch > bugs, or just things like comps differences or lorax behaviour > differences or package dependency problems that result in i686 images > not building, or failing to work in ways that are arch-specific > somehow. When this happens, sometimes myself or Mohan Boddu (mboddu) or > Kevin Fenzi (nirik) will notice this, but we don't always have the > time/cycles to address it. > > We have automated testing for nightly composes (and for updates, but at > present I'm not running the automated tests on updates) in openQA: > https://openqa.fedoraproject.org/ > > Ideally it'd be great if someone from this group is aware and engaged > and involved when some important x86 images are not composing, or x86 > tests are failing where x86_64 tests do not. So I wanted to try and > open some lines of communication there. Thanks for reaching out to us. Near the release of F27 I was watching these more closely, but then I got completely buried at work, and have been negligent. We have a huge deadline in the March/April timeframe, and unfortunately, I won't have the free cycles to participate until then. > Right now, there's a report-y thing run after each compose: > https://pagure.io/fedora-qa/check-compose > > It generates the "compose check report" mails that are sent to devel@. > These cover the entire compose, though - so they include x86 > information, but it's alongside the x86_64 info and isn't really > tailored. It would be possible to tweak check-compose (and the code > that runs it) to send an x86-focused report of some kind to this list > (or, really, anywhere else), if that would be something people would > want. That list could note when important x86 images were missing from > the compose, and when there are failed tests which did *not* fail on > x86_64, for instance. It doesn't currently have those features, but I'm > pretty sure I can add them. So, let me know if that's something folks > are interested in, and I can look at doing it. That would be helpful, if it isn't too much trouble. Being able to detect an issue that is only affecting x86 at a glance would improve my response time. :) > It would also be great on an informal level to just have a known person > to poke when x86-specific issues arrive; if there's someone who's > usually hanging around in #fedora-releng (most importantly, possibly > also #fedora-qa) who we know will care about this sort of thing when > poked, that'd go quite a long way to helping, I think. Unfortunately, you won't find me on IRC, but feel free to send me an e-mail. Though, again, I'll be unresponsive until we can meet our deadline. E-mails to this list are probably the best way to get someone's attention. > Aside from all the above, I've subscribed to this list and joined > #fedora-x86 on Freenode and will do my best to send out feelers when > there's a known x86-specific issue. > > Thanks, folks! Thank you, too. Sorry for being missing in action. jeff -- Jeff Backus jeff.backus(a)gmail.com http://github.com/jsbackus -- Jeff Backus jeff.backus(a)gmail.com http://github.com/jsbackus

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

X86 February 2018