Re: F40 Change Proposal: ROCm 6 Release (Self-Contained)

[Tim Flink]

On 1/12/24 14:52, Ryan Bach via devel wrote:

https://release-monitoring.org/project/132606/
--


I'm not sure I understand the purpose of that link.

The git repo that anitya is tracking there is mostly docs and isn't on the list 
of ROCm components that we're planning to package in Fedora. It should get 
updated with new tags whenever there's a ROCm release but so will all the 
individual components that are/will be in Fedora.

What am I missing?

Tim
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F40 Change Proposal: Pytorch Release (Self-Contained)

[Tim Flink]

On 1/11/24 21:40, drago01 wrote:



On Thursday, January 11, 2024, Aoife Moloney > wrote:



== Benefit to Fedora ==

This change will introduce PyTorch, a high demand machine learning
framework, to Fedora. PyTorch is widely used for tasks such as image
and speech recognition, natural language processing, and other
artificial intelligence applications, providing a user-friendly
interface for building and experimenting with complex machine learning
models. This is for CPU (x86_64 and aarch64) only and is the first
release for Fedora. The current development effort is focused on AMD
GPU acceleration.


What does this mean? Is it now CPU only or does it support AMD GPUs?

CPU only would be of limited use and people would most likely just use 
pip instead.


Yes, pytorch would be CPU only for F40 as a first step.

We're still working on AMD GPU support via ROCm - hopefully that will be for 
F41.

Tim
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Help packaging PyTorch dependencies for Fedora

[Tim Flink]

On 12/9/23 14:47, Dominik 'Rathann' Mierzejewski wrote:

On Friday, 08 December 2023 at 16:34, Steve Grubb wrote:

On Friday, December 8, 2023 12:41:59 AM EST Jun Aruga (he / him) wrote:

Congratulations for the PyTorch package!
https://src.fedoraproject.org/rpms/python-torch

I hope someone will announce this great achievement to the Fedora
community too, and update the following page too.
https://fedoraproject.org/wiki/SIGs/PyTorch/packagingStatus


Yes, this is nice that we have pytorch in Fedora. Looking at the specfile...

USE_CUDA=OFF
USE_ROCM=OFF

Which does not align with:

%description
PyTorch is a Python package that provides two high-level features:
  * Tensor computation (like NumPy) with strong GPU acceleration

GPU acceleration?


Indeed. We have ROCM in Fedora already:
$ sudo dnf list rocm\*devel
Last metadata expiration check: 0:00:24 ago on Sat 09 Dec 2023 22:42:19.
Available Packages
rocm-comgr-devel.x86_64   16.1-2.fc38   
updates
rocm-hip-devel.x86_64 5.5.1-10.fc38 
updates
rocm-opencl-devel.x86_64  5.5.1-10.fc38 
updates
rocm-runtime-devel.x86_64 5.5.0-2.fc38  
updates
rocm-smi-devel.x86_64 5.5.1-3.fc38  
updates

At least the OpenCL part works quite well for me.


We have made a lot of progress towards getting ROCm packaged in Fedora but 
we're not quite done and I know there are a few yet-unpackaged ROCm components 
which are required before ROCm support can be enabled for pytorch.

The current status list of ROCm packages is in the wiki: 
https://fedoraproject.org/wiki/SIGs/HC#Package_status

The current plan is to have ROCm 6.0.0 in F40 before branch, assuming that the 
release dates line up. As far as I know, AMD has not given an exact release 
date for 6.0 but ROCm 6.0 was announced last week and it seems likely to 
release well before F40 branch.

Tim


[...]

pip install torch
python3

import torch
torch.__config__.show()


The config listed there should be compared with the config in the spec file to
get as close to the expected feature set as possible so that people can just
switch. This is a positive step and I would love to switch one day.


Good idea.

Regards,
Dominik

--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Help packaging PyTorch dependencies for Fedora

[Tim Flink]

On 12/8/23 08:34, Steve Grubb wrote:

On Friday, December 8, 2023 12:41:59 AM EST Jun Aruga (he / him) wrote:

Congratulations for the PyTorch package!
https://src.fedoraproject.org/rpms/python-torch

I hope someone will announce this great achievement to the Fedora
community too, and update the following page too.
https://fedoraproject.org/wiki/SIGs/PyTorch/packagingStatus


Yes, this is nice that we have pytorch in Fedora. Looking at the specfile...

USE_CUDA=OFF
USE_ROCM=OFF

Which does not align with:

%description
PyTorch is a Python package that provides two high-level features:
  * Tensor computation (like NumPy) with strong GPU acceleration

GPU acceleration? Also,


GPU acceleration is not enabled for the pytorch packages and that is 
intentional, for now. pytorch has a mess of third party dependencies which are 
managed upstream using git subrepos that point to external dependencies that 
may or may not be easy to package for Fedora. From the beginning, our plan has 
been to get pytorch packaged for CPU only first and add accelerator support as 
we can. Perhaps the description for pytorch needs to be changed but our intent 
is to enable ROCm support for F40.

I don't have the exact list of packages remaining before we can enable ROCm 
support for pytorch in front of me but I believe that we're down into the 
single digits and the biggest hurdle at the moment is ROCm's miopen due to some 
incompatibility with Fedora's llvm or hipcc.


USE_OPENMP=OFF

So, no threading? What about at least enabling BLAS? Maybe it is by default.
Not seeing it in the specfile. Without a CUDA version of this, it can't be
used the way it was meant to be. We still need to use pip install to get an
accelerated version:


I'm not familiar with OpenMP or what might be required there, Tom (cc'd) would 
know more on that exact detail.

I doubt that a CUDA version of pytorch will ever be packagable for the Fedora 
repos - the licensing on CUDA would have to change before that happens and 
while it's possible, it doesn't seem likely in the foreseeable future.

It would be great to enable support for Intel accelerators but that is a 
different project for a different day. ROCm is the only accelerator support 
that we have scoped out at this point.


pip install torch
python3

import torch
torch.__config__.show()


The config listed there should be compared with the config in the spec file to
get as close to the expected feature set as possible so that people can just
switch. This is a positive step and I would love to switch one day.


In general, there are two reasons why a torch feature is not enabled in the 
Fedora package:

1. The license of a dependency for that feature is incompatible with Fedora
2. One or more dependencies are not yet packaged for Fedora

Obviously, features that fall into (1) are very difficult, if not impossible 
for us to work around. Features that fall into (2) will likely need more time - 
the first build for PyTorch was about a week ago and we still have work to do.

