qa-devel April 2017

qa-devel@lists.fedoraproject.org

6 participants
5 discussions

Planned Outage: Taskotron Production - 2017-04-25 @ 19:00
by Tim Flink 25 Apr '17

25 Apr '17

There there will be an outage starting at 2017-04-25 19:00 UTC, which will last approximately 2 hours. This is less notice than I would like but we're going to have some downtime for Taskotron later today. I suspect that the actual outage will be less than 2 hours but for the sake of safety, we've left it that long. The primary purpose of this outage is to get the production resultsdb database off of the common host that most of the rest of the QA apps are using. There have been some performance issues as of late and we want to start narrowing down what could be causing the problem. Tim

1 1

2017-04-24 @ 15:00 UTC - Fedora QA Devel Meeting
by Tim Flink 24 Apr '17

24 Apr '17

# Fedora QA Devel Meeting # Date: 2017-04-24 # Time: 14:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting-1 on irc.freenode.net https://phab.qa.fedoraproject.org/w/meetings/20170424-fedoraqadevel/ If you have any additional topics, please reply to this thread or add them in the wiki doc. Tim Proposed Agenda =============== Announcements and Information ----------------------------- - Please list announcements or significant information items below so the meeting goes faster Tasking ------- - Does anyone need tasks to do? Potential Other Topics ---------------------- - Documentation - Test Invocation - Dist-Git Task Storage Open Floor ---------- - TBD

2 2

Re-Scheduling Jobs for Taskotron as a User
by Tim Flink 20 Apr '17

20 Apr '17

One of the things that seems like it is and will be a pain point for folks writing package-specific tasks is how to work through the times when there was an issue in the task and things didn't run well. At the moment, the only solution we have is to re-build the affected package or to pester an admin to re-run the trigger - neither of which is an ideal answer. I was thinking about how to improve this in the near future and am wondering about adding a "reschedule" button to execdb jobs: 1. authenticated user clicks on "reschedule" button 2. execdb makes an api call to the buildmaster to find the parameters which were used for that task 3. using the data from 2), execdb starts a new job for just that item and item type I'm not thrilled at the idea of code duplication here between trigger and execdb but compared to figuring out a web interface for trigger, this seems like a more tractable solution for the short/medium term. Thoughts? Tim

6 8

Proposal to CANCEL: 2017-04-17 QA Devel Meeting
by Tim Flink 17 Apr '17

17 Apr '17

It's a holiday for many of the usual suspects and seeing as how attendance will likely be low, I'm proposing that we cancel the usual QA Devel meeting. If there are topics that you think need to be discussed this week, reply to this thread and we can un-cancel. Tim

1 0

2017-04-10 @ 15:00 UTC - Fedora QA Devel Meeting
by Tim Flink 10 Apr '17

10 Apr '17

# Fedora QA Devel Meeting # Date: 2017-04-10 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting-1 on irc.freenode.net https://phab.qa.fedoraproject.org/w/meetings/20170410-fedoraqadevel/ If you have any additional topics, please reply to this thread or add them in the wiki doc. Tim Proposed Agenda =============== Announcements and Information ----------------------------- - Please list announcements or significant information items below so the meeting goes faster Tasking ------- - Does anyone need tasks to do? Potential Other Topics ---------------------- - Documentation - Deployment of new Features - Dist-Git Task Storage - CI Open Floor ---------- - TBD

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

qa-devel April 2017