Planned Outage: Taskotron - 2015-04-23 18:00:00 UTC
There will be an outage starting at 2015-04-23 18:00:00 UTC, which will
last approximately 3 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:
date -d '2015-04-23 18:00:00 UTC
On Mon, 04 May 2015 15:43:19 -0700
Adam Williamson wrote:
> so I think it's well enough covered. Would anyone miss the minutes if
> they weren't sent to test@ any more? Thanks!
Wouldn't bother me - I usually look in the meetbot archives first if
I'm looking for something in the minutes anyways
On Fri, 8 May 2015 16:59:22 +0300
Igor Gnatenko wrote:
> Hi,
>
> I pushed mesa update into F22, but actually testing failed at some
> packages.
>
> I think its not related to my update.
>
> https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/67288/steps/runtask/logs/stdio
>
Planned Outage: Taskotron - 2015-05-11 19:00:00 UTC
There will be an outage starting at 2015-05-11 19:00:00 UTC, which will
last about 15 minutes
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:
date -d '2015-05-11 19:00:00 UTC'
---
On Tue, 12 May 2015 15:11:00 -0700
Adam Williamson wrote:
> So, I'd like to get sufficient votes on the proposed blockers and at
> least the significant proposed FEs as soon as possible. Would folks
> prefer voting on-list or in-bug, or having a special meeting, perhaps
> tomorrow (05-13) or Th
On Tue, 2 Jun 2015 07:02:06 -0400 (EDT)
Kamil Paral wrote:
> Hello,
>
> I have added some notes below.
>
> > The other thing to settle is what we actually want to report. Matt
> > provided the following guidelines:
> >
> > - the current state of the subproject
> > - future plans
> > - th
Hi everyone,
Roshi and I talked about it today over IRC and neither of us sees
anything that needs to be covered this week - no followup items and
nothing of significant note on test@ over the last week.
The council report will also be on Monday (roshi is covering that) and
that was the only some
===
#fedora-meeting Meeting
===
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2015-08-03/fedora-qa.2015-08-03-15.13.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting/2015-08-03/fedora-qa.2015-08-03-15.13.txt
Log:
http://meetb
I don't think that this has gotten much attention yet, so I wanted to
let folks know that Bodhi 2.0 is coming soon - the current working plan
is to upgrade the production bodhi instance next week after folks return
from Flock.
If this plan goes forward, there will be 3-ish weeks (depending on the
With the upgrade to bodhi2, the method we were using to notify
packagers of check failures (bodhi comments) is not working at the
moment due to some of the api changes which came with the upgrade.
We're working to restore the comments and eventually transition over to
fedmsg emission but in the me
On Tue, 19 Aug 2014 09:12:24 -0600
Chris Murphy wrote:
>
> On Aug 19, 2014, at 1:18 AM, Christopher Meng
> wrote:
>
> > I don't see the issue here, too.
> >
> > Maybe caused by the special hardware?
>
> Well this is just bizarre. This morning, it's working fine.
> Everything is the same, the
On Tue, 19 Aug 2014 09:54:01 -0600
Chris Murphy wrote:
>
> On Aug 19, 2014, at 9:22 AM, Tim Flink wrote:
>
> > On Tue, 19 Aug 2014 09:12:24 -0600
> > Chris Murphy wrote:
> >
> >>
> >> On Aug 19, 2014, at 1:18 AM, Christopher Meng
> >&
This has been a long time coming, but AutoQA is no longer scheduling
jobs and Taskotron is now running all of the automated checks on
packages/updates.
The changeover should be transparent to most people - the same checks
are being run in pretty much the same situations. Until Bodhi 2.0 is
deploye
On Tue, 14 Oct 2014 19:20:59 -0500
Michael Catanzaro wrote:
> The blocker bugs app [1] seems to have hardcoded links to outdated
> release criteria. Not sure where to file a bug
>
> [1] https://qa.fedoraproject.org/blockerbugs/propose_bug
Wow, that's been around for a while :)
Thanks for l
The usual suspects for leading the QA meeting are going to be out at
meeting time tomorrow and I'm not up to date enough with the possible
topics to put together a good agenda, so I propose that we cancel the
QA meeting tomorrow.
Of course, if there are topics that need discussion, I'm happy to
fa
On Sat, 19 Sep 2015 22:36:19 +0800
Ed Greshko wrote:
> With both fedora-easy-karma and fedora-gooey-karma broken what are
> folks using to easily supply feedback on packages in updates-testing?
There is a mostly-working patch attached to the bug about f-e-k:
https://bugzilla.redhat.com/show_bug
On Wed, 18 Nov 2015 16:36:16 -0800
Adam Williamson wrote:
> #2 MOAR METADATA
>
>
> The alternative is to make the existing Blocker trackers do more work.
> In this model we wouldn't add any new tracker bugs; we'd just add new
> 'magic words' in the Whiteboard field. Right now,
# Taskotron Outage and Upgrade
# Date: 2015-11-25
# Time: 21:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Length: Approximately 4 hours
There is a larger infra outage scheduled for Wednesday and we're going
to take advantage of that to do an upgrade to production Taskotron. Th
On Mon, 23 Nov 2015 13:26:54 -0500 (EST)
Kamil Paral wrote:
> > I feel that for something as important as system upgrade, we should
> > provide a better level of quality and assurance for upgrading
> > across 2 releases. Currently we have no criterion and testing it is
> > just an afterthought, n
do with packages whose test suite is not suitable to be
> executed during build (e.g. due to requirements or limitations on the
> build servers) ?
>
> What's your take ?
>
> ( Adding Tim Flink to CC to answer from the infrastructure side. )
I'm still unclear on what y
The AutoQA developers are proud to announce the release of AutoQA 0.8.5
today. This is a maintenance release with the following changes:
- Improved clarity in upgradepath output (#445)
- Updated repository configuration for F20 release
The new version has been deployed to our staging environme
On Mon, 06 Jan 2014 15:13:48 +
"Jóhann B. Guðmundsson" wrote:
>
> On 01/06/2014 02:52 PM, Matthew Miller wrote:
> > Hi Fedora test and QA folks! I posted a (kind of long) message on
> > Fedora devel with some thoughts about the direction of the project
> > in the next year. A lot of it direc
I had been thinking about doing this, but John brought it up during the
qa meeting today.
As we're done with both the holidays (read: vacation for many folks)
and F20, it's probably a good time to talk about where we are with the
various qa development projects and what we're going to focus on ove
On Mon, 06 Jan 2014 20:20:45 +
"Jóhann B. Guðmundsson" wrote:
>
> On 01/06/2014 05:42 PM, Tim Flink wrote:
> > I want to focus on getting the base
> > automation working well so that we can go to the WGs with "here's
> > our automation system a
On Mon, 06 Jan 2014 20:10:51 +
"Jóhann B. Guðmundsson" wrote:
> Do you think it's wise to be splitting this into seperated meeting
> from the qa meeting?
As much as I'm not really excited about yet another meeting, yes I do
think that it's wise to split this off.
- There is enough to tal
On Mon, 06 Jan 2014 21:27:44 +
"Jóhann B. Guðmundsson" wrote:
> >> If we want to free time to work on stuff like this Anaconda release
> >> cycle and testing must be finished before alpha or dealt with after
> >> beta.
> > Sure, that could end up being useful but it's but one piece of the
>
On Mon, 06 Jan 2014 13:39:35 -0800
Adam Williamson wrote:
> On Mon, 2014-01-06 at 20:20 +, "Jóhann B. Guðmundsson" wrote:
> > On 01/06/2014 05:42 PM, Tim Flink wrote:
> > > I want to focus on getting the base
> > > automation working well so that we can
On Mon, 06 Jan 2014 21:47:33 +
"Jóhann B. Guðmundsson" wrote:
>
> On 01/06/2014 09:39 PM, Adam Williamson wrote:
> > Of course, anything else we can do to free up not just Tim and
> > Kamil, but anyone else with the necessary knowledge and skills, to
> > contribute to tooling work is a good
# Fedora QA Devel Meeting
# Date: 2014-01-09
# Time: 16:00 - 18:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-2 on irc.freenode.net
The email feedback I received from folks was from NA and EMEA timezones
and showed a preference for Thursday over Wednes
=
#fedora-meeting-2: fedoraqa-devel
=
We didn't quite get through everything today, so we'll continue after
the QA meeting on Monday.
I'll be sending an announcement for that meeting shortly.
Minutes:
http://meetbot.fedoraproject.
# Fedora QA Devel Meeting
# Date: 2014-01-13
# Time: 17:00 - 19:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net
https://apps.fedoraproject.org/calendar/meeting/271/
Since we didn't quite get through everything on Thursday, we're
co
On Mon, 13 Jan 2014 09:57:05 -0700
Tim Flink wrote:
> On Fri, 10 Jan 2014 18:21:28 -0700
> Tim Flink wrote:
>
> > # Fedora QA Devel Meeting
> > # Date: 2014-01-13
> > # Time: 17:00 - 19:00 UTC
> > (https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
>
On Fri, 10 Jan 2014 18:21:28 -0700
Tim Flink wrote:
> # Fedora QA Devel Meeting
> # Date: 2014-01-13
> # Time: 17:00 - 19:00 UTC
> (https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
> # Location: #fedora-meeting-1 on irc.freenode.net
There was some miscommunication ab
==
#fedora-blocker-review: fedoraqa-devel
==
After much fun with finding an open channel for the meeting, we did get
through a bunch of stuff. At the moment, no more meetings are planned
and we will schedule more as needed/app
The Fedora QA devel team is proud to announce the release of Taskotron
0.1!
This is the first of many releases to come. While we are not yet to
the point where AutoQA can be replaced, each new release will bring us
closer to reaching that initial goal. The current plan is to move
towards a time-
# Fedora QA Devel Meeting
# Date: 2014-05-19
# Time: 16:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Now that Taskotron 0.1 has been released, it's time to start planning
for 0.2 so let's do a meeting right after the Fedora QA meet
===
#fedora-meeting: fedoraqa-devel
===
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2014-05-19/fedoraqa-devel.2014-05-19-16.00.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting/2014-05-19/fedoraqa-devel.2014-
I just upgraded the version of Phabricator that we have on qadevel [1]
and we now have the ability to do FAS authentication instead of the old
standalone username/password setup.
[1] https://phab.qadevel.cloud.fedoraproject.org/
If you have no idea what I'm talking about, you can probably ignore
The Fedora QA devel team is proud to announce the release of Taskotron
0.3!
This is another incremental improvement and a continuation of our
new-ish timed release process. The new release is running in our
staging instance:
https://taskotron-stg.fedoraproject.org/
The major changes have been:
This has been a long time coming but after running on smaller systems
for the last couple months to make sure that all the parts are running
smoothly, Taskotron is now running in staging:
https://taskotron.stg.fedoraproject.org/
What does this mean? It means that we are almost ready to turn on th
As support for the Persona system has winded down, we finally have a
new method for logging into our phabricator instance (that should
also get rid of all those 500s on login).
My goal has been to set up the migration so that there's no account
fiddling needed to use the new auth system. Things ar
On Wed, 07 Dec 2016 08:24:46 -0800
Adam Williamson wrote:
> For a start Ipsilon tells me it's some entirely foreign third-party
> domain - 'monikra.me' - that wants access to all my personal
> information, which is a bit unsettling. I went ahead and let it have
> it (For Science!) and got:
FWI
On Wed, 7 Dec 2016 08:52:53 -0700
Tim Flink wrote:
> As support for the Persona system has winded down, we finally have a
> new method for logging into our phabricator instance (that should
> also get rid of all those 500s on login).
>
> My goal has been to set up the migration
I realize this is a little last minute but there's no telling how much
longer the current auth system will continue to work.
I'm planning to take qadevel down (phabricator, some docs etc.)
tomorrow so that I can finally replace it with an instance that has
working auth among other improvements.
T
The outage is taking a bit longer than I had hoped - other production
systems going down during the outage didn't help :)
I'm still working on this and will send out an email when it's done.
Tim
On Wed, 14 Dec 2016 10:54:45 -0700
Tim Flink wrote:
> I realize this is a litt
hine ready
for data migration.
Tim
On Thu, 15 Dec 2016 14:34:55 -0700
Tim Flink wrote:
> The outage is taking a bit longer than I had hoped - other production
> systems going down during the outage didn't help :)
>
> I'm still working on this and will send out an email whe
I realize this is a little last minute but persona has been completely
shut down now (so auth is no longer possible) and the last issue that
was preventing migration was taken care of yesterday.
I'm planning to take qadevel down (phabricator, some docs etc.)
today so that I can finally replace it
On Thu, 5 Jan 2017 10:42:09 -0700
Tim Flink wrote:
> I realize this is a little last minute but persona has been completely
> shut down now (so auth is no longer possible) and the last issue that
> was preventing migration was taken care of yesterday.
The outage is complete and phabri
There will be an outage starting at 2017-01-17 20:00 UTC, which will
last approximately 12 hours.
To convert UTC to your local time, take a look at
https://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2016-01-17 20:00 UTC'
Reason for outage:
We will be upgrading Taskotron to a new version w
Outage is complete, everything is back up and running.
Please let us know if you see anything not working correctly.
Tim
On Mon, 16 Jan 2017 13:22:20 -0700
Tim Flink wrote:
> There will be an outage starting at 2017-01-17 20:00 UTC, which will
> last approximately 12 hours.
>
>
This has been announced through other channels but just to make sure
folks are aware, there will be a planned outage later today for updates
and reboots.
This will affect all qa systems (amongst others):
- taskotron
- phabricator
- blockerbugs
- openqa
There will be an outage starting at
This has been announced through other channels but just to make sure
folks are aware, there there will be an outage starting at 2016-09-21
21:00 UTC, which will last approximately 4 hours.
This will affect all qa systems (amongst others):
- taskotron
- phabricator
- blockerbugs
- openqa
On Mon, 19 Sep 2016 13:49:37 -0700
Adam Williamson wrote:
> On Mon, 2016-09-19 at 12:30 -0600, Tim Flink wrote:
> > This has been announced through other channels but just to make sure
> > folks are aware, there there will be an outage starting at
> > 2016-09-21 21:00
Hello everyone!
My name is Tim Flink and I just joined Red Hat to work on Fedora QA.
I've been a Fedora user since Fedora 5 but haven't been involved in the
community until now.
My recent experience has been in storage device testing and test
automation framework development with a
On 02/01/2011 09:44 AM, "Jóhann B. Guðmundsson" wrote:
> On 02/01/2011 03:24 PM, Tim Flink wrote:
>> Hello everyone!
>>
>> My name is Tim Flink and I just joined Red Hat to work on Fedora QA.
>> I've been a Fedora user since Fedora 5 but haven
Hi all!
I sent out an introduction yesterday, but my name is Tim Flink and I'm a
new Red Hat employee working on Fedora QA.
I was wondering if someone would be willing to sponsor my membership in
the FAS qa group (FAS: tflink). If so, I would really appreciate it.
Thanks,
Tim
--
On 02/02/2011 04:41 PM, "Jóhann B. Guðmundsson" wrote:
> On 02/02/2011 10:37 PM, Tim Flink wrote:
>> Hi all!
>>
>> I sent out an introduction yesterday, but my name is Tim Flink and I'm a
>> new Red Hat employee working on Fedora QA.
>>
>> I w
On 02/11/2011 03:35 PM, Orion Poplawski wrote:
> On 02/11/2011 03:32 PM, Orion Poplawski wrote:
>> Has anyone been able to boot the F15 Alpha TC1 image as a kvm guest? On my
>> CentOS 5.5 host I get some kind of kernel crash.
>>
>
> Ah, looks like I was running out of memory.
>
> Is it expected to
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 through the installer without issue
On 02/21/2011 10:12 AM, Kamil Paral wrote:
>
> I wonder if this is related to a problem I faced when I installed F15 Alpha
> RC2 and then ran "yum update". I received some errors about incorrect
> signature key (it seemed that some packages were signed by a key not present
> in the system, or so
On 02/21/2011 10:04 AM, Tim Flink wrote:
> 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
> w
I'm hitting https://bugzilla.redhat.com/show_bug.cgi?id=678431 while
attempting to report a couple of bugs.
Are there any known workarounds? I'm not sure that my bug reports will
be as useful without backtraces.
I thought that this was approved as an alpha blocker since it interferes
with abrt
On 02/22/2011 06:26 PM, Dennis Gilmore wrote:
> On Tuesday, February 22, 2011 06:33:22 pm Tim Flink wrote:
>> I'm hitting https://bugzilla.redhat.com/show_bug.cgi?id=678431 while
>> attempting to report a couple of bugs.
>>
>> Are there any known workarounds? I
On 03/16/2011 11:36 AM, Gregory Woodbury wrote:
> On Wed, Mar 16, 2011 at 1:11 PM, James Laska wrote:
>
>> On Wed, 2011-03-16 at 12:10 -0400, Gregory Woodbury wrote:
>>> 1) The boot.iso netinstall fails with an anaconda error about unique uuid
>>> for disks.
>>
>> https://bugzilla.redhat.com/show
On 03/16/2011 01:18 PM, Gregory Woodbury wrote:
> On Wed, Mar 16, 2011 at 1:47 PM, Tim Flink wrote:
>
>> On 03/16/2011 11:36 AM, Gregory Woodbury wrote:
>>> No traceback or messages that I can see, just a notification that i can't
>>> put
>>> a part
On 03/21/2011 02:11 PM, James Laska wrote:
> Greetings folks,
>
> As mentioned during the QA meeting today, I promised to provide
> custom-built boot.iso (x86_64) so folks can add some bodhi karma for two
> important updates. The following updates are needed in order to proceed
> with building Be
I took part in an interesting discussion in #fedora-qa today with
someone who was new to Fedora (coming from Ubuntu) and interested in
testing.
He (I assume he, will use for consistancy) came to the alpha download
page on fedoraproject.org [1], tried to use and install the alpha and
ran into some
On 03/25/2011 02:04 PM, Adam Williamson wrote:
> On Fri, 2011-03-25 at 13:53 -0600, Tim Flink wrote:
>> I took part in an interesting discussion in #fedora-qa today with
>> someone who was new to Fedora (coming from Ubuntu) and interested in
>> testing.
>>
>&
On 03/25/2011 02:33 PM, Tim Flink wrote:
> On 03/25/2011 02:04 PM, Adam Williamson wrote:
>> On Fri, 2011-03-25 at 13:53 -0600, Tim Flink wrote:
>>> I took part in an interesting discussion in #fedora-qa today with
>>> someone who was new to Fedora (coming fro
Rolling on with the Fedora 15 Test Days, we have the Printing test day
this week:
https://fedoraproject.org/wiki/Test_Day:2011-03-29_Printing
This event will focus on all aspects of printing; including printer
setup, printer sharing and printing jobs.
In previous Fedora releases the application
On 04/07/2011 09:29 AM, James Laska wrote:
> Greetings folks,
>
> The last planned update to anaconda before RC1 is available for testing.
> I built a custom boot.iso in order to provide karma feedback on
> anaconda-15.27-1. The boot.iso was also created using the latest
> systemd and NetworkMana
On 04/07/2011 01:30 PM, James Laska wrote:
>>> Hmm, I seem to be having a bit of trouble getting a bootable system on a
>>> VM from that boot.iso.
>>>
>>> I'm going to try again and see if I can't get it to work.
>>
>> That's actually known and due to
>> https://bugzilla.redhat.com/show_bug.cgi?i
I apologize if this has already been discussed but my google-fu and
mailbox-search-fu aren't finding anything recent.
What is supposed to be the default background on the desktop spin? At
one point, I had the F15 artwork for GDM, grub gnome etc. [1] but the
grub background seems to be the only one
On 04/14/2011 11:45 AM, Tim Flink wrote:
> I apologize if this has already been discussed but my google-fu and
> mailbox-search-fu aren't finding anything recent.
>
> What is supposed to be the default background on the desktop spin? At
> one point, I had the F15 artwork for
On 04/14/2011 02:32 PM, Martin Sourada wrote:
> Well, for gnome (and gdm) you should get the picture in 'Wallpaper
> (GNOME)' section on that page you mentioned. It's set via
> 'desktop-backgrounds-gnome' package, if that's not installed on Desktop
> Spin than the comps should be adjusted... AFAIK
I just noticed this on a fresh install of F15 from the Beta RC2 media and I'm
not sure if there is a problem.
I have separate LVs for home and root, and it looks like they're both mounted
multiple times:
/dev/mapper/vg_testlap-lv_root on / type ext4
(rw,relatime,seclabel,barrier=1,data=ordered
During the blocker meeting today, a greeter bug came up [1] but we
weren't sure if this is affecting the live images.
Using a recent live image, has anyone been dumped to gdm with an empty
user list?
Tim
[1] https://bugzilla.redhat.com/show_bug.cgi?id=678236
signature.asc
Description: OpenPGP
On 04/15/2011 04:31 PM, Clyde E. Kunkel wrote:
> Probably something I did, can anyone shed light on the following?
>
>
> $ sudo yum update
> Loaded plugins: langpacks, presto, refresh-packagekit
> Setting up Update Process
> Resolving Dependencies
> --> Running transaction check
> ---> Package ad
On 04/15/2011 12:27 PM, Tim Flink wrote:
> During the blocker meeting today, a greeter bug came up [1] but we
> weren't sure if this is affecting the live images.
>
> Using a recent live image, has anyone been dumped to gdm with an empty
> user list?
>
> Tim
>
>
The Cloud SIG test day for Fedora 15 is will be this Thursday [1]. The
focus will be on using BoxGrinder [2] and Amazon Elastic Compute Cloud
(EC2) [3] with Fedora 15.
BoxGrinder is "a set of projects that help you grind out appliances for
multiple virtualization and Cloud providers." Another way
On 04/27/2011 10:16 AM, James Laska wrote:
>
> Thanks to Clyde for the karma so far! The update is one karma point shy
> of moving into 'stable'. Anyone else have a spare system (or virt
> guest) they can use to run some quick tests on?
>
> Thanks,
> James
Tested and karma added.
Tim
sign
As I'm going through updates-testing, I'm noticing a decent number of
comments with 0 karma and content similar to "not tested" or "I don't
have this". I'm guessing a bit here, but I assume that is due to using
fedora-easy-karma.
You can skip an update in f-e-k by just hitting enter; you don't hav
I've been putting this off for a while but it's time to actually do it.
I'm going to disable username/password logins to phabricator when I
update it with the newest build next week. The username/password system
was only meant as a temporary system until we could get FAS auth
working and that's be
# Fedora QA Devel Meeting
# Date: 2014-12-15
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net
Now that F21 is out the door, we can start working a bit more on
tooling. I'd like to spend most of the time discussing the vari
# Fedora QA Devel Meeting
# Date: 2014-12-16
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net
We had a couple folks who couldn't make the meeting today at the last
minute, so we decided to hold the meeting tomorrow instead
As a heads up, all QA services will be affected by the infra outages
scheduled over the next 3 days: 2014-12-15, 2014-12-16 and 2014-12-17.
Taskotron and Blockerbugs will be affected by all three outages but
Beaker will be less affected due to how it's deployed as a
non-production service.
https:/
On Thu, 11 Dec 2014 13:20:40 -0700
Tim Flink wrote:
> I've been putting this off for a while but it's time to actually do
> it.
>
> I'm going to disable username/password logins to phabricator when I
> update it with the newest build next week. The username/passwor
I'm not sure what happened but the machine hosting qadevel became
unresponsive sometime in the last 12 hours and is not recoverable.
I'm going to be rebuilding the host today but until I'm done,
phabricator and the other services on qadevel will not be available.
I'll update this thread as I make
Since qadevel needs to be rebuilt, I'm taking this opportunity to move
it out of the cloud infrastructure since that's been on my TODO list
for some time now.
As part of this, the database host for most of the QA services needs to
be upgraded.
Taskotron (dev, stg and prod) will be going during th
On Fri, 30 Jan 2015 14:45:07 -0700
Tim Flink wrote:
> Since qadevel needs to be rebuilt, I'm taking this opportunity to move
> it out of the cloud infrastructure since that's been on my TODO list
> for some time now.
>
> As part of this, the database host for most of t
On Fri, 30 Jan 2015 08:44:03 -0700
Tim Flink wrote:
> I'm not sure what happened but the machine hosting qadevel became
> unresponsive sometime in the last 12 hours and is not recoverable.
>
> I'm going to be rebuilding the host today but until I'm done,
> phabric
Just wanted to send a heads-up to folks but there was an upgrade to
RHBZ last night which broke the blockerbugs app's ability to sync with
bugzilla and the data shown is probably not current.
I'm trying to get this fixed as quickly as I can but wanted to make
sure folks were aware of the problem s
On Wed, 8 Apr 2015 12:36:18 -0600
Tim Flink wrote:
> Just wanted to send a heads-up to folks but there was an upgrade to
> RHBZ last night which broke the blockerbugs app's ability to sync with
> bugzilla and the data shown is probably not current.
>
> I'm trying to get
AutoQA will be affected by the infrastructure changes announced last
week [1]. During the outage, AutoQA tests will not be run and feedback
will not be posted to Bodhi.
At this point, we are expecting the outage to last at least a day while
the systems are re-racked and we reconfigure AutoQA for t
On 07/19/2011 09:49 AM, Sergio Rubio wrote:
> Greetings!
>
> Posted this to the wrong mailing list (David Cantrell suggested using
> this one instead).
>
> Linking to avoid re-typing :), my apologies:
>
> https://www.redhat.com/archives/anaconda-devel-list/2011-July/msg00090.html
>
> In a nutsh
# F16 Alpha Blocker Review meeting #3
# Date: 2011-07-29
# Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST)
# Location: #fedora-bugzappers on irc.freenode.net
It's once again time for everyone's favorite activity - blocker bug
review meeting time !!
Fedora 16 has branched and the first Alpha
On Thu, 28 Jul 2011 14:52:12 -0700
Adam Williamson wrote:
> "Daily Review & Notification of Open Alpha|Beta|Final Blocker Bugs"
> is a trickier customer. As scheduled, it seems to suggest that for
> Alpha, Beta and Final, we should be 'reviewing and notifying' open
> blockers for an arbitrary-s
This is a little later than originally planned, but the Fedora 15
(yes, Fedora 15 - not a typo) EC2 test day will be on this Thursday
2011-08-04 [1].
Fedora 15 AMIs are available for testing and are listed on the test
day wiki page [1]. The tests are designed to ensure basic functionality
for the
==
#fedora-meeting: Fedora QA meeting
==
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2011-08-08/fedora-qa.2011-08-08-15.01.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting/2011-08-08/fedora-qa
The Fedora 15 EC2 test day took place on 2011-08-04. 5 testers posted
results to the test day page [1] providing 3 reproductions of a known
issue and one new bug filed.
New Bugs:
* 728465 [2] - Fedora EC2: httpd test failed with symbolic error
in /var/log/messages and systemd be
1 - 100 of 483 matches
Mail list logo