We are working to get the pytorch packages in Fedora to be as complete as we 
can make them. If anyone is interested in helping, please join us on discourse 
(#ai-ml-sig) or Matrix (#ai-ml:fedoraproject.org).

Tim


Best Regards,
-Steve

--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Help packaging PyTorch dependencies for Fedora

[Tim Flink]

On 12/7/23 22:41, Jun Aruga (he / him) wrote:

Congratulations for the PyTorch package!
https://src.fedoraproject.org/rpms/python-torch

I hope someone will announce this great achievement to the Fedora
community too, and update the following page too.
https://fedoraproject.org/wiki/SIGs/PyTorch/packagingStatus


PyTorch packages in Fedora are still a work in progress - torchvision and 
torchdata are still in review, for example.  We are definitely planning to 
announce it once we've made more progress and are also planning to make a F40 
change proposal for PyTorch.

I didn't realize that the dependency packaging list was out of date but I'll 
review it this week and make sure it has been updated.

Tim



Jun

On Wed, Oct 11, 2023 at 11:55 PM Kaitlyn Abdo  wrote:


Hello everyone,

I hope this email finds everyone well. We are currently packaging PyTorch for 
Fedora and we are actively packaging the dependencies. We’re reaching out to 
see if anyone is interested in joining the project. If you’re interested in 
more information, our meeting notes are in a GitHub repo and we have the AI/ML 
SIG discussion page where we’ve hosted all of our post meeting discussions. We 
have a WikiPage for our package assignment list if you would like to see what 
needs packaging or just to see the status of the project. Our next meeting is 
tomorrow, October 11th at 9AM EST and it’s on the FedoCal under the SIG 
calendar. All lists are found below. If you’re interested in joining, have any 
questions, or want to get a calendar invite for our reoccurring meeting, please 
feel free to email me at ka...@redhat.com or Teng at t...@redhat.com.

AI/ML SIG Discussion Page: https://discussion.fedoraproject.org/tag/ai-ml-sig
Meeting Notes: https://github.com/kaitlynabdo/pytorch-fedora-meeting-notes
Packaging Assignment List: 
https://fedoraproject.org/wiki/SIGs/PyTorch/packagingStatus
FedoCal: https://calendar.fedoraproject.org/SIGs/

Thank you!
Kaitlyn Abdo
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue





--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: How to fix the "rpma.src: W: strange-permission rpma.spec 600" warning?

[Tim Flink]

On 5/25/23 09:56, Xiao Yang wrote:

Hi all,

I try to create rpma source package on fedora by fedpkg --release rawhide 
mockbuild.
The permissions of original rpma.spec is 0644:
$ ll rpma.spec
-rw-r--r--. 1 mockbuild mock 2107 May 25 17:31 rpma.spec

The permissions of rpma.spec in the generated rpma source package is changed to 
0600 and then the following warning is triggered by fedpkg --release rawhide 
lint.
$ fedpkg --release rawhide lint
Failed to get repository name from Git url or pushurl
Failed to get ns from Git url or pushurl
Mockbuild results directory found. Linting mockbuild results.
 rpmlint session starts 
rpmlint: 2.4.0
configuration:
 /usr/lib/python3.11/site-packages/rpmlint/configdefaults.toml
 /etc/xdg/rpmlint/fedora-legacy-licenses.toml
 /etc/xdg/rpmlint/fedora-spdx-licenses.toml
 /etc/xdg/rpmlint/fedora.toml
 /etc/xdg/rpmlint/scoring.toml
 /etc/xdg/rpmlint/users-groups.toml
 /etc/xdg/rpmlint/warn-on-functions.toml
checks: 31, packages: 4

rpma.src: W: strange-permission rpma.spec 600
  3 packages and 1 specfiles checked; 0 errors, 1 warnings, 0 badness; has 
taken 0.3 s

Could you tell me how to fix the warning?

Best Regards,
Xiao Yang
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


I don't know if you found a solution to this but I figured that I would post 
what I ended up doing after hitting the same problem, assuming that you're also 
using rpmautospec.

The root of this is that rpmautospec/rpkg use python's tempdir in their process 
of rendering the actual spec file. On my system, at least, /tmp has 600 
permissions so the rendered file inherits those permissions and is just copied 
after rendering, making it into the srpm without a permission change.

I assume that the koji builders don't have the same setup and thus avoid the 
rpmlint warnings for official builds.

I fixed the problem for my local build by generating the srpm outside fedpkg:

$ mkdir build
$ rpmautospec process-distgit mypackage.spec build/mypackage.spec
$ chmod 644 build/mypackage.spec
$ mock -r fedora-rawhide-x86_64 --buildsrpm --spec build/mypackage.spec 
--sources .
$ cp /var/lib/mock/fedora-rawhide-x86_64/result/*.src.rpm .

I'm a little unclear on whether this needs to be fixed or not if it only 
affects local mockbuilds or if there are better workarounds. If there's a 
better solution for this other than going back to generating the changelog and 
release by hand, I'm all ears 

Tim
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Test-Announce] 2022-11-14 @ 16:00 UTC - Fedora QA Meeting

[Tim Flink]

# Fedora Quality Assurance Meeting
# Date: 2022-10-24
# Time: 16:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.libera.chat

Greetings testers!

F37 went GO last week and is due to be released immanently. Let's review any 
remaining last-minute items for F37 and start looking at F38.

If you have any items for the agenda, please reply to this email to suggest 
them.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 37 status
3. Fedora 38 changes
4. Test Day / community event status
4. Open floor
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [Test-Announce] Proposal to CANCEL: 2022-08-22 Fedora QA Meeting

[Tim Flink]

At some point, we do need to wrap up the TCMS conversation. If not this week 
then hopefully next week or the week after.

Tim

On 8/22/22 00:25, Adam Williamson wrote:

Hi folks! I'm proposing we cancel the QA meeting today/tomrrow. I
don't have anything much for the agenda again. There will be a
blocker review meeting, though.

If you're aware of anything it would be useful to discuss this week,
please do reply to this mail and we can run the meeting.

Thanks folks!

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: orphaning Taskotron-related packages

[Tim Flink]

On Thu, 12 Nov 2020 18:25:17 +0100
Kamil Paral  wrote:

> Note: The email subject should have said "retiring" instead of
> "orphaning". There is little reason to orphan them, retiring is the
> right approach here. Perhaps except for mongoquery, somebody else
> could be interested in maintaining that, so that one should be
> orphaned instead.

Orphaning python-mongoquery and retiring everything else makes sense to
me.

Tim


pgpKM0xSB4EP3.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org

bsd wtf (was Re: youtube-dl Copyright Violations)

[Tim Flink]

On Mon, 26 Oct 2020 09:47:42 +
Sérgio Basto  wrote:

> On Mon, 2020-10-26 at 08:33 +, Leigh Scott wrote:
> > > I don't know what IANAL means but sounds rude...
> > > 
> > > 
> > > 
> > > On Mon, 26 Oct 2020 at 00:14, Fabio Valentini
> > >  > 
> > LOL :-)
> > 
> > IANAL=I am not a lawyer  
> 
> you may install wtf [1] (part of bsd-games package) and query
> aboutthis acronym [2] 
> 
> [1]
> dnf install /usr/bin/wtf 
> 
> [2] 
> wtf IANAL
> 
> IANAL: I am not a lawyer

I did not know that was a thing but I'm happy to know it now.

To save some time in case someone else is curious and ends up going
down the same rabbit hole I did:

There is a maintained upstream for bsd-games [1] that has effectively
forked the old codebase and trimmed out some of the bits which are not
quite games including wtf (the readme says "outdated acronym lookup. We
have Google now."). However, the fedora package doesn't appear to built
from the new upstream, still using 2.17 as a base which still has wtf
instead of the new upstream's 3.x.

[1] https://github.com/msharov/bsd-games

The ftp site that is often credited for being the upstream url for
bsd-games [2] isn't working for me at the moment but I don't know if
that's just temporary.

[2] ftp://metalab.unc.edu/pub/Linux/games/
  
There is a sourceforge project [3] which mirrors NetBSD's updates to
the wtf acronym database. That acronym database in NetBSD [4] is still
regularly updated and the sourceforge project is still seeing updates.

[3] https://sourceforge.net/projects/bsdwtf/
[4] http://cvsweb.netbsd.org/bsdweb.cgi/src/share/misc/acronyms

Tim


pgptZVdWSfttF.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: seeing issues querying results by nvr/item in resultsdb

[Tim Flink]

On Thu, 9 Apr 2020 07:15:03 +0200
Kamil Paral  wrote:

> On Thu, Apr 9, 2020 at 12:46 AM Tim Flink  wrote:
> 
> > I'm working on something that looks for certain results in resultsdb
> > and I'm getting some strange results. I'm hoping someone here can
> > point out what I'm doing wrong.
> >
> > I'm hitting an issue where the data I'm getting back from resultsdb
> > via the api isn't matching what I see in the frontend. The result is
> > clearly in the db (I can get the data if I query the result ID) but
> > when I search for the result using one of its keywords, I get an
> > empty set back. What's even stranger is that this isn't consistent
> > - some results submitted around the same time return the results I
> > expect.
> >
> > I wrote up a quick script to show what I'm seeing:
> >
> > https://gist.github.com/tflink/1a1ed4263fbeb56b04442a948770965f
> >
> > It includes the output I'm seeing at the moment as I suspect it'll
> > start working as soon as someone else looks at it :)
> >
> > I've tried this on the resultsdb production machine and I'm seeing
> > the same results. I feel like I'm missing something obvious here so
> > if you see it, I'd appreciate the help.
> >
> > Thanks,
> >
> > Tim
> >  
> 
> I'm not sure I completely understood your description. However, I did
> notice that you're searching for
> switchboard-plug-about.2.6.2-1.fc31
> when you should be searching for
> switchboard-plug-about-2.6.2-1.fc31
> (a dot replaced by a dash)
> 
> That could solve the mystery, hopefully :)
> 
> Its results then show up just fine for me in the frontend:
> https://taskotron.fedoraproject.org/resultsdb/results?item:like=switchboard-plug-about-2.6.2-1.fc31*

I had a feeling it was something stupid and it was. Thanks for the help.

Tim


pgpVbnXBqU8ad.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org

seeing issues querying results by nvr/item in resultsdb

[Tim Flink]

I'm working on something that looks for certain results in resultsdb
and I'm getting some strange results. I'm hoping someone here can point
out what I'm doing wrong.

I'm hitting an issue where the data I'm getting back from resultsdb via
the api isn't matching what I see in the frontend. The result is
clearly in the db (I can get the data if I query the result ID) but
when I search for the result using one of its keywords, I get an empty
set back. What's even stranger is that this isn't consistent - some
results submitted around the same time return the results I expect.

I wrote up a quick script to show what I'm seeing:

https://gist.github.com/tflink/1a1ed4263fbeb56b04442a948770965f

It includes the output I'm seeing at the moment as I suspect it'll
start working as soon as someone else looks at it :)

I've tried this on the resultsdb production machine and I'm seeing the
same results. I feel like I'm missing something obvious here so if you
see it, I'd appreciate the help.

Thanks,

Tim


pgpfZm8yx5wb9.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org

Re: rpminspect Jenkins is effectively down

[Tim Flink]

That took a bit longer than I had hoped but as of the time I'm sending
out this email, the Jenkins instance running rpminspect is back up and
is in the process of slowly working through its backlog.

There are some rpminspect results that were lost and aren't currently
part of the backlog. My next work item is to get all of those
re-scheduled.

Unfortunately, I still don't know what caused the failure that required
a rebuild of the Jenkins master. I've reworked a few things and put some
job throttling in place to limit the number of concurrent jobs on the
Jenkins instance. Hopefully, that will keep the master from getting
overwhelmed and going down again. I'm also going to be putting more
monitoring in place soon - thanks to the Testing Farm folks for letting
us use their prometheus instance.

Please let me know if you notice anything not working. I'll send out
another email once the lost runs have been re-scheduled.

Tim

On Mon, 23 Mar 2020 10:29:28 -0600
Tim Flink  wrote:

> I figured I would start a new thread instead of continuing on with the
> old one.
> 
> The Jenkins instance running rpminspect has crapped itself for the
> second time in less than a week and it's currently not processing the
> rpminspect runs it should be.
> 
> There are also reports of missing rpminspect runs which likely stem
> from the Jenkins issues.
> 
> I'm working on it and will send updates as things are fixed and
> skipped runs are re-scheduled.
> 
> Tim



pgpJcIPUF7I67.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

rpminspect Jenkins is effectively down

[Tim Flink]

I figured I would start a new thread instead of continuing on with the
old one.

The Jenkins instance running rpminspect has crapped itself for the
second time in less than a week and it's currently not processing the
rpminspect runs it should be.

There are also reports of missing rpminspect runs which likely stem
from the Jenkins issues.

I'm working on it and will send updates as things are fixed and skipped
runs are re-scheduled.

Tim


pgpIHA5o5pnlu.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: [Test-Announce] Taskotron Going EOL on 2020-04-30

[Tim Flink]

On Sat, 7 Mar 2020 01:03:53 +0100
Miro Hrončok  wrote:

> On 07. 03. 20 0:29, Tim Flink wrote:
> > If you have any questions about this, feel free to reply to this
> > thread.  
> 
> Hello Tim.
> 
> I have 3 questions.
> 
> 1) On what level of Fedora leadership was this decision made (and
> where can I read about it)?

Much of it was an informal discussion between the Taskotron developers
where we came to the conclusion that Fedora CI was in a better place to
run these checks for Fedora.

> 2) Why are we removing something that arguably has a lot of value
> with something that doesn't exist yet?

I don't really have much to add to the conversation that has
already happened elsewhere in the thread. This particular EOL date was
chosen due to the infra move and the space constraints they have going
forward.

Even if we wanted to revive Taskotron at this point, a lot of work
would be needed to change things to fit into current CPE paradigms.
We'd also need to address the bit-rot from being in "minimal effort
maintenance mode" for years.

> 3) And to get a bit more specific: How do we rewrite our general
> Python versions checks [1] to the Jenkins thing and how do we deploy
> them? (Our point of contact for this was previously Kamil Páral --
> but I suppose that changes now, correct?)

I was under the impression that the python-versions check wasn't needed
going forward. Did I misunderstand something?

For the short term, I can hack those to run in Jenkins for now so that
it (and any others needed) continue to run and aren't disrupted.

They would eventually need to be ported to the new setup which I'm told
will be based around tmt. Some of those details have come up already and
the Fedora CI folks will have more information once more of the required
bits are in place.

> Thanks for running Taskotron so far. It helped us a lot in the past
> with the Python 2 to 3 transition.

I'm glad to hear that it's been helpful. Thank you for your support
over the years.

Tim

> [1] https://github.com/fedora-python/taskotron-python-versions
> 



pgp3y_HhQHUfs.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: [Test-Announce] Taskotron Going EOL on 2020-04-30

[Tim Flink]

On Fri, 6 Mar 2020 16:37:33 -0700
Jerry James  wrote:

> On Fri, Mar 6, 2020 at 4:31 PM Tim Flink  wrote:
> > In the short term, there is a Jenkins instance which is running
> > rpminspect. Rpminspect includes tests which are effectively the
> > same as rpmlint and rpmgrill which removes the need to run them.  
> 
> For packages with a .rpmlintrc file in the git repo,
> does rpminspect take that file into account?

The short version is no, not at the moment.

rpminspect is mostly capable of using custom configurations - that's
something that David Cantrell (the primary author of rpminspect) has
been talking about since he started promoting rpminspect.

It's a pretty simple matter to look for a config file in dist-git but I
don't believe that the exact format or mechanism for translating
something user generated into a partial config that rpminspect
understands has been figured out yet.

We were planning to do that in the Jenkins instance that is running
rpminspect but now that there is a new to-be-announced system that will
replace that setup later this year, I'm not sure it's worth the effort
to get that working in two places.

If this is something that you feel needs a higher priority, I'd suggest
starting a conversation with the Fedora CI folks on ci@

Thanks,

Tim


pgpsBU5wSx0_s.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Test-Announce] Taskotron Going EOL on 2020-04-30

[Tim Flink]

This is something that has been coming for quite a while now
and while it was discussed among QA and Infra, there hasn't been
enough communication with the rest of Fedora. For that, I apologize.

Taskotron has been in maintenance-only mode for a couple of years now
pending a replacement of some kind. That replacement has taken longer
to materialize than originally planned but the servers which run
Taskotron are almost out of warranty and will not be moving to the new
datacenter with the rest of Fedora's infrastructure.

Given all of this, we have decided that 2020-04-30 will be the day that
Taskotron will be turned off so that we're not trying to turn stuff off
in the middle of the infra move later this summer.

---
What does this mean for me?
---

If you're not a packager, you will probably not notice the shutdown.

If you are a packager, this will affect some of the results that you
currently see in Bodhi under the "Automated Tests" tab. At the moment,
most of those results come from Taskotron. If those checks are run in
the future, they will likely show up with slightly different names.


Is anything replacing Taskotron?


In the short term, there is a Jenkins instance which is running
rpminspect. Rpminspect includes tests which are effectively the same as
rpmlint and rpmgrill which removes the need to run them.

We already have rpminspect results going into production resultsdb
and showing up in Bodhi.

In the longer term, there will be a new solution to run rpminspect,
rpmdeplint and other static-analysis style checks coming from the Fedora
CI folks which they will be deploying before Flock.

-
What about ResultsDB?
-

ResultsDB is part of Taskotron but it is used by other bits like Bodhi
and Greenwave. The discussion around where ResultsDB will live going
forward and who will be responsible for the deployment is still ongoing
but ResultsDB will not be turned off as part of this EOL process.


If you have any questions about this, feel free to reply to this thread.

Thanks,

Tim


pgpFmy_Kw9u4i.pgp
Description: OpenPGP digital signature
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: taskotron going down for emergency maintenance

[Tim Flink]

Taskotron is back up but we're still having some issues with delays to
the incoming jobs.

We're still investigating but data should be flowing again, even if it
is a bit delayed.

Thanks,

Tim

On Thu, 27 Feb 2020 10:09:33 -0700
Tim Flink  wrote:

> The subject says it all, really.
> 
> Taskotron is having some problems with an internal component, it can't
> wait for a better time and we need some downtime to fix it.
> 
> If all goes well, it should be back up shortly. I'll send another
> email to update once we're done.
> 
> Tim



pgpR7q9Lx1xXj.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

taskotron going down for emergency maintenance

[Tim Flink]

The subject says it all, really.

Taskotron is having some problems with an internal component, it can't
wait for a better time and we need some downtime to fix it.

If all goes well, it should be back up shortly. I'll send another email
to update once we're done.

Tim


pgp4sFi8EO6c7.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Planned Outage - Taskotron and ResultsDB - 2019-11-26 19:00 UTC

[Tim Flink]

I hit a hiccup during the upgrade but everything should be back to
normal and upgraded.

If you notice anything not working correctly, please let us know in
#fedora-admin or #fedora-qa.

Thanks,

Tim

On Tue, 26 Nov 2019 11:58:36 -0700
Tim Flink  wrote:

> Apologies for the last minute nature of this outage, the details
> behind the upgrade were under debate and we didn't want to announce a
> time until we were sure about what was going to happen when.
> 
> Seeing as the machines are running F29, they need to be upgraded as
> it's going EOL today.
> 
> Tim
> 
> 
> 
> 
> There will be an outage starting at 2019-11-26 21:00 UTC, which will
> last approximately 3 hours.
> 
> To convert UTC to your local time, take a look at
> https://fedoraproject.org/wiki/UTCHowto or run:
> 
> date -d '2019-11-26 19:00 UTC'
> 
> Reason for outage:
> 
> We will be upgrading the servers which host Taskotron and ResultsDB to
> newer versions of Fedora.
> 
> Affected Services:
> 
> Taskotron, ResultsDB and anything which uses ResultsDB as a data
> source (Bodhi, gating etc.)
> 
> Ticket Link:
> 
> https://pagure.io/fedora-infrastructure/issue/8420
> 
> Contact Information:
> 
> Please join #fedora-admin in irc.freenode.net or add comments to the
> ticket for this outage above.



pgp0vHeRKl7Wq.pgp
Description: OpenPGP digital signature
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Planned Outage - Taskotron and ResultsDB - 2019-11-26 19:00 UTC

[Tim Flink]

Apologies for the last minute nature of this outage, the details
behind the upgrade were under debate and we didn't want to announce a
time until we were sure about what was going to happen when.

Seeing as the machines are running F29, they need to be upgraded as
it's going EOL today.

Tim




There will be an outage starting at 2019-11-26 21:00 UTC, which will
last approximately 3 hours.

To convert UTC to your local time, take a look at
https://fedoraproject.org/wiki/UTCHowto or run:

date -d '2019-11-26 19:00 UTC'

Reason for outage:

We will be upgrading the servers which host Taskotron and ResultsDB to
newer versions of Fedora.

Affected Services:

Taskotron, ResultsDB and anything which uses ResultsDB as a data source
(Bodhi, gating etc.)

Ticket Link:

https://pagure.io/fedora-infrastructure/issue/8420

Contact Information:

Please join #fedora-admin in irc.freenode.net or add comments to the
ticket for this outage above.


pgpAIRab4ZYRV.pgp
Description: OpenPGP digital signature
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Planned Outage - Taskotron and ResultsDB - 2019-11-26 19:00 UTC

[Tim Flink]

I hit a hiccup during the upgrade but everything should be back to
normal and upgraded.

If you notice anything not working correctly, please let us know in
#fedora-admin or #fedora-qa.

Thanks,

Tim

On Tue, 26 Nov 2019 11:58:36 -0700
Tim Flink  wrote:

> Apologies for the last minute nature of this outage, the details
> behind the upgrade were under debate and we didn't want to announce a
> time until we were sure about what was going to happen when.
> 
> Seeing as the machines are running F29, they need to be upgraded as
> it's going EOL today.
> 
> Tim
> 
> 
> 
> 
> There will be an outage starting at 2019-11-26 21:00 UTC, which will
> last approximately 3 hours.
> 
> To convert UTC to your local time, take a look at
> https://fedoraproject.org/wiki/UTCHowto or run:
> 
> date -d '2019-11-26 19:00 UTC'
> 
> Reason for outage:
> 
> We will be upgrading the servers which host Taskotron and ResultsDB to
> newer versions of Fedora.
> 
> Affected Services:
> 
> Taskotron, ResultsDB and anything which uses ResultsDB as a data
> source (Bodhi, gating etc.)
> 
> Ticket Link:
> 
> https://pagure.io/fedora-infrastructure/issue/8420
> 
> Contact Information:
> 
> Please join #fedora-admin in irc.freenode.net or add comments to the
> ticket for this outage above.



pgp9ManwadQny.pgp
Description: OpenPGP digital signature
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org

Planned Outage - Taskotron and ResultsDB - 2019-11-26 19:00 UTC

[Tim Flink]

Apologies for the last minute nature of this outage, the details
behind the upgrade were under debate and we didn't want to announce a
time until we were sure about what was going to happen when.

Seeing as the machines are running F29, they need to be upgraded as
it's going EOL today.

Tim




There will be an outage starting at 2019-11-26 21:00 UTC, which will
last approximately 3 hours.

To convert UTC to your local time, take a look at
https://fedoraproject.org/wiki/UTCHowto or run:

date -d '2019-11-26 19:00 UTC'

Reason for outage:

We will be upgrading the servers which host Taskotron and ResultsDB to
newer versions of Fedora.

Affected Services:

Taskotron, ResultsDB and anything which uses ResultsDB as a data source
(Bodhi, gating etc.)

Ticket Link:

https://pagure.io/fedora-infrastructure/issue/8420

Contact Information:

Please join #fedora-admin in irc.freenode.net or add comments to the
ticket for this outage above.


pgpi88mgzU0B4.pgp
Description: OpenPGP digital signature
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org

Re: Do people not care about broken dependencies?

[Tim Flink]

On Mon, 10 Jun 2019 11:03:56 +0200
Felix Schwarz  wrote:

> +1 to prevent broken dependencies to be pushed into stable. If Fedora
> aims to be a "polished"/"user friendly" distro users should never
> have to deal with broken dependencies.
> 
> Also packages with broken dependencies should not be part of a
> release (maybe not auto-retired if they are still ok for other
> releases). Felix

Adam mentioned this elsewhere in the thread, but there are folks who
care about this but we also have many other things to take care of.

This is something that is on my radar to add to Fedora CI but there are
a bunch of other things which need to be done first and I've not gotten
to the point where I've even written down these plans in a coherant
fashion.

As we get closer to making it a reality, I'll be writing about it more.

Tim


pgpGxbUoK4qub.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: rpmlint whitelisting broken in taskotron?

[Tim Flink]

On Fri, 26 Apr 2019 20:33:43 +0200
Fabio Valentini  wrote:

> On Fri, Apr 26, 2019, 20:24 Tim Flink  wrote:
> 
> > On Fri, 26 Apr 2019 16:42:30 +0200
> > Fabio Valentini  wrote:
> >  
> > > Hi,
> > >
> > > I've noticed that my bodhi updates started showing rpmlint errors
> > > for my packages again, where they were previously silent because
> > > I supply a $SRCNAME.rpmlintrc file in my dist-git repos.
> > >
> > > It looks like taskotron is broken and/or ignores this file again.
> > > Is this a known issue?
> > >
> > > For example, this build from today shows rpmlint issues that are
> > > explicitly whitelisted (using the file locally suppresses the
> > > warnings/errors as intended):
> > >
> > > update:
> > > https://bodhi.fedoraproject.org/updates/FEDORA-2019-ecaba1eef1 in
> > > repo: 
> > https://src.fedoraproject.org/rpms/elementary-greeter/blob/f30/f/elementary-greeter.rpmlintrc
> >
> > This was not a known issue, no. It stems from us depending on the
> > cgit interface which was taken down a few days ago - we're getting
> > 404s when we try to grab the rpmlintrc file
> >
> > I'm still looking into this but have filed an issue track it:
> >
> > https://pagure.io/taskotron/libtaskotron/issue/429
> >
> > Thanks for the report and sorry for the bother.
> >
> > Tim
> >  
> 
> Great, thanks for looking into it!
> 
> pagure provides really simple URLs to fetch raw files, so it
> shouldn't be hard to adapt the code from cgit, for example:
> 
> https://src.fedoraproject.org/rpms/elementary-photos/raw/47e73b7ac14dea07b5fcbd39b5f2aff67fea4fbc/f/elementary-photos.rpmlintrc

The freeze break request I needed to update the packages was approved
over the weekend and libtaskotron has been updated in production.

This issue with finding package-specific rpmlintrc files should be
fixed. Please let us know if you continue to see the issue.

Thanks,

Tim


pgpwZidTguql8.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: rpmlint whitelisting broken in taskotron?

[Tim Flink]

On Fri, 26 Apr 2019 16:42:30 +0200
Fabio Valentini  wrote:

> Hi,
> 
> I've noticed that my bodhi updates started showing rpmlint errors for
> my packages again, where they were previously silent because I supply
> a $SRCNAME.rpmlintrc file in my dist-git repos.
> 
> It looks like taskotron is broken and/or ignores this file again. Is
> this a known issue?
> 
> For example, this build from today shows rpmlint issues that are
> explicitly whitelisted (using the file locally suppresses the
> warnings/errors as intended):
> 
> update: https://bodhi.fedoraproject.org/updates/FEDORA-2019-ecaba1eef1
> in repo:
> https://src.fedoraproject.org/rpms/elementary-greeter/blob/f30/f/elementary-greeter.rpmlintrc

This was not a known issue, no. It stems from us depending on the cgit
interface which was taken down a few days ago - we're getting 404s when
we try to grab the rpmlintrc file 

I'm still looking into this but have filed an issue track it:

https://pagure.io/taskotron/libtaskotron/issue/429

Thanks for the report and sorry for the bother.

Tim


pgpoygVPxciLF.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Planned Outage: Taskotron 2019-04-09 16:00 UTC

[Tim Flink]

There will be an outage starting at 2019-04-09 16:00 UTC, which will
last approximately 4 hours.

To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:

date -d '2019-04-09 16:00UTC'

Reason for outage:

Major upgrade to Taskotron

Affected Services:

Taskotron
Bodhi (displaying results)
Greenwave

Ticket Link:

https://pagure.io/fedora-infrastructure/issue/7686

Please join #fedora-admin or #fedora-noc on irc.freenode.net or add
comments to the ticket for this outage above.
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Planned Outage: Taskotron 2019-04-09 16:00 UTC

[Tim Flink]

There will be an outage starting at 2019-04-09 16:00 UTC, which will
last approximately 4 hours.

To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:

date -d '2019-04-09 16:00UTC'

Reason for outage:

Major upgrade to Taskotron

Affected Services:

Taskotron
Bodhi (displaying results)
Greenwave

Ticket Link:

https://pagure.io/fedora-infrastructure/issue/7686

Please join #fedora-admin or #fedora-noc on irc.freenode.net or add
comments to the ticket for this outage above.
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org

Proposal to CANCEL: 2018-02-05 QA Devel Meeting

[Tim Flink]

I'm not aware of any topics that need urgent discussion this week, so I
propose that we cancel the QA Devel meeting on 2018-02-05.

If there are some topics that need discussing, please reply here and
the meeting can happen.

Tim


pgpOa9Cero_lx.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: Test gating enabled in Bodhi

[Tim Flink]

On Tue, 23 Jan 2018 11:06:59 +0100
Pierre-Yves Chibon  wrote:

> On Tue, Jan 23, 2018 at 09:42:50AM +, Richard W.M. Jones wrote:
> > On Tue, Jan 23, 2018 at 10:28:14AM +0100, Pierre-Yves Chibon
> > wrote:  
> > > Good Morning Fedorans!
> > > 
> > > On Thursday, a new version of Bodhi was deployed that enabled
> > > Bodhi to gate updates based on test results. You may notice a
> > > "Test Gating Status" message in the right have side of the page.
> > > 
> > > One thing to know about this is that there is currently a
> > > confusing issue where Bodhi will say that the tests have failed
> > > when the tests haven't finished running[0]. We are working on
> > > solving that issue, but for now you can just wait a while and it
> > > should report the result once all the tests have finished.
> > > 
> > > There are three tests that must pass in order for updates to go
> > > to stable:
> > > 
> > > 0. dist.depcheck - to make sure the update's dependencies are
> > > available. 1. dist.abicheck - to make sure the update's ABI
> > > remains stable in a given Fedora release.
> > > 2. AtomicCI pipeline - packages that are part of the Atomic Host
> > > *and* include in their dist-git tests, must have these tests
> > > passed in the AtomicCI pipeline  
> > 
> > This update cannot be pushed:
> > 
> >   https://bodhi.fedoraproject.org/updates/FEDORA-2018-932548462e
> > 
> > When I click on the "automated tests" it says:
> > 
> >   "Automated Test Results
> >   Failed to talk to Greenwave.
> >   The update can not be pushed: 1 of 2 required tests not found"
> > 
> > and then the only "red" test (ie. failure) is rpmlint which is just
> > a bunch of rpmlint being wrong.  Nothing about "dist.depcheck" or
> > "dist.abicheck" is mentioned anywhere.  
> 
> abicheck is the first test results shown in the automated tests tab
> but indeed, no depcheck mentioned. Maybe someone from taskotron could
> help us on this?

In this particular case, I think that the update in question went from
updates-testing-pending to updates-testing while taskotron was down for
an updgrade on the 9th. There are no rpmdeplint results in resultsdb
which is what I assume greenwave is complaining about.

To be honest, we've always assumed that this situation was unlikely,
verging on impossible due to the way that rpmdeplint is scheduled and
run. Obviously, it's more likely than we thought and is an issue that
we'll need to address going forward before gating can be enabled for
everything.

Actually, all of these issues are a bit surprising and there are
several things which have gone from "eh, nobody cares. we'll get around
to it someday" to "we should probably get that figured out now-ish" due
to the issues raised around the gating in bodhi.

Tim


pgp4aAexCmlR9.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Making ResultsDB dumps public?

[Tim Flink]

On Sun, 14 Jan 2018 14:19:54 -0800
Kevin Fenzi  wrote:

> On 01/11/2018 07:44 AM, Kamil Paral wrote:
> > On Wed, Nov 1, 2017 at 7:48 PM, Kevin Fenzi  > > wrote:
> > 
> > On 10/24/2017 03:36 AM, Kamil Paral wrote:  
> > > On Sun, Oct 8, 2017 at 12:14 AM, Kevin Fenzi  > > > wrote: 
> > >> They should be there starting tomorrow.
> > >>  
> > >
> > >
> > > I still don't see any dumps in there. Is it still being
> > > worked on?  
> > 
> > I seem to have made a typo in the script that does this. ;(
> > 
> > Sent in a freeze break request with a fix
> > 
> > 
> > I and Josef looked at it today, and it seems it contains some very
> > old data - from Jan 2017 to April 2017. We failed to find the
> > script that generates the dump in infra ansible, so we can't really
> > debug what's wrong. Can you please look at it or give us some
> > pointers?  
> 
> Odd.
> 
> It's
> https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/batcave/files/public-db-copy.sh?id=778dae3
> which runs on batcave01 and runs:
> https://infrastructure.fedoraproject.org/cgit/ansible.git/plain/scripts/public-db-copy?id=778dae3
> 
> scp db-qa01.qa.fedoraproject.org:/resultsdb-$(date +%F).dump.xz
> /srv/web/infra/db-dumps/resultsdb.dump.xz
> 
> and on db-qa01.qa:/backups:
> 
> -rw-r--r--. 1 postgres postgres 142589024 Apr 12  2016
> resultsdb-2016-04-12.dump.xz
> -rw-r--r--. 1 postgres postgres  50184088 Jun 20  2017
> resultsdb-2017-06-20.dump.xz
> -rw-r--r--. 1 postgres postgres  50367072 Jan 13 01:59
> resultsdb-2018-01-13.dump.xz
> -rw-r--r--. 1 postgres postgres  50367072 Jan 14 01:12
> resultsdb-2018-01-14.dump.xz
> 
> It claims to be the dump from today... so not sure whats going on.

The database for production resultsdb is on db-qa02.qa instead of
db-qa01.qa. 

From my read of those scripts, I suspect that is the cause of the
public dumps being old.

Tim


pgpPJBmj2cc4C.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Planned Outage - Taskotron update - 2018-01-09 @ 22:00 UTC

[Tim Flink]

Apologies on not announcing this farther ahead of time.

There will be an outage starting at 2018-01-09 22:00:00 UTC, which will
last 4-6 hours.

To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:

date -d '2018-01-09 22:00:00 UTC'

Reason for outage:

We are upgrading the hosts which run the services required for
Taskotron. This will not affect resultsdb as this will be upgraded at a
later date.

Affected Services:

taskotron.fedoraproject.org

Contact Information:

Please join #fedora-admin or #fedora-noc on irc.freenode.net


pgp9xEPsN64z7.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

2018-01-08 @ 15:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

# Fedora QA Devel Meeting
# Date: 2018-01-08
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net


https://fedoraproject.org/wiki/QA:Qadevel-20180108

If you have any additional topics, please reply to this thread or add
them in the wiki doc.

Tim


pgpFsj5HPfbjN.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

taskotron-dev rebuild

[Tim Flink]

After much fun, František, Josef and I got taskotron-dev re-deployed as
F27.

It's not running any ansiblize builds yet but that's planned for
tomorrow (hopefully)

Tim


pgpywid8Z_Xex.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: Please review - Infra Ansible - move slaves from home to srv

[Tim Flink]

On Tue, 21 Nov 2017 12:08:07 +0100
Josef Skladanka <jskla...@redhat.com> wrote:

> The raw diff was attached to the original email, I could have
> mentioned that, I guess. /me was not able to make gmail send
> unformatted/unwrapped text.
> Sorry for the inconvenience.

Reading the attachment is a lot better. One might hope that I would
have learned how to do the email by now but apparently that's not always
true :-/

Thanks,

Tim

> j.
> 
> On Mon, Nov 20, 2017 at 6:32 PM, Tim Flink <tfl...@redhat.com> wrote:
> 
> > On Mon, 20 Nov 2017 10:36:03 +0100
> > Josef Skladanka <jskla...@redhat.com> wrote:
> >  
> > > I'm not sure what is the best way to ask for review for a
> > > pagure-less project, since we don't use Phabricator any more,
> > > so... let the funmail begin:  
> >
> > The wrapped diff is hard to read but it looks pretty good to me. I
> > think that the patch should be applied in parts as we reimage the
> > client-host machines but that's more of a nitpick :)
> >
> > Tim
> >  
> > > diff --git a/inventory/host_vars/qa10.qa.fedoraproject.org
> > > b/inventory/host_vars/qa10.qa.fedoraproject.org
> > > index 297f614e3..d2119dc47 100644
> > > --- a/inventory/host_vars/qa10.qa.fedoraproject.org
> > > +++ b/inventory/host_vars/qa10.qa.fedoraproject.org
> > > @@ -9,18 +9,18 @@ gw: 10.5.124.254
> > >
> > >  short_hostname: qa10.qa
> > >  slaves:
> > > -  - { user: "{{ short_hostname }}-1", home:
> > > "/home/{{ short_hostname }}-1", dir:
> > > "/home/{{ short_hostname }}-1/slave" }
> > > -  - { user: "{{ short_hostname }}-2", home:
> > > "/home/{{ short_hostname }}-2", dir:
> > > "/home/{{ short_hostname }}-2/slave" }
> > > -  - { user: "{{ short_hostname }}-3", home:
> > > "/home/{{ short_hostname }}-3", dir:
> > > "/home/{{ short_hostname }}-3/slave" }
> > > -  - { user: "{{ short_hostname }}-4", home:
> > > "/home/{{ short_hostname }}-4", dir:
> > > "/home/{{ short_hostname }}-4/slave" }
> > > -  - { user: "{{ short_hostname }}-5", home:
> > > "/home/{{ short_hostname }}-5", dir:
> > > "/home/{{ short_hostname }}-5/slave" }
> > > -  - { user: "{{ short_hostname }}-6", home:
> > > "/home/{{ short_hostname }}-6", dir:
> > > "/home/{{ short_hostname }}-6/slave" }
> > > -  - { user: "{{ short_hostname }}-7", home:
> > > "/home/{{ short_hostname }}-7", dir:
> > > "/home/{{ short_hostname }}-7/slave" }
> > > -  - { user: "{{ short_hostname }}-8", home:
> > > "/home/{{ short_hostname }}-8", dir:
> > > "/home/{{ short_hostname }}-8/slave" }
> > > -  - { user: "{{ short_hostname }}-9", home:
> > > "/home/{{ short_hostname }}-9", dir:
> > > "/home/{{ short_hostname }}-9/slave" }
> > > -  - { user: "{{ short_hostname }}-10", home:
> > > "/home/{{ short_hostname }}-10", dir:
> > > "/home/{{ short_hostname }}-10/slave" }
> > > -  - { user: "{{ short_hostname }}-11", home:
> > > "/home/{{ short_hostname }}-11", dir:
> > > "/home/{{ short_hostname }}-11/slave" }
> > > -  - { user: "{{ short_hostname }}-12", home:
> > > "/home/{{ short_hostname }}-12", dir:
> > > "/home/{{ short_hostname }}-12/slave" }
> > > -  - { user: "{{ short_hostname }}-13", home:
> > > "/home/{{ short_hostname }}-13", dir:
> > > "/home/{{ short_hostname }}-13/slave" }
> > > -  - { user: "{{ short_hostname }}-14", home:
> > > "/home/{{ short_hostname }}-14", dir:
> > > "/home/{{ short_hostname }}-14/slave" }
> > > -  - { user: "{{ short_hostname }}-15", home:
> > > "/home/{{ short_hostname }}-15", dir:
> > > "/home/{{ short_hostname }}-15/slave" }
> > > +  - { user: "{{ short_hostname }}-1", home: "/srv/buildslaves/{{
> > > short_hostname }}-1", dir:
> > > "/srv/buildslaves/{{ short_hostname }}-1/slave" }
> > > +  - { user: "{{ short_hostname }}-2", home: "/srv/buildslaves/{{
> > > short_hostname }}-2", dir:
> > > "/srv/buildslaves/{{ short_hostname }}-2/slave" }
> > > + 

Re: Please review - Infra Ansible - move slaves from home to srv

[Tim Flink]

I applied the qa11 bits and everything seems to be working.

Tim

On Mon, 20 Nov 2017 10:32:54 -0700
Tim Flink <tfl...@redhat.com> wrote:

> On Mon, 20 Nov 2017 10:36:03 +0100
> Josef Skladanka <jskla...@redhat.com> wrote:
> 
> > I'm not sure what is the best way to ask for review for a
> > pagure-less project, since we don't use Phabricator any more, so...
> > let the funmail begin:  
> 
> The wrapped diff is hard to read but it looks pretty good to me. I
> think that the patch should be applied in parts as we reimage the
> client-host machines but that's more of a nitpick :)
> 
> Tim
> 
> > diff --git a/inventory/host_vars/qa10.qa.fedoraproject.org
> > b/inventory/host_vars/qa10.qa.fedoraproject.org
> > index 297f614e3..d2119dc47 100644
> > --- a/inventory/host_vars/qa10.qa.fedoraproject.org
> > +++ b/inventory/host_vars/qa10.qa.fedoraproject.org
> > @@ -9,18 +9,18 @@ gw: 10.5.124.254
> > 
> >  short_hostname: qa10.qa
> >  slaves:
> > -  - { user: "{{ short_hostname }}-1", home:
> > "/home/{{ short_hostname }}-1", dir:
> > "/home/{{ short_hostname }}-1/slave" }
> > -  - { user: "{{ short_hostname }}-2", home:
> > "/home/{{ short_hostname }}-2", dir:
> > "/home/{{ short_hostname }}-2/slave" }
> > -  - { user: "{{ short_hostname }}-3", home:
> > "/home/{{ short_hostname }}-3", dir:
> > "/home/{{ short_hostname }}-3/slave" }
> > -  - { user: "{{ short_hostname }}-4", home:
> > "/home/{{ short_hostname }}-4", dir:
> > "/home/{{ short_hostname }}-4/slave" }
> > -  - { user: "{{ short_hostname }}-5", home:
> > "/home/{{ short_hostname }}-5", dir:
> > "/home/{{ short_hostname }}-5/slave" }
> > -  - { user: "{{ short_hostname }}-6", home:
> > "/home/{{ short_hostname }}-6", dir:
> > "/home/{{ short_hostname }}-6/slave" }
> > -  - { user: "{{ short_hostname }}-7", home:
> > "/home/{{ short_hostname }}-7", dir:
> > "/home/{{ short_hostname }}-7/slave" }
> > -  - { user: "{{ short_hostname }}-8", home:
> > "/home/{{ short_hostname }}-8", dir:
> > "/home/{{ short_hostname }}-8/slave" }
> > -  - { user: "{{ short_hostname }}-9", home:
> > "/home/{{ short_hostname }}-9", dir:
> > "/home/{{ short_hostname }}-9/slave" }
> > -  - { user: "{{ short_hostname }}-10", home:
> > "/home/{{ short_hostname }}-10", dir:
> > "/home/{{ short_hostname }}-10/slave" }
> > -  - { user: "{{ short_hostname }}-11", home:
> > "/home/{{ short_hostname }}-11", dir:
> > "/home/{{ short_hostname }}-11/slave" }
> > -  - { user: "{{ short_hostname }}-12", home:
> > "/home/{{ short_hostname }}-12", dir:
> > "/home/{{ short_hostname }}-12/slave" }
> > -  - { user: "{{ short_hostname }}-13", home:
> > "/home/{{ short_hostname }}-13", dir:
> > "/home/{{ short_hostname }}-13/slave" }
> > -  - { user: "{{ short_hostname }}-14", home:
> > "/home/{{ short_hostname }}-14", dir:
> > "/home/{{ short_hostname }}-14/slave" }
> > -  - { user: "{{ short_hostname }}-15", home:
> > "/home/{{ short_hostname }}-15", dir:
> > "/home/{{ short_hostname }}-15/slave" }
> > +  - { user: "{{ short_hostname }}-1", home: "/srv/buildslaves/{{
> > short_hostname }}-1", dir:
> > "/srv/buildslaves/{{ short_hostname }}-1/slave" }
> > +  - { user: "{{ short_hostname }}-2", home: "/srv/buildslaves/{{
> > short_hostname }}-2", dir:
> > "/srv/buildslaves/{{ short_hostname }}-2/slave" }
> > +  - { user: "{{ short_hostname }}-3", home: "/srv/buildslaves/{{
> > short_hostname }}-3", dir:
> > "/srv/buildslaves/{{ short_hostname }}-3/slave" }
> > +  - { user: "{{ short_hostname }}-4", home: "/srv/buildslaves/{{
> > short_hostname }}-4", dir:
> > "/srv/buildslaves/{{ short_hostname }}-4/slave" }
> > +  - { user: "{{ short_hostname }}-5", home: "/srv/buildslaves/{{
> > short_hostname }}-5", dir:
> > "/srv/buildslaves/{{ short_hostname }}-5/slave" }
> > +  - { user: "{{ short_hostname }}-6", home: "/srv/buildslaves/{{
> > short_hostname }}-6", dir:
> > "/srv/buildslaves/{{ short

Re: Please review - Infra Ansible - move slaves from home to srv

[Tim Flink]

On Mon, 20 Nov 2017 10:36:03 +0100
Josef Skladanka  wrote:

> I'm not sure what is the best way to ask for review for a pagure-less
> project, since we don't use Phabricator any more, so... let the
> funmail begin:

The wrapped diff is hard to read but it looks pretty good to me. I
think that the patch should be applied in parts as we reimage the
client-host machines but that's more of a nitpick :)

Tim

> diff --git a/inventory/host_vars/qa10.qa.fedoraproject.org
> b/inventory/host_vars/qa10.qa.fedoraproject.org
> index 297f614e3..d2119dc47 100644
> --- a/inventory/host_vars/qa10.qa.fedoraproject.org
> +++ b/inventory/host_vars/qa10.qa.fedoraproject.org
> @@ -9,18 +9,18 @@ gw: 10.5.124.254
> 
>  short_hostname: qa10.qa
>  slaves:
> -  - { user: "{{ short_hostname }}-1", home: "/home/{{ short_hostname
> }}-1", dir: "/home/{{ short_hostname }}-1/slave" }
> -  - { user: "{{ short_hostname }}-2", home: "/home/{{ short_hostname
> }}-2", dir: "/home/{{ short_hostname }}-2/slave" }
> -  - { user: "{{ short_hostname }}-3", home: "/home/{{ short_hostname
> }}-3", dir: "/home/{{ short_hostname }}-3/slave" }
> -  - { user: "{{ short_hostname }}-4", home: "/home/{{ short_hostname
> }}-4", dir: "/home/{{ short_hostname }}-4/slave" }
> -  - { user: "{{ short_hostname }}-5", home: "/home/{{ short_hostname
> }}-5", dir: "/home/{{ short_hostname }}-5/slave" }
> -  - { user: "{{ short_hostname }}-6", home: "/home/{{ short_hostname
> }}-6", dir: "/home/{{ short_hostname }}-6/slave" }
> -  - { user: "{{ short_hostname }}-7", home: "/home/{{ short_hostname
> }}-7", dir: "/home/{{ short_hostname }}-7/slave" }
> -  - { user: "{{ short_hostname }}-8", home: "/home/{{ short_hostname
> }}-8", dir: "/home/{{ short_hostname }}-8/slave" }
> -  - { user: "{{ short_hostname }}-9", home: "/home/{{ short_hostname
> }}-9", dir: "/home/{{ short_hostname }}-9/slave" }
> -  - { user: "{{ short_hostname }}-10", home: "/home/{{ short_hostname
> }}-10", dir: "/home/{{ short_hostname }}-10/slave" }
> -  - { user: "{{ short_hostname }}-11", home: "/home/{{ short_hostname
> }}-11", dir: "/home/{{ short_hostname }}-11/slave" }
> -  - { user: "{{ short_hostname }}-12", home: "/home/{{ short_hostname
> }}-12", dir: "/home/{{ short_hostname }}-12/slave" }
> -  - { user: "{{ short_hostname }}-13", home: "/home/{{ short_hostname
> }}-13", dir: "/home/{{ short_hostname }}-13/slave" }
> -  - { user: "{{ short_hostname }}-14", home: "/home/{{ short_hostname
> }}-14", dir: "/home/{{ short_hostname }}-14/slave" }
> -  - { user: "{{ short_hostname }}-15", home: "/home/{{ short_hostname
> }}-15", dir: "/home/{{ short_hostname }}-15/slave" }
> +  - { user: "{{ short_hostname }}-1", home: "/srv/buildslaves/{{
> short_hostname }}-1", dir:
> "/srv/buildslaves/{{ short_hostname }}-1/slave" }
> +  - { user: "{{ short_hostname }}-2", home: "/srv/buildslaves/{{
> short_hostname }}-2", dir:
> "/srv/buildslaves/{{ short_hostname }}-2/slave" }
> +  - { user: "{{ short_hostname }}-3", home: "/srv/buildslaves/{{
> short_hostname }}-3", dir:
> "/srv/buildslaves/{{ short_hostname }}-3/slave" }
> +  - { user: "{{ short_hostname }}-4", home: "/srv/buildslaves/{{
> short_hostname }}-4", dir:
> "/srv/buildslaves/{{ short_hostname }}-4/slave" }
> +  - { user: "{{ short_hostname }}-5", home: "/srv/buildslaves/{{
> short_hostname }}-5", dir:
> "/srv/buildslaves/{{ short_hostname }}-5/slave" }
> +  - { user: "{{ short_hostname }}-6", home: "/srv/buildslaves/{{
> short_hostname }}-6", dir:
> "/srv/buildslaves/{{ short_hostname }}-6/slave" }
> +  - { user: "{{ short_hostname }}-7", home: "/srv/buildslaves/{{
> short_hostname }}-7", dir:
> "/srv/buildslaves/{{ short_hostname }}-7/slave" }
> +  - { user: "{{ short_hostname }}-8", home: "/srv/buildslaves/{{
> short_hostname }}-8", dir:
> "/srv/buildslaves/{{ short_hostname }}-8/slave" }
> +  - { user: "{{ short_hostname }}-9", home: "/srv/buildslaves/{{
> short_hostname }}-9", dir:
> "/srv/buildslaves/{{ short_hostname }}-9/slave" }
> +  - { user: "{{ short_hostname }}-10", home: "/srv/buildslaves/{{
> short_hostname }}-10", dir: "/srv/buildslaves/{{ short_hostname
> }}-10/slave" }
> +  - { user: "{{ short_hostname }}-11", home: "/srv/buildslaves/{{
> short_hostname }}-11", dir: "/srv/buildslaves/{{ short_hostname
> }}-11/slave" }
> +  - { user: "{{ short_hostname }}-12", home: "/srv/buildslaves/{{
> short_hostname }}-12", dir: "/srv/buildslaves/{{ short_hostname
> }}-12/slave" }
> +  - { user: "{{ short_hostname }}-13", home: "/srv/buildslaves/{{
> short_hostname }}-13", dir: "/srv/buildslaves/{{ short_hostname
> }}-13/slave" }
> +  - { user: "{{ short_hostname }}-14", home: "/srv/buildslaves/{{
> short_hostname }}-14", dir: "/srv/buildslaves/{{ short_hostname
> }}-14/slave" }
> +  - { user: "{{ short_hostname }}-15", home: "/srv/buildslaves/{{
> short_hostname }}-15", dir: "/srv/buildslaves/{{ short_hostname
> }}-15/slave" }
> diff --git a/inventory/host_vars/qa11.qa.fedoraproject.org
> 

2017-11-20 Fedora QA Devel Meeting Minutes

[Tim Flink]

=
#fedora-meeting-1: fedora-qadevel
=

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-11-20/fedora-qadevel.2017-11-20-15.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-11-20/fedora-qadevel.2017-11-20-15.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-11-20/fedora-qadevel.2017-11-20-15.00.log.html


Meeting summary
---
* Roll Call  (tflink, 15:00:29)

* Announcements and Information  (tflink, 15:05:25)
  * got libtaskotron POC using openstack working - tflink  (tflink,
15:05:35)
  * more work on using disk-image-builder to build images for Taskotron
- tflink  (tflink, 15:05:36)
  * added 'pull_request' type to libtaskotron -- kparal  (tflink,
15:05:36)
  * built scratch libtaskotron and taskotron-trigger and deployed to dev
in order to get github pull-request triggered tasks working --
kparal  (tflink, 15:05:36)
  * updated yumrepoinfo in libtaskotron and on servers to reflect F27
being stable -- kparal  (tflink, 15:05:36)

* What to do about staging?  (tflink, 15:12:41)
  * no immediate objections to the idea of dismantling most of taskotron
stg to free up a worker for openqa  (tflink, 15:32:02)

* Moving to the cloud?  (tflink, 15:35:45)
  * no immediate objections to the idea of moving taskotron to use
openstack instances instead of local VMs on client hosts for our
deployments  (tflink, 15:56:40)

* image "building" monkey business  (tflink, 15:58:07)
  * LINK: https://docs.openstack.org/diskimage-builder/latest/
(tflink, 15:58:42)
  * LINK:

https://docs.openstack.org/diskimage-builder/latest/user_guide/building_an_image.html#disk-image-layout
(tflink, 16:06:40)
  * no immediate objections to explore switching over to
diskimage-builder to create images  (tflink, 16:27:34)

* initial plan of action  (tflink, 16:28:41)
  * LINK:

https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org/thread/ADQQOZ5XZJN7I3HBHAYXONVTQMZFWROK/
(jskladan, 16:34:55)

* Open Floor  (tflink, 16:55:10)

Meeting ended at 16:56:29 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* tflink (228)
* kparal (106)
* jskladan (80)
* zodbot (5)
* frantisekz (4)
* lbrabec (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot



pgpX_ZcUHN0qB.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-11-20 @ 15:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

# Fedora QA Devel Meeting
# Date: 2017-11-20
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net


https://fedoraproject.org/wiki/QA:Qadevel-20171120

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

Topics
---
  - What to do about Taskotron staging
  - Moving to the cloud?
  - disk-image-builder worth looking at more?

Potential Other Topics
--

  - deployment of ansiblize branches

Open Floor
--
  - TBD


pgpOgalGwOaSJ.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-10-16 @ 14:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

# Fedora QA Devel Meeting
# Date: 2017-10-16
# Time: 14:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net


https://fedoraproject.org/wiki/QA:Qadevel-20171016

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
--

  - deployment of ansiblize branches

Open Floor
--
  - TBD


pgpE7_kHXa4TR.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: Making ResultsDB dumps public?

[Tim Flink]

On Mon, 2 Oct 2017 14:12:54 -0700
Kevin Fenzi <ke...@scrye.com> wrote:

> On 09/25/2017 07:13 AM, Tim Flink wrote:
> > On Mon, 25 Sep 2017 05:37:03 -0400
> > Harold Dost <haroldd...@gmail.com> wrote:
> >   
> >> Assuming that the schema [1] is correct, there should be no
> >> personal or secret information. Though it would be good to
> >> validate that there aren't any unexpected tables.
> >>
> >> [1]:https://fedoraproject.org/wiki/AutoQA_resultsdb_schema  
> > 
> > That schema was correct in the past but has not been kept up to date
> > AFAIK.
> > 
> > That being said, none of the changes I can think of would cause a
> > problem in making the database dump public.  
> 
> If you all are ok with it, I can make these public after the freeze is
> over.

Sounds good to me. Thanks for getting that taken care of.

Tim


pgpV5KsZbwjQl.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-10-02 Fedora QA Devel Meeting Minutes

[Tim Flink]

=
#fedora-meeting-1: fedoraqa-devel
=


Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-02/fedoraqa-devel.2017-10-02-14.02.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-02/fedoraqa-devel.2017-10-02-14.02.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-02/fedoraqa-devel.2017-10-02-14.02.log.html

Meeting summary
---
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1496476   (kparal,
  14:04:40)
* deploying ansiblize  (tflink, 14:26:05)

* open floor  (tflink, 14:56:04)

Meeting ended at 14:58:10 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* tflink (69)
* kparal (65)
* lbrabec (4)
* zodbot (3)
* puiterwijk (1)
* Southern_Gentlem (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


pgpPTBfUdncSc.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-10-02 @ 14:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

# Fedora QA Devel Meeting
# Date: 2017-10-02
# 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/20171002-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
--

  - deployment of ansiblize branches

Open Floor
--
  - TBD


pgpVEzmvoBEJ6.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: Making ResultsDB dumps public?

[Tim Flink]

On Mon, 25 Sep 2017 05:37:03 -0400
Harold Dost  wrote:

> Assuming that the schema [1] is correct, there should be no personal
> or secret information. Though it would be good to validate that there
> aren't any unexpected tables.
> 
> [1]:https://fedoraproject.org/wiki/AutoQA_resultsdb_schema

That schema was correct in the past but has not been kept up to date
AFAIK.

That being said, none of the changes I can think of would cause a
problem in making the database dump public.

Tim

___
> 
> Harold Dost | @hdost
> 
> 
> 
> 
> On Sep 25, 2017 01:30, "Dan Callaghan"  wrote:
> 
> Is there any objection to making the ResultsDB database dumps public
> under https://infrastructure.fedoraproject.org/infra/db-dumps/ ?
> 
> I wanted to grab a database dump today, to populate a local database
> for development purposes. I was able to scp it from db-qa02 since I'm
> in sysadmin-qa, but I figured it would be nice to have it available
> publicly alongside those other applications' db dumps.
> 
> I can't think of any reason why the ResultsDB dumps need to be kept
> secret. There should be no sensitive data in them, right?
> 
> So if there are no objections I'll file an infra ticket for adding the
> dumps into the public-db-copy script.
> 
> --
> Dan Callaghan 
> Senior Software Engineer, Products & Technologies Operations
> Red Hat
> 
> ___
> qa-devel mailing list -- qa-devel@lists.fedoraproject.org
> To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org



pgp0RrsAS3Wtm.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-09-18 Fedora QA Devel Meeting Minutes

[Tim Flink]

=
#fedora-meeting-1: fedora-qadevel
=

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-09-18/fedora-qadevel.2017-09-18-14.01.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-09-18/fedora-qadevel.2017-09-18-14.01.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-09-18/fedora-qadevel.2017-09-18-14.01.log.html



Meeting summary
---
* Roll Call  (tflink, 14:01:29)
  * LINK:

https://pics.me.me/this-is-my-favourite-guitar-i-call-it-old-smokey-10620789.png
(jskladan1, 14:03:15)

* Announcements and Information  (tflink, 14:04:10)
  * rpmlint errors in debugsource rpms fixed  (kparal, 14:04:33)
  * LINK: https://pagure.io/taskotron/task-rpmlint/issue/14   (kparal,
14:04:35)
  * ansiblized libtaskotron documentation added (in a basic form) into
readme  (kparal, 14:05:14)
  * LINK:
https://pagure.io/taskotron/libtaskotron/branch/feature/ansiblize
(kparal, 14:05:17)
  * ansiblized libtaskotron builds available  (kparal, 14:05:55)
  * LINK:
https://copr.fedorainfracloud.org/coprs/kparal/taskotron-ansiblize/
(kparal, 14:05:57)

* standard interface tests on koji/mbs builds  (tflink, 14:09:54)

* fedmsg versions for trigger  (tflink, 14:24:53)
  * LINK: https://pagure.io/taskotron/issue/235   (lbrabec, 14:26:28)
  * to fix the fedmsg memory issue, the plan is to use side-builds in
the short term if needed, upgrade the master to f26 in the medium
term and upgrade everything to f26 in the longer term  (tflink,
14:36:52)

* Tasking  (tflink, 14:38:48)

* Open Floor  (tflink, 14:43:26)

Meeting ended at 14:46:54 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* tflink (74)
* kparal (23)
* jskladan_rip (15)
* zodbot (4)
* jcline (4)
* jskladan1 (3)
* lbrabec (3)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


pgpkIxrrHtvPv.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-09-18 @ 14:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

# Fedora QA Devel Meeting
# Date: 2017-09-18
# 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/20170918-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
--

  - running standard interface tests on koji/mbs builds

Open Floor
--
  - TBD


pgpGEZqkXVtw4.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Proposal to CANCEL: 2017-09-04 QA Devel Meeting

[Tim Flink]

Monday is a holiday in the US and I will not be available to lead the
QA Devel meeting. 

If there are some topics that need discussing and someone else is
willing to lead the meeting, please reply here and the meeting can
happen.

Tim


pgpO61z9V2nLs.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Proposal to CANCEL: 2017-08-28 QA Devel Meeting

[Tim Flink]

There are more than one of us traveling to Flock on Monday and as such,
I propose that we cancel the regularly scheduled QA Devel meeting.

If there is some urgent topic to discuss, please reply to this thread
and the meeting can happen if there is someone around who is willing to
lead such meeting.

Tim


pgpCOe6RLvojO.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: Fedora's beaker instance

[Tim Flink]

On Thu, 17 Aug 2017 17:43:13 +1000
Dan Callaghan <dcall...@redhat.com> wrote:

> Sorry for my very slow reply Petr...
> 
> Excerpts from pschindl's message of 2017-08-08 17:24 +02:00:
> > Hi Dan,
> > 
> > I have few questions regarding a beaker.qa.fp.org. What is the
> > state of the project right now? I now work with DesktopQA team on
> > upstreaming their tests. And because they run their tests on
> > internal beaker so I'd like to mimic their workflow. So I'd like to
> > try to run tests on our Fedora's beaker.
> > 
> > So my questions. Does the beaker.qa.fp.org works at all? Could you
> > give me access to at least one machine? Can I help you somehow with
> > make it work? What can I do to put F26 or Rawhide trees to Beaker?
> > 
> > Thank you for your answers. Have a nice day. With regards
> > Petr Schindler (Fedora QA)  
> 
> I've cc'ed the Fedora qa-devel list. Tim Flink did a lot of work
> getting the Fedora Beaker instance set up.
 
> If you wanted to get access to use it, I'm sure we could do that. We 
> would just need to add you to this group:
> 
> https://beaker.qa.fedoraproject.org/groups/qa-beaker-users#members
> 
> As far as I know, Beaker itself is fully up and running now (we had
> some issues with Fedora authentication but they were all sorted out a
> while back). However it looks like the Dell machines attached to
> Beaker are not successfully booting into the installer right now. Tim
> might know more about what is missing/broken with them. I'm not
> entirely sure what's wrong because I don't think I have access to
> their serial console.

The biggest problem I'm hitting right now is that I can't import repos.
There's something about the setup we have inside Fedora infra that
beaker's repo importing mechanism can't handle.

I keep meaning to get around to figuring out what's wrong and fix it
but as beaker is a pretty low priority right now, I never seem to get
around to it.

> That reminds me, one thing we never did set up properly is a
> Conserver instance so that Beaker can scrape the serial console logs.
> That would certainly make it easier to see why the Dell machines
> aren't netbooting successfully.

For now, you can find me and ask me to look at the machine itself. That
doesn't scale but for now, I'm not aware of other options.

> I should try and see about writing a playbook to deploy Conserver...

I'd love to see that happen :)

Tim


pgpUV439bfKjY.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-08-21 Fedora QA Devel Meeting Minutes

[Tim Flink]

=
#fedora-meeting-1: fedora-qadevel
=


Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-08-21/fedora-qadevel.2017-08-21-14.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-08-21/fedora-qadevel.2017-08-21-14.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-08-21/fedora-qadevel.2017-08-21-14.00.log.html


Meeting summary
---
* Roll Call  (tflink, 14:00:29)

* Announcements and Information  (tflink, 14:05:54)
  * taskotron-prod upgraded to f25 - tflink, kparal, jskladan  (tflink,
14:06:03)
  * F27 Branched set up in Taskotron and upgradepath updated so that it
should no longer crash when Bodhi doesn't know Branched yet --
kparal  (tflink, 14:06:03)
  * LINK: https://pagure.io/taskotron/libtaskotron/issue/328   (tflink,
14:06:03)

* Open Floor  (tflink, 14:06:37)

Meeting ended at 14:18:02 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* tflink (40)
* jskladan (18)
* zodbot (3)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


pgpSlC0BatJWk.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: Planned Outage - Taskotron update - 2017-08-15 @16:00 UTC

[Tim Flink]

The outage took a little longer than we planned but everything is back
up and has been running smoothly.

Tim

On Tue, 15 Aug 2017 09:46:47 -0600
Tim Flink <tfl...@redhat.com> wrote:

> Apologies on not announcing this farther ahead of time, the
> announcement slipped through the cracks :(
> 
> There will be an outage starting at 2017-08-15 16: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 '2017-08-15 16:00:00 UTC'
> 
> Reason for outage:
> 
> We are upgrading the hosts which run the services required for
> Taskotron.
> 
> Affected Services:
> 
> taskotron.fedoraproject.org
> 
> Contact Information:
> 
> Please join #fedora-admin or #fedora-noc on irc.freenode.net



pgpTmzpL35_9c.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Planned Outage - Taskotron update - 2017-08-15 @16:00 UTC

[Tim Flink]

Apologies on not announcing this farther ahead of time, the
announcement slipped through the cracks :(

There will be an outage starting at 2017-08-15 16: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 '2017-08-15 16:00:00 UTC'

Reason for outage:

We are upgrading the hosts which run the services required for
Taskotron.

Affected Services:

taskotron.fedoraproject.org

Contact Information:

Please join #fedora-admin or #fedora-noc on irc.freenode.net


pgpzeIW7eWBDz.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Ansiblizing Questions

[Tim Flink]

On Wed, 9 Aug 2017 14:31:49 +0200
Lukas Brabec  wrote:

> Hey, gang!
> 
> As I read through standard interface and tried ansiblized branch of
> libtaskotron, I found things that were not exactly clear to me and I
> have some questions. My summer afternoon schedule involves feeding
> rabbits (true story!) and I keep missing people on IRC, hence this
> email.
> 
> 
> = Test output and its format =
> 
> Standard test interface specifies that [1]:
> 1) "test system must examine the exit code of the playbook. A zero
> exit code is successful test result, non-zero is failure"
> and
> 2) "test suite must treat the file test.log in the artifacts folder as
> the main readable output of the test"
> 
> ad 1) Examining the exit code is pretty straight forward. The mapping
> to outcome would be zero to PASSED and non-zero to FAILED. Currently
> we use more than these two outcomes, i.e. INFO and NEEDS_INSPECTION.
> Are we still going to use them, if so, what would be the cases? The
> playbook can fail by itself (e.g. fail like command not found, or
> permission denied), but I presume this failure would be reported to
> ExecDB not to ResultsDB. Any thoughts on this?


I think that, for now at least, we won't be using the INFO and
NEEDS_INSPECTION. The standard interface definition is what it is and
they've decided that results are binary. It's possible that could
change in the future but for now, the INFO and NEEDS_INSPECTION states
probably won't be used when reporting to resultsdb.

> ad 2) The standard interface does not specify the format of test
> output, just that the test.log must be readable. Does this mean that
> the output can be in any arbitrary format and the parsing of it would
> be left to people who care, i.e. packagers? Wouldn't be this a problem
> with if, for example, bodhi wanted to extract/parse this information
> from ResultsDB and show it on update page?

As far as I know, this was left vague on purpose so that it can change
and be specified by the the test system. In this case, we'd definitely
need to support the xunit xml format that I suspect most folks will be
using but I'm open to the idea of keeping our results yaml format alive
if it makes sense.

So long as we're explicit about which formats are supported for our
implementation of a test system and don't make silly choices, I think
we're good here.

> = Triggering generic tasks =
> 
> Standard interface is centered around dist-git style tasks and doesn't
> cover generic tasks like rpmlint or rpmdeplint. As these tasks are
> Fedora QA specific, are we going to create custom extension to
> standard interface, used only by our team, to be able to run generic
> tasks?

It'd be nice if it wasn't just us using it but the standard interface
may indeed require some tweaking to get it to cover all of the usecases
that we're interested in.

Do you have any suggestions as to how we could make non-dist-git tasks
work reasonably well without making drastic changes to what the
standard interface currently is? 

> = Reporting to ResultsDB =
> 
> Gating requirements for CI and CD contains [2]:
> "It must be possible to represent CI test results in resultsdb."
> However standard interface does not speak about resultsdb.

The standard interface arguably shouldn't care about resultsdb. It does
say "it must be possible to represent ..." and not "must report to
resultsdb".

> Does this mean, that task playbook won't contain something like
> ResultsDB module (in contrast to ResultsDB directive in formulae), as
> the task playbook should be agnostic to system in which it is run, and
> the reporting will be done by our code in runtask?

That's how I'm understanding things, yes. There may be other systems
that we'll need to interface with but let's cross that bridge if and
when we get there.

> = Output of runtask =
> 
> Libtaskotron's output is nice and readable, but output of the parts,
> handled by ansible now, is not. My knowledge of ansible is still
> limited, but as far as my experience goes, debuging ansible playbooks
> or even asnible modules is kind of PITA. Are we going to address this
> in some way, or just bite the bullet and move along?

Do you have any ideas on how to improve that? One thing that I had in
mind was to look at using ara to make the output a bit easier to digest.

https://github.com/openstack/ara


> = Params of runtask =
> 
> When I tried ansiblized branch of libtaskotron, I ran into issues such
> as unsupported params: ansible told me to run it with "-vvv" param,
> which runtask does not understand. Is there a plan on how are we going
> to forward such parameters (--ansible-opts= or just forward any params
> we don't understand)?

Personally, I think that --ansible-opts= makes sense here but I don't
have terribly strong feelings about it.

> Runtask, at the moment, maps our params to ansible-playbook params and
> those defined by standard interface. Are we going to stick with this
> or change our params to match the 

017-08-07 Fedora QA Devel Meeting Minutes

[Tim Flink]

=
#fedora-meeting-1: fedora-qadevel
=

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-08-07/fedora-qadevel.2017-08-07-14.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-08-07/fedora-qadevel.2017-08-07-14.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-08-07/fedora-qadevel.2017-08-07-14.00.log.html


Meeting summary
---
* roll call  (tflink, 14:00:36)

* Announcements and Information  (tflink, 14:04:42)
  * ci-listener is up and running in the CentOS CI Infra - tflink,
pingou  (tflink, 14:04:51)
  * Moved tickets from Phabricator to the respective repositories

https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org/thread/EEA7DJUICDMSCI4R7I54GBEKBMHDBU2X/
- jskladan, kparal  (tflink, 14:07:00)
  * Archived differentila revisions' "html snapshots" and raw diffs.
Accessible at

https://fedorapeople.org/groups/qa/phabarchive/differentials/phab.qa.fedoraproject.org/
- jskladan, kparal  (tflink, 14:07:00)

* Phabricator Migration  (tflink, 14:09:24)
  * LINK: https://phab.qa.fedoraproject.org/D1208   (jskladan, 14:12:31)
  * for now, any patches on outside projects (i.e. infra) will have to
be discussed as patches, either in tickets or on ML  (tflink,
14:17:16)
  * now that we don't have phab linting our code, we need to find a new
way to have that check run  (tflink, 14:25:15)
  * LINK: https://pagure.io/taskotron/issue/227   (kparal, 14:26:11)
  * now that we don't have phab running unittests on our code, we need
to find a new way to have that check run  (jskladan, 14:26:58)

* Tasking  (tflink, 14:48:07)

* Open Floor  (tflink, 15:00:32)

Meeting ended at 15:01:45 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)


pgpSmdFNIK2rx.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-08-07 @ 15:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

# Fedora QA Devel Meeting
# Date: 2017-08-07
# 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/20170807-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
--

  - Phabricator Migration

Open Floor
--
  - TBD


pgpG0JkwoKBzo.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-07-31 Fedora QA Devel Meeting Minutes

[Tim Flink]

=
#fedora-meeting-1: fedora-qadevel
=

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-31/fedora-qadevel.2017-07-31-14.02.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-31/fedora-qadevel.2017-07-31-14.02.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-31/fedora-qadevel.2017-07-31-14.02.log.html


Meeting summary
---
* roll call  (tflink, 14:02:37)

* Announcements and Information  (tflink, 14:04:12)
  * started working on Phab to Pagure migration - Diffs and Tickets now
can be exported to html/json 'snapshots' - jskladan  (jskladan,
14:06:12)

* phabricator migration  (tflink, 14:10:06)
  * LINK: https://secure.phabricator.com/T4571   (jskladan, 14:20:22)
  * ACTION: tflink to look into a read-only mode for phabricator
(tflink, 14:23:48)

* libtaskotron's ansiblize branch  (tflink, 14:32:49)
  * taskotron-stg upgrade to f25 will happen this thursday  (tflink,
15:04:05)
  * taskotron-prod upgrade to f25 will happen next monday  (tflink,
15:04:15)
  * changeover of dev or stg to ansiblize will be soon, date TBD
(tflink, 15:04:39)

* Open Floor  (tflink, 15:07:18)
  * LINK:

http://kittenrescue.org/wp-content/uploads/2017/03/KittenRescue_KittenCareHandbook.jpg
(jskladan, 15:07:45)
  * LINK:

http://www.warrenphotographic.co.uk/photography/bigs/03003-Ginger-cat-with-grey-foster-kittens-white-background.jpg
(jskladan, 15:08:05)

Meeting ended at 15:09:22 UTC.




Action Items

* tflink to look into a read-only mode for phabricator




Action Items, by person
---
* tflink
  * tflink to look into a read-only mode for phabricator
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* tflink (111)
* kparal (56)
* jskladan (53)
* roshi (10)
* lbrabec (7)
* zodbot (5)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


pgpci2z4BrK03.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-07-17 Fedora QA Devel Meeting Minutes

[Tim Flink]

=
#fedora-meeting-1: fedora-qadevel
=

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-17/fedora-qadevel.2017-07-17-14.01.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-17/fedora-qadevel.2017-07-17-14.01.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-17/fedora-qadevel.2017-07-17-14.01.log.html

Meeting summary
---
* roll call  (tflink, 14:01:16)

* Announcements and Information  (tflink, 14:03:41)
  * depcheck has been removed from production -- kparal and mkrizek
(tflink, 14:03:55)
  * libtaskotron 0.4.24 built and submitted as updated (still in
testing) -- kparal  (tflink, 14:03:55)
  * task-mtf now has a pretty html overview page -- kparal and jscotka
(tflink, 14:03:55)
  * taskotron stack now works with Jenkins in place of Buildbot --
jskladan (+jsedlak)  (tflink, 14:03:55)
  * mkrizek has left Fedora QA  (kparal, 14:04:14)

* taskotron + Jenkins  (tflink, 14:08:06)

* Fedora Atomic Host CI and ResultsDB  (tflink, 14:27:51)

* Tasking  (tflink, 14:32:12)

* Open Floor  (tflink, 14:39:50)

Meeting ended at 14:42:13 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* tflink (88)
* jskladan (51)
* kparal (30)
* puiterwijk (9)
* roshi (4)
* zodbot (4)
* tenk (2)
* garretraziel (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


pgpDik3PsUDSt.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-07-17 @ 15:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

# Fedora QA Devel Meeting
# Date: 2017-07-17
# 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/20170717-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
--

  - Standard Interface Compat
  - Project Storage
  - Documentation/Examples

Open Floor
--
  - TBD


pgpIzD5yxJxN1.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-06-26 Fedora QA Devel Meeting Minutes

[Tim Flink]

=
#fedora-meeting-1: fedora-qadevel
=

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-06-26/fedora-qadevel.2017-06-26-14.01.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-06-26/fedora-qadevel.2017-06-26-14.01.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-06-26/fedora-qadevel.2017-06-26-14.01.log.html


Meeting summary
---
* Roll Call  (tflink, 14:01:34)

* Announcements and Information  (tflink, 14:03:48)
  * the switch from depcheck to rpmdeplint has been announced. if no
issues, I'll obsolete depcheck repo and projects in a week or so
(kparal, 14:04:46)
  * task-modularity-testing-framework will get a new "modulelint"
subtask this week  (kparal, 14:07:33)

* Standard Interface Compatibility  (tflink, 14:08:24)
  * we've decided to start splitting libtaskotron into 3 as we shift
over to the new standard interface  (tflink, 14:19:16)
  * ACTION: tflink to finish porting directives to ansible modules
(tflink, 14:21:15)
  * ACTION: jskladan and kparal to switch taskotron-stg back to
listening to prod fedmsgs  (tflink, 14:42:22)

* Project Storage  (tflink, 14:43:47)
  * kparal is the dedicated pagure hacker, all RFE's are to be
implemented by him in a timely manner  (jskladan, 14:48:18)

* Documentation/Examples  (tflink, 14:54:44)

* Open Floor  (tflink, 14:56:16)
  * LINK:

https://www.facebook.com/9gag/videos/10155767949826840/?autoplay_reason=gatekeeper_container_type=0_creator_product_type=2_id=2392950137_video_guests=0
(jskladan, 14:57:52)

Meeting ended at 14:59:41 UTC.




Action Items

* tflink to finish porting directives to ansible modules
* jskladan and kparal to switch taskotron-stg back to listening to prod
  fedmsgs




Action Items, by person
---
* jskladan
  * jskladan and kparal to switch taskotron-stg back to listening to
prod fedmsgs
* kparal
  * jskladan and kparal to switch taskotron-stg back to listening to
prod fedmsgs
* tflink
  * tflink to finish porting directives to ansible modules
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* tflink (131)
* kparal (58)
* jskladan (47)
* roshi (24)
* zodbot (9)
* mkrizek (3)
* lbrabec (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


pgprl5btK2RzB.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Proposal to CANCEL: 2017-06-19 QA Devel Meeting

[Tim Flink]

There's some RH stuff going on at the usual time and I'm not aware of
any terribly urgent topics for discussion. As such, I propose that we
cancel the QA Devel meeting today.

If you have a topic that you feel should be discussed, please respond
to this thread.

Tim


pgpCWRVFSkdl7.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Proposal to CANCEL: 2017-05-29 QA Devel Meeting

[Tim Flink]

Monday is a US holiday and I won't be around to lead a QA devel
meeting. If someone else wants to lead the meeting, I'm certainly not
going to stop them :)

As such, I propose that we cancel the QA devel meeting on May 29. If you
have a topic that you think needs to be urgently discussed, reply to
this thread.

Tim


pgpYGmUT3_zf3.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: 2017-05-15 @ 15:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

=
#fedora-meeting-1: fedora-qadevel
=


Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-05-15/fedora-qadevel.2017-05-15-14.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-05-15/fedora-qadevel.2017-05-15-14.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-05-15/fedora-qadevel.2017-05-15-14.00.log.html


Meeting summary
---
* roll call  (tflink, 14:00:16)

* Announcements and Information  (tflink, 14:03:46)
  * libtaskotron documentation improvements -- kparal  (tflink,
14:04:00)
  * libtaskotron support for ansible task to be posted for
review/discussion early this week - mkrizek  (mkrizek, 14:04:37)
  * roshi working on getting ansible tasks running against docker
containers  (roshi, 14:06:03)

* F27  (tflink, 14:09:04)

* working with CI folks  (tflink, 14:14:17)

* Future Taskotron Architecture  (tflink, 14:24:34)

* Ansible, Test Invocation and Splitting libtaskotron  (tflink,
  14:39:32)
  * LINK: https://fedoraproject.org/wiki/Changes/InvokingTestsAnsible
(tflink, 14:40:14)

* Open Floor  (tflink, 14:50:57)
  * LINK:
https://fedoraproject.org/wiki/User:Roshi/QA/Taskotron_Overview
(roshi, 14:58:39)

Meeting ended at 15:00:28 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* tflink (134)
* roshi (19)
* jskladan (18)
* kparal (16)
* mkrizek (7)
* zodbot (4)
* garretraziel (2)
* lbrabec (1)



pgpNDIf61oTs9.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-05-22 Fedora QA Devel Meeting Minutes

[Tim Flink]

=
#fedora-meeting-1: fedora-qadevel
=

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-05-22/fedora-qadevel.2017-05-22-14.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-05-22/fedora-qadevel.2017-05-22-14.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-05-22/fedora-qadevel.2017-05-22-14.00.log.html


Meeting summary
---
* roll call  (tflink, 14:00:54)

* Announcements and Information  (tflink, 14:07:18)
  * libtaskotron docs have a new theme, and some parts were updated (not
deployed yet in production) -- kparal  (tflink, 14:07:25)
  * D1195 updated to run "ansible -c local" on a minion :( - mkrizek
(mkrizek, 14:07:43)

* Tasking  (tflink, 14:16:00)

* Test Invocation Status  (tflink, 14:19:28)
  * D1195 is still in progress, will support the new ansible-based
standard interface when merged  (tflink, 14:20:10)
  * porting existing tasks to new ansible format has yet to start, will
hopefully not take long  (tflink, 14:20:52)
  * process of porting libtaskotron directives to ansible modules is
ongoing, some discussion required  (tflink, 14:23:37)
  * LINK: https://pagure.io/ansible-fedoraqa-modules   (tflink,
14:23:40)

* Testcloud and ppc  (tflink, 14:34:59)

* Open Floor  (tflink, 14:40:57)

Meeting ended at 14:42:13 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* tflink (74)
* kparal (23)
* roshi (18)
* mkrizek (10)
* zodbot (4)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


pgponz2m1oDUr.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-05-22 @ 15:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

# Fedora QA Devel Meeting
# Date: 2017-05-22
# 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/20170522-fedoraqadevel/

If you have any additional topics, please reply to this thread or add
them in the wiki doc. I don't expect this meeting to take a full hour

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 status

Open Floor
--
  - TBD


pgpJsfWCQi45T.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-05-15 @ 15:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

# Fedora QA Devel Meeting
# Date: 2017-05-15
# 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/20170515-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
  - Plans around F27 Timeline
  - Splitting up libtaskotron into python lib, ansible modules and
runner

Open Floor
--
  - TBD


pgpsCwxWqFAm3.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: sysadmin-qa group for deploying waiverdb

[Tim Flink]

On Tue, 9 May 2017 15:25:31 +0200
Kamil Paral  wrote:



> >
> > Also, would someone be willing to sponsor Matt (FAS username mjia)
> > into sysadmin-qa? Matt and I sit together here in the office so I
> > am always available to help out too.
> >  
> 
> I don't really know the infra processes, so the right person to ping
> here would be tflink from our team (he's in Raleigh this week on an
> Infra FAD), or kevin or puiterwijk from Infra team.

They're actually in the same room :-P

I've added and sponsored mjia to sysadmin-qa.

Dan, I assume that you'll be helping him figure out the bastion hosts
etc.?

Tim


pgp8AWM7dOB6M.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Proposal to CANCEL: 2017-05-08 QA Devel Meeting

[Tim Flink]

It's a holiday in the Czech Republic again on Monday and I'm not going
to be available to lead any meeting either.

As such, I propose that we cancel the QA devel meeting on May 8. If you
have a topic that you think needs to be urgently discussed, reply to
this thread.

Tim


pgpzxJpS8TLUf.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Proposal to CANCEL: 2017-05-01 QA Devel Meeting

[Tim Flink]

It's a holiday in at least the Czech Republic and India so I expect
that any meeting would be very sparsely attended.

As such, I propose that we cancel the QA devel meeting on May 1. If you
have a topic that you think needs to be urgently discussed, reply to
this thread.

Tim


pgpdz7LbN0fH5.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Planned Outage: Taskotron Production - 2017-04-25 @ 19:00

[Tim Flink]

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



pgplp9fwWdptt.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-de...@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-04-24 Fedora QA Devel Meeting Minutes

[Tim Flink]

=
#fedora-meeting-1: fedora-qadevel
=


Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-04-24/fedora-qadevel.2017-04-24-14.03.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-04-24/fedora-qadevel.2017-04-24-14.03.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-04-24/fedora-qadevel.2017-04-24-14.03.log.html


Meeting summary
---
* roll call  (tflink, 14:03:02)

* Announcements and Information  (tflink, 14:05:16)
  * i386 repo issues should be fixed now (related to i386 being an
alternate arch since F26) -- kparal  (tflink, 14:05:22)
  * LINK: https://phab.qa.fedoraproject.org/T876   (tflink, 14:05:22)
  * task-modularity-testing-framework should be now working fine on dev
-- kparal, tflink, mkrizek, puiterwijk  (tflink, 14:05:22)

* Test Invocation  (tflink, 14:09:32)
  * LINK: https://fedoraproject.org/wiki/Changes/InvokingTestsAnsible
(tflink, 14:10:35)
  * LINK: https://phab.qa.fedoraproject.org/T939   (tflink, 14:10:42)
  * ACTION: tflink to follow up with ci folks on why localhost-only is a
requirement for ansible-based tests  (tflink, 14:23:03)
  * LINK: https://en.wikipedia.org/wiki/SOAP   (tflink, 14:27:07)

* ResultsDB performance/usage  (tflink, 14:41:36)

* Open Floor  (tflink, 14:47:52)

Meeting ended at 14:51:49 UTC.




Action Items

* tflink to follow up with ci folks on why localhost-only is a
  requirement for ansible-based tests




Action Items, by person
---
* tflink
  * tflink to follow up with ci folks on why localhost-only is a
requirement for ansible-based tests
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* tflink (92)
* mkrizek (24)
* roshi (23)
* zodbot (4)
* garretraziel (1)
* lbrabec (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


pgpmxdR2NhXMJ.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-04-24 @ 15:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

# 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


pgpVtYqHkHmVD.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: Re-Scheduling Jobs for Taskotron as a User

[Tim Flink]

On Tue, 18 Apr 2017 14:53:07 +0200
Kamil Paral <kpa...@redhat.com> wrote:

> On Tue, Apr 18, 2017 at 2:35 PM, Tim Flink <tfl...@redhat.com> wrote:
> 
> > 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:
> >  
> 
> Execdb web is not searchable, people will never find their job. It
> makes a lot of sense to have the button in execdb, because that's
> where we want to show people crashed jobs (those will not appear
> neither in resultsdb nor in Bodhi). So thumbs up to that idea. But
> the search seems to be a prerequisite to this. Or we need to make
> sure crashed jobs are sent out with direct links to execdb to the
> relevant maintainers, if that turns out to be easier.

Yeah, it's not an ideal solution but in my mind, it's better than
asking folks to rebuild just to get the task re-run.

> >   1. authenticated user clicks on "reschedule" button
> >  
> 
> Authentication itself sounds like a non-trivial issue. I wonder if we
> can avoid it at least temporarily. Maybe allow anyone to click the
> button, but limit the number of times it can be pressed (e.g. max 5
> times)? Also introduce a timeout after the press (max once per hour
> since the last re-run), and don't allow to re-run old jobs (e.g.
> older than 24 hours)?
> 
> Maybe authentication will be easier after all :) Maybe we don't even
> need to check package permissions in the beginning, just making sure
> the person has a valid FAS (cla+1) account.

I was hoping that we'd be able to auth against ipsilon without much
added effort. Ideally we'd restrict things to someone with ACLs to the
involved package but that's far from required.

cla+1 should be good enough for now, I think. Limiting it to
packagers could also be reasonable but I'm not sure it's going to be a
big deal so long as we can keep track of who's doing the reschedules
through at least a log file.

Tim

> 
> >   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
> >
> > ___
> > qa-devel mailing list -- qa-devel@lists.fedoraproject.org
> > To unsubscribe send an email to
> > qa-devel-le...@lists.fedoraproject.org
> >
> >  



pgpQbLfl5KjHY.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re-Scheduling Jobs for Taskotron as a User

[Tim Flink]

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


pgpaqRUCMC5uL.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: 2017-04-10 @ 15:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

=
#fedora-meeting-1: fedora-qadevel
=

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-04-10/fedora-qadevel.2017-04-10-14.01.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-04-10/fedora-qadevel.2017-04-10-14.01.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-04-10/fedora-qadevel.2017-04-10-14.01.log.html


Meeting summary
---
* roll call  (tflink, 14:02:00)

* Announcements and Information  (tflink, 14:05:45)
  * modularity patches merged and released - mkrizek  (tflink, 14:05:56)

* Deployment of new features  (tflink, 14:08:43)

* Resultsdb Performance  (tflink, 14:21:52)

* Dist-Git Task Storage  (tflink, 14:28:19)

* CI  (tflink, 14:31:03)
  * LINK:
https://lists.fedoraproject.org/archives/list/c...@lists.fedoraproject.org/
(tflink, 14:32:44)

* Tasking  (tflink, 14:38:55)

* Open Floor  (tflink, 14:42:13)

Meeting ended at 14:44:02 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* tflink (82)
* kparal (29)
* roshi (24)
* zodbot (5)
* mkrizek (2)
* garretraziel (1)
* x3mboy (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


pgpPc8puVwqhF.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-04-10 @ 15:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

# 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


pgpTJTxQvtaEp.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Proposal to CANCEL: 2017-03-27 QA Devel Meeting

[Tim Flink]

I have a conflict during the normal QA Devel meeting this week so
unless someone else wants to lead the meeting, I propose that we cancel
it.

Tim


pgpAr5zGFbbQD.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-03-20 Fedora QA Devel Meeting Minutes

[Tim Flink]

Apologies for not announcing the meeting again. The minutes and logs
from what were discussed are as follow:

=
#fedora-meeting-1: fedora-qadevel
=

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-03-20/fedora-qadevel.2017-03-20-14.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-03-20/fedora-qadevel.2017-03-20-14.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-03-20/fedora-qadevel.2017-03-20-14.00.log.html



Meeting summary
---
* Roll Call  (tflink, 14:02:27)

* Announcements and Information  (tflink, 14:03:25)
  * Dist-Git Task Storage Deployed to and Enabled in Production- tflink
(tflink, 14:03:56)
  * Still investigating issues with nested virt for Cloud/Atomic compose
tests - roshi  (roshi, 14:04:33)
  * base-images are building again  (kparal, 14:04:50)
  * bot indexing disabled for resultsdb  (kparal, 14:05:12)
  * taskotron landing page now has a fancy instance switcher -- lbrabec
(kparal, 14:05:40)

* Dist-Git Task Storage  (tflink, 14:08:17)
  * draft Taskotron Overview documentation on wiki:
https://fedoraproject.org/wiki/User:Roshi/QA/Taskotron_Overview -
roshi  (roshi, 14:10:10)
  * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=870047
(tflink, 14:12:30)

* ResultsDB Performance  (tflink, 14:18:39)

* Moar Ansible?  (tflink, 14:30:37)
  * LINK: https://review.openstack.org/#/c/442180/   (tflink, 14:33:11)
  * LINK: https://review.openstack.org/#/c/438281/   (tflink, 14:33:31)

* Tasking  (tflink, 14:39:41)

* Open Floor  (tflink, 14:41:43)

Meeting ended at 14:48:07 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* tflink (79)
* kparal (33)
* jskladan (11)
* zodbot (9)
* roshi (8)
* mkrizek (4)
* lbrabec (1)
* robyduck (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


pgpdRcJGETboJ.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-03-13 Fedora QA Devel Meeting Minutes

[Tim Flink]

=
#fedora-meeting-1: fedora-qadevel
=


Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-03-13/fedora-qadevel.2017-03-13-14.00.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-03-13/fedora-qadevel.2017-03-13-14.00.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-03-13/fedora-qadevel.2017-03-13-14.00.log.html


Meeting summary
---
* roll call  (tflink, 14:01:03)

* Announcements and Information  (tflink, 14:03:45)
  * taskotron-dev works again - mkrizek  (mkrizek, 14:04:33)
  * deployment of atomic/cloud checks is in progress - mkrizek, roshi
(mkrizek, 14:05:07)
  * we have nested virt on dev \o/  (mkrizek, 14:05:52)
  * working on overview documentation for how data flows through
taskotron - roshi  (roshi, 14:06:47)
  * phab updated to a version with working search  (tflink, 14:08:47)

* Deploying New Features  (tflink, 14:09:33)

* Documentation, Guides and Examples  (tflink, 14:18:11)

* Phabricator  (tflink, 14:31:25)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1418940   (tflink,
14:33:22)
  * ACTION: tflink to move the conversation around phab and pagure to
qadevel@  (tflink, 14:54:06)

* open floor  (tflink, 14:54:10)

Meeting ended at 14:55:49 UTC.




Action Items

* tflink to move the conversation around phab and pagure to qadevel@




Action Items, by person
---
* tflink
  * tflink to move the conversation around phab and pagure to qadevel@
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* tflink (95)
* roshi (43)
* kparal (30)
* mkrizek (18)
* jskladan (5)
* zodbot (5)
* tenk (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


pgpZMucFZk7cy.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: Cancel/Reschedule 2017-03-06 Fedora QA Devel Meeting

[Tim Flink]

On Mon, 6 Mar 2017 08:54:20 -0500 (EST)
Kamil Paral  wrote:

> > I can't make the QA Devel meeting this week so unless someone else
> > wants to lead the meeting, we'll need to cancel or reschedule it.
> > 
> > 12:00 or 13:00 UTC should work for me Tuesday-Thursday if that works
> > for other folks.
> > 
> > Thoughts? Votes? Volunteers?  
> 
> Hi, unless there's something urgent to discuss (shout anyone), I
> think we can easily skip one meeting and follow-up next week. I
> removed the meeting from fedocal.


OK, works for me. When I asked in #fedora-qa last week, there seemed to
be some interest in rescheduling.

I'm not aware of anything urgent that would require a meeting, anyways.

Tim


pgplujRBYQJYR.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Cancel/Reschedule 2017-03-06 Fedora QA Devel Meeting

[Tim Flink]

I can't make the QA Devel meeting this week so unless someone else
wants to lead the meeting, we'll need to cancel or reschedule it.

12:00 or 13:00 UTC should work for me Tuesday-Thursday if that works
for other folks.

Thoughts? Votes? Volunteers?

Tim


pgpMOJP45QNqP.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-02-27 @ 15:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

# Fedora QA Devel Meeting
# Date: 2017-02-20
# Time: 15:00 UTC (note time change)
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net


https://phab.qa.fedoraproject.org/w/meetings/20170227-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
  - Dist-Git Task Storage
  - making taskotron images public

Open Floor
--
  - TBD


pgp74vKBVWq28.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: Trigger changes - call for comments

[Tim Flink]

On Thu, 16 Feb 2017 11:33:02 +0100
Josef Skladanka  wrote:

> Hey, gang!
> 
> As with the ExecDB, I took some time to try and formalize what I
> think is to be done with Trigger in the near-ish future.
> Since it came to my attention, that the internal G-Docs can not be
> accessed outside of RH, this time, it is shared from my personal
> account - hopefully more people will be enabled to read and comment
> on the document. Without further ado -
> https://docs.google.com/document/d/1BEWdgm0jO4p5DsTO4vntwUumgLZGtU5lBaBX5av7MGQ/edit?usp=sharing

Looks good to me overall. I agree that we may have some
misunderstandings around what "rerun" implies WRT environment
reproduction but I also agree that it's something that we can deal with
later.

Tim
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-02-20 Fedora QA Devel Meeting Minutes

[Tim Flink]

=
#fedora-meeting-1: fedora-qadevel
=


Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-02-20/fedora-qadevel.2017-02-20-15.02.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-02-20/fedora-qadevel.2017-02-20-15.02.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-02-20/fedora-qadevel.2017-02-20-15.02.log.html


Meeting summary
---
* Roll Call  (tflink, 15:02:23)

* Announcements and Information  (tflink, 15:05:42)
  * allow for Jenkins to be used in the Taskotron stack WIP - mkrizek
(tflink, 15:05:52)
  * LINK: https://phab.qa.fedoraproject.org/T908   (tflink, 15:05:52)
  * depcheck crashes have been resolved - kparal  (tflink, 15:05:52)
  * LINK: https://phab.qa.fedoraproject.org/T906   (tflink, 15:05:52)
  * testcloud race condition leaving a lot of zombie VMs should be
resolved - kparal  (tflink, 15:05:52)
  * LINK: https://phab.qa.fedoraproject.org/T905   (tflink, 15:05:53)
  * new resultsdb* pushed stable, should be updated on prod soon -
kparal  (tflink, 15:05:54)
  * LINK: https://phab.qa.fedoraproject.org/T877   (tflink, 15:05:56)
  * LINK: https://phab.qa.fedoraproject.org/T890   (tflink, 15:05:58)
  * tunirtests have been ported to ansible  (roshi, 15:07:15)
  * LINK: https://pagure.io/fedora-qa/cloud-atomic-ansible-tests
(roshi, 15:07:19)
  * testcloud 0.1.11 has been released and pushed to updates-testing
(tflink, 15:07:39)

* Trigger and ExecDB changes  (tflink, 15:19:27)
  * LINK: https://phab.qa.fedoraproject.org/w/taskotron/execdb_rewrite/
(jskladan, 15:20:57)
  * LINK:

https://docs.google.com/document/d/1BEWdgm0jO4p5DsTO4vntwUumgLZGtU5lBaBX5av7MGQ/edit?usp=sharing
(jskladan, 15:21:05)
  * ACTION: jskladan to do the execdb rewrite this week (don't forget to
create at least high-level tickets to track progress)  (jskladan,
15:25:33)

* Meta CI for libtaskotron  (tflink, 15:27:23)
  * LINK: https://pagure.io/taskotron/task-taskotron-ci   (tflink,
15:27:47)
  * we do need more tests in the CI task, the example tasks may be a
good place to start  (tflink, 15:35:16)

* Documentation  (tflink, 15:37:12)
  * ACTION: kparal to take information from trigger proposal and make a
quick trigger doc out of that in pagure  (tflink, 15:48:06)

* Open Floor  (tflink, 15:48:15)

Meeting ended at 15:57:18 UTC.




Action Items

* jskladan to do the execdb rewrite this week (don't forget to create at
  least high-level tickets to track progress)
* kparal to take information from trigger proposal and make a quick
  trigger doc out of that in pagure




Action Items, by person
---
* jskladan
  * jskladan to do the execdb rewrite this week (don't forget to create
at least high-level tickets to track progress)
* kparal
  * kparal to take information from trigger proposal and make a quick
trigger doc out of that in pagure
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* tflink (90)
* jskladan (62)
* kparal (44)
* roshi (30)
* zodbot (7)
* garretraziel (3)
* mkrizek (1)
* lbrabec (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


pgpdfN0RI88UW.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-02-20 @ 15:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

# Fedora QA Devel Meeting
# Date: 2017-02-20
# Time: 15:00 UTC (note time change)
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net


https://phab.qa.fedoraproject.org/w/meetings/20170220-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
--


  - Meta CI for libtaskotron
  - Documentation
  - ExecDB and Trigger Proposals

Open Floor
--
  - TBD
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: ExecDB rewrite - call for comments

[Tim Flink]

On Mon, 13 Feb 2017 08:15:40 +0100
Josef Skladanka  wrote:

> Hey gang!
> 
> With the incoming changes, I'd like to make ExecDB a bit more worth
> its name, and make it less tied to Buildbot than it is at the moment,
> and also make some changes to what functionality it provides.
> 
> Please, comment!
> 
> Thanks, Joza
> 
> https://docs.google.com/a/redhat.com/document/d/1sOAn2WJ0-XAJu9ssckevS9-m2BM7DwyGbfUaSHx3Nq0/edit?usp=sharing

Overall, I think you've captured what's been discussed about enhancing
ExecDB.

I left a few comments but nothing major. Thanks for getting this
started.

Tim
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Proposal to CANCEL: 2017-01-30 Fedora QA Devel Meeting

[Tim Flink]

I'm not aware of anything terribly urgent to discuss this week and many
of the usual suspects are still traveling so I propose that we cancel
the QA devel meeting this week.

If you have topics that you'd like to see discussed urgently, reply to
this thread.

Tim


pgp59TBqjooRO.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Proposal to CANCEL: 2017-01-23 Fedora QA Devel Meeting

[Tim Flink]

There are a bunch of Red Hat related events this week and a majority
of the usual suspects are going to be busy with other things. I'm not
aware of any urgent topics that need to be discussed/reviewed as a group
this week, so I propose that we cancel the weekly Fedora QA devel
meeting.

If there are any topics that I'm forgetting about and/or you think
should be brought up with the group, reply to this thread and we can
un-cancel the meeting.

Tim


pgp5UadUsLmyF.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: Planned Outage: Taskotron - 2017-01-17 20:00 UTC

[Tim Flink]

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 <tfl...@redhat.com> wrote:

> 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 which requires a
> migration that will take 8-12 hours. This migration will be very
> infrequent if it ever happens and we don't anticipate needing long
> outages like this in the future
> 
> All jobs which would have run during the outage will be queued for
> execution after the outage has completed
> 
> Affected Services:
> 
> All services on taskotron.fedoraproject.org
> 
> Ticket Information: https://pagure.io/fedora-infrastructure/issue/5697
> 
> Contact Information: infrastruct...@lists.fedoraproject.org
> 
> Please join #fedora-admin in irc.freenode.net or add comments to the
> ticket for this outage above.



pgpl7eSMFhOP7.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Planned Outage: Taskotron - 2017-01-17 20:00 UTC

[Tim Flink]

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 which requires a
migration that will take 8-12 hours. This migration will be very
infrequent if it ever happens and we don't anticipate needing long
outages like this in the future

All jobs which would have run during the outage will be queued for
execution after the outage has completed

Affected Services:

All services on taskotron.fedoraproject.org

Ticket Information: https://pagure.io/fedora-infrastructure/issue/5697

Contact Information: infrastruct...@lists.fedoraproject.org

Please join #fedora-admin in irc.freenode.net or add comments to the
ticket for this outage above.


pgpFXbVbPMvtY.pgp
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Task Result Dashboards

[Tim Flink]

On Fri, 13 Jan 2017 13:58:25 +0100
Josef Skladanka <jskla...@redhat.com> wrote:

> On Thu, Jan 12, 2017 at 7:42 AM, Tim Flink <tfl...@redhat.com> wrote:
> 
> > The idea was to start with static site generation because it doesn't
> > require an application server, is easy to host and likely easier to
> > develop, at least initially.
> >
> > I don't really have a strong preference either way, just wanted to
> > say  
> that "initial development" time is the same for web app, and for
> static generated pages - it both does the same thing - takes an input
> + output template and produces output. You can't really get around
> that from what I'm seeing here. Static generated page equals cached
> data in the app, and for the starters we can go on using just the
> stupidest of caches provided in Flask (even though it might well be
> cool and interesting to use some document store later on, but that's
> premature optimization now).

Honestly, I don't care a whole lot about how the dashboards are
implemented so long as they get done and they get done relatively
quickly.


> > >After brief discussion with jskladan, I understand that
> > > resultsDB would be able to handle requests from dynamic page.  
> >
> > Sure but then someone would have to write and maintain it. The
> > things that drove me towards static site generation are:
> >  
> 
> Write and maintain what? I'm being sarcastic here, but this sounds
> like the code for static generated pages will not have to be written
> and maintained... And once again - the actual code that does the
> actual thing will be the same, regardless of whether the output is a
> web page, or a http response.

I was thinking that a static site generator would work around the need
for auth and interface code to create new dashboards. We could just
have a git repo with yaml files and if someone wanted a new dashboard,
they could just submit a PR with the new yaml file.

> >  
> > > * I'm not sure what exactly is meant by 'item tag' in the examples
> > > section.
> > >
> > > * Would the YAML configuration look something like this:
> > >
> > >url: link.to.resultsdbapi.org
> > >overview:
> > >- testplan:
> > >  - name: LAMP
> > >  - items:
> > >- mariadb
> > >- httpd
> > >  - tasks:
> > >- and:
> > >  - rpmlint
> > >  - depcheck
> > >  - or:
> > >- foo
> > >- bar  
> >
> > I was thinking more of the example yaml that's in the git repo at
> > taskdash/mockups/yamlspec.yml [1] but I'm not really tied to it
> > strongly
> > - so long as it works and the format is easy enough to understand.
> >
> >  
> I guess I know where you were going with that example, but it is a bit
> lacking. For one all it really allows for is "hard and" relationship
> between the testcases in the testplan (dashboard, call it whatever you
> like), which might be enough, but with what was said here it will
> start being insufficient pretty fast. The other thing is, that we
> really want to be able to do the "item selection" in some way. We
> sure could say "take all results for all these four testcases, and
> produce a line-per-item" but that is so broad, that it IMO stops
> making sense anywhere beyond the "global" (read applicable to all the
> items in the resutsdb) testplans.

This is meant as an initial direction, not a final resting place. I
fully expect that the functionality will continue to evolve if we adopt
the project.
> > >Is there going to be any additional grouping (for example,
> > > based on arch) or some kind of more precise outcome aggregation
> > > (only warn if part of testplan is failing, etc.)  
> >
> > Maybe but I think those features can be added later. Are you of the
> > mind that we need to take those things into account now?
> >
> >  
> I don't really think that they can. Take a simple "gating" dashboard
> for example. There is a pretty huge difference between "package
> passes, if rpmlint, depcheck and abicheck pass on it" and "package
> passses if rpmlint, depcheck and abicheck pass for all the required
> arches". And I'm certain we want to be able to do the latter. Like it
> is not really "pass" when rpmlint passed on ARM, depcheck on X86_64
> and abicheck on i386, but all the other combinations failed.

Why can't all that be hardcoded for now, at least? The required checks
and arches don't change very often.

> It might seem like unn

2017-01-16 @ 15:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

 Fedora QA Devel Meeting
# Date: 2017-01-16
# Time: 15:00 UTC (note time change)
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net

There are a few things worth discussing this week

https://phab.qa.fedoraproject.org/w/meetings/20170116-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
--


  - Dist-Git Task Storage Deployment
  - Rebuilding Taskotron Production
  - Documentation
  - Task Dashboards

Open Floor
--
  - TBD


pgpXK5cCO16n_.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: Task Result Dashboards

[Tim Flink]

On Wed, 11 Jan 2017 12:43:23 +0100
Lukas Brabec  wrote:

> Hi team,
> 
> I would like to open discussion on topic "Task Result Dashboards".
> I'm posting here in order to avoid long of the grid discussions we
> had last time regarding the docker testing stuff.
> There is a tracking ticket in phab [1] that links to tflink's initial
> ideas [2].
> 
> * What is the motivation, what do we want to achieve with such
> dashboards and who is the 'non-techincal audience'?

The motivation is to enable more complex visualizations of results. If
we're interested in the current state of all ruby packages or all
python packages it's not all that easy to see that at a glance with our
current resultsdb interfaces.

I can also see having a dashboard for all critpath packages or all
packages needed for building a livecd being a useful thing to render

> * Runnable once a day or once per hour at minimum; does this imply
> static periodically refreshed page? If so, what is the motivation for
> static website?

The idea was to start with static site generation because it doesn't
require an application server, is easy to host and likely easier to
develop, at least initially.

>After brief discussion with jskladan, I understand that resultsDB
> would be able to handle requests from dynamic page.

Sure but then someone would have to write and maintain it. The things
that drove me towards static site generation are:

 - easier to make something quickly

 - enables easier dashboard contribution; we just need the description
   of what's being visualized.

> * I'm not sure what exactly is meant by 'item tag' in the examples
> section.
> 
> * Would the YAML configuration look something like this:
> 
>url: link.to.resultsdbapi.org
>overview:
>- testplan:
>  - name: LAMP
>  - items:
>- mariadb
>- httpd
>  - tasks:
>- and:
>  - rpmlint
>  - depcheck
>  - or:
>- foo
>- bar

I was thinking more of the example yaml that's in the git repo at
taskdash/mockups/yamlspec.yml [1] but I'm not really tied to it strongly
- so long as it works and the format is easy enough to understand.

>Is there going to be any additional grouping (for example, based
> on arch) or some kind of more precise outcome aggregation (only warn
> if part of testplan is failing, etc.)

Maybe but I think those features can be added later. Are you of the
mind that we need to take those things into account now?

> * Are we going to generate the dashbord for the latest results only,
> or/and some kind of summary over given period in history?

For now, the latest results. In my mind, we'd be running the dashboard
creation on a cron job or in response to fedmsgs. At that point, we'd
date the generated dashboards and keep a record of those without
needing a lot more complexity

> * How are Task dasboards related to Static dashboards [3]

They're the same thing - a demonstration of me somehow forgetting that
there was a basic ticket when I wrote T738.

Thanks for taking this on, it'll be great to have some nicer status
displays of the kinds of checks running in Taskotron.

Tim


[1]
https://bitbucket.org/tflink/taskdash/src/67f370e62f163de94d8404331d13c404fbf1ec73/mockups/yamlspec.yml?at=master=file-view-default
> 
> [1] https://phab.qa.fedoraproject.org/T725
> [2] https://bitbucket.org/tflink/taskdash
> [3] https://phab.qa.fedoraproject.org/T738
> ___
> qa-devel mailing list -- qa-devel@lists.fedoraproject.org
> To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org



pgp9U1e5TiN7K.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: Proposal: Migrating More Git Projects to Pagure

[Tim Flink]

On Mon, 9 Jan 2017 09:21:16 -0700
Tim Flink <tfl...@redhat.com> wrote:

> This came up in the qadevel meeting today and I wanted to put a bit
> more detail out.
> 
> Bitbucket was never intended to be the long-term home for our git
> projects - I think we're about the only folks in Fedora using it and
> it's not free software. As fedorahosted is closed down, we need to
> find a new home for blockerbugs but I figure that now is as good of a
> time as any to get all of our git projects in the same place.
> 
> I'm proposing the following moves:
> 
> * Move all Taskotron projects to pagure.io using the taskotron group:
>- pagure.io/taskotron/libtaskotron
>- pagure.io/taskotron/resultsdb
>- etc.
> 
> * Move blockerbugs under the existing fedora-qa namespace in pagure:
>- pagure.io/fedora-qa/blockerbugs
> 
> I'm not sure if there are any plans for the openqa stuff that
> currently lives on bitbucket but it'd be nice to see that moved as
> well.
> 
> Any objections, comments, concerns?

To be a bit more explicit, I'm planning to do these migrations tomorrow
unless there are objections.

Tim


pgpfycwF6n0kg.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: New ExecDB

[Tim Flink]

On Fri, 21 Oct 2016 13:16:04 +0200
Josef Skladanka  wrote:

> So, after a long discussion, we arrived to this solution.
> 
> We will clearly split up the "who to notify" part, and "should we
> re-schedule" part of the proposal. The party to notify will be stored
> in the `notify` field, with `taskotron, task, unknown` options.
> Initially any crashes in `shell` or `python` directive, during
> formula parsing, and when installing the packages specified in the
> formula's environment will be sent to task maintainers, every other
> crash to taskotron maintainer. That covers what I initially wanted
> from the multiple crashed states.
> 
> On top of that, we feel that having an information on "what went
> wrong" is important, and we'd like to have as much detail as
> possible, but on the other hand we don't want the re-scheduling logic
> to be too complicated. We agreed on using a `cause` field, with
> `minion, task, network, libtaskotron, unknown` options, and storing
> any other details in a key-value store. We will likely just
> re-schedule any crashed task anyway, at the beginning, but this
> allows us to hoard some data, and make more informed decision later
> on. On top of that, the `fatal` flag can be set, to say that it is
> not necessary to reschedule, as the crash is unlikely to be fixed by
> that.
> 
> This allows us to keep the re-scheduling logic rather simple, and most
> imporantly decoupled from the parts that just report what went wrong.

How far did you end up getting on this?

Tim


pgpZnfeI5dQEn.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: Enabling running Taskotron tasks on Koji scratch builds

[Tim Flink]

On Mon, 9 Jan 2017 08:09:52 -0500 (EST)
Martin Krizek  wrote:

> Hi team,
> 
> we have received a few requests to run tasks on koji scratch builds.
> Unfortunately, it is not as straightforward as it would seem since
> "real" koji builds and scratch builds are not treated the same.
> That's why "real" builds are downloaded with "koji download-build"
> and scratch builds are downloaded with its own tool called
> "koji-download-scratch" which is part of the fedora-review package.
> 
> The way the "real" koji builds work is that they are referenced by
> NVRs since NVRs are unique (I think there can be multiple builds with
> the same NVR, many with "failed" status and just one with the
> "completed" status and only the completed ones are searched, but
> that's just my guess). In taskotron's koji tasks, we feed NVR's to
> libtaskotron's koji directive which downloads build's RPMs.
> 
> In the case of scratch builds, they are not referenced by NVR's but
> rather just with task ID's.
> 
> With that being said, we just can't write a trigger for listening for
> the scratch builds fedmsgs [1] and trigger a libtaskotron job because
> there's no NVR in the fedmsg and even if it was, we wouldn't be able
> to download the rpms.

Couldn't we use the task ID as the primary identifier but use the srpm
for readability sake since there is no "build" NVR for scratch builds?
Either that or make the primary ID a tuple of (srpm name, koji task
start time) either stored that way or rendered as a string e.g
foo-1.2-3.fc99.src.rpm built at 201701092100 (MMDDHHMM) would become
foo-1.2-3.fc99-201701092100.

> During a discussion with Kamil, a few solutions were mentioned (none
> of them is pretty):
> 
> 1. We can ask koji developers if there is a way to add a method that
> would return all koji scratch builds for a given NVR - we would then
> take the latest one and work with it.

How would we get the NVR if there's no build identifier on scratch
builds? Are you talking about the SRPM name in the fedmsg?

> 2. We can use "koji download-task" which works for both. That would
> mean koji_build item type would eat koji task IDs instead of NVRs.
> This would lead to having koji task IDs in resultsdb instead of NVR's
> which kills readability. Unless libtaskotron finds the NVR from the
> koji task ID in the case of "real" build" and stores it in a field in
> resultsdb...Also, we need NVRs for fedmsgs. So add code to the fedmsg
> layer that would take care of somehow adding a NVR to fedmsg of
> completed scratch builds tasks...

Can't we tell the difference between an NVR and a task ID just by the
form that the content takes? Wouldn't the following work:

  1. attempt to parse input as NVR, if there are no issues, assume that
 it's a build ID
  2. if the NVR parse fails, check to see if the input is an int. if
 assume that it's a koji task ID

It'd mean that our koji downloading code would get more complicated but
it seems like nothing that more unit tests couldn't mitigate. Unless
I'm mis-thinking here, the changes needed to pull this off in trigger
would be even smaller.

> 3. We can add a new action to the koji directive "download_task". And
> then have for each koji task two formulas, one for scratch build
> (using "download_task") and one for "real" build" (using
> "download_build). This would require writing code for supporting
> multiple formulas for one task and would result in having two almost
> identical formulas...

I'm not a huge fan of 3 if there is any other reasonable way to do
things. Code duplication is not the way to go.

> Before proceeding with 1. and asking koji folks if they are able to
> help with that I wanted to check here if anyone has any thoughts on
> this.

If what I wrote above would work well enough, that sounds like a good
way to go forward to me. If not, 2 sounds like a decent option.

Tim


pgpyhqQB81L01.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Proposal: Migrating More Git Projects to Pagure

[Tim Flink]

This came up in the qadevel meeting today and I wanted to put a bit
more detail out.

Bitbucket was never intended to be the long-term home for our git
projects - I think we're about the only folks in Fedora using it and
it's not free software. As fedorahosted is closed down, we need to find
a new home for blockerbugs but I figure that now is as good of a time
as any to get all of our git projects in the same place.

I'm proposing the following moves:

* Move all Taskotron projects to pagure.io using the taskotron group:
   - pagure.io/taskotron/libtaskotron
   - pagure.io/taskotron/resultsdb
   - etc.

* Move blockerbugs under the existing fedora-qa namespace in pagure:
   - pagure.io/fedora-qa/blockerbugs

I'm not sure if there are any plans for the openqa stuff that currently
lives on bitbucket but it'd be nice to see that moved as well.

Any objections, comments, concerns?

Tim



pgptiXw3EN5P2.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-01-09 Fedora QA Devel Meeting Minutes

[Tim Flink]

=
#fedora-meeting-1: fedora-qadevel
=

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-01-09/fedora-qadevel.2017-01-09-15.01.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-01-09/fedora-qadevel.2017-01-09-15.01.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-01-09/fedora-qadevel.2017-01-09-15.01.log.html


Meeting summary
---
* Roll Call  (tflink, 15:01:22)

* Announcements and Information  (tflink, 15:05:36)
  * taskotron stg rebuild to f24/f25 process started, many snags are
being hit - tflink, mkrizek  (tflink, 15:05:45)
  * new qa.fp.o instance with phabricator FINALLY deployed with working
auth - tflink  (tflink, 15:05:46)
  * roshi is back  (kparal, 15:06:03)
  * discussion started on qa-devel ML about running tasks on koji
scratch builds - mkrizek  (mkrizek, 15:07:40)

* Phabricator Maintenance  (tflink, 15:09:15)
  * LINK: https://pagure.io/phabricator-extension-ipsilonoauth/
(tflink, 15:12:59)
  * LINK: https://pagure.io/phabphourphedora   (tflink, 15:13:41)

* Rebuilding Taskotron instances  (tflink, 15:19:46)

* Documentation  (tflink, 15:25:57)

* Dist-Git Task Storage Proposal (and test case docs)  (tflink,
  15:30:17)
  * LINK:

https://phab.qa.fedoraproject.org/w/taskotron/new_distgit_task_storage_proposal/
(tflink, 15:30:31)

* git hosting  (tflink, 15:38:22)
  * AGREED: move all of our projects over to pagure so that things are
all on pagure  (tflink, 15:43:45)

* tasking  (tflink, 15:45:30)
  * LINK: https://phab.qa.fedoraproject.org/T725   (tflink, 15:46:40)

* Open Floor  (tflink, 15:51:03)

Meeting ended at 15:56:10 UTC.



pgpnsWaqjrZnY.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

2017-01-09 @ 15:00 UTC - Fedora QA Devel Meeting

[Tim Flink]

# Fedora QA Devel Meeting
# Date: 2017-01-09
# Time: 15:00 UTC (note time change)
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net

It's been a while since we last met and there are a couple of things
worth discussing.

https://phab.qa.fedoraproject.org/w/meetings/20170109-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
  - Dist-Git Task Storage Proposal (and test case docs)
  - Rebuilding Taskotron instances
  - Phabricator Maintenance
  - Projects

Open Floor
--
  - TBD


pgpBj_n9iosRq.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: 2017-01-05 @ 18:00 UTC - Outage for qadevel.cloud replacement (for real this time)

[Tim Flink]

On Thu, 5 Jan 2017 18:07:10 -0700
Tim Flink <tfl...@redhat.com> wrote:

> On Thu, 5 Jan 2017 10:42:09 -0700
> Tim Flink <tfl...@redhat.com> 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 phabricator has been successfully migrated
> to
> 
> https://phab.qa.fedoraproject.org/
> 
> Note the new hostname - you should be redirected to the new host if
> you use the old url, though.
> 
> I've changed the .arcconfig files for the taskotron-related repos. I
> think that I got the develop branch for everything but if you see one
> I missed, please fix it.

One thing that I forgot to mention - I had to mess around with the
database a bit to make the transition smooth and not require 10 steps
for everyone to be able to log in again. Part of that was assuming that
phab usernames are identical to FAS usernames.

If your phab username does not match your FAS username, let me know. I
can fix that but until I do fix it, you won't be able to log in.

Tim


pgpPTF4TKKMGq.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: 2017-01-05 @ 18:00 UTC - Outage for qadevel.cloud replacement (for real this time)

[Tim Flink]

On Thu, 5 Jan 2017 10:42:09 -0700
Tim Flink <tfl...@redhat.com> 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 phabricator has been successfully migrated to

https://phab.qa.fedoraproject.org/

Note the new hostname - you should be redirected to the new host if you
use the old url, though.

I've changed the .arcconfig files for the taskotron-related repos. I
think that I got the develop branch for everything but if you see one I
missed, please fix it.

Tim


pgprFodxJU22k.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org