Proposal to Cancel - 2016-08-01 Fedora QA Devel Meeting
by Tim Flink
Seeing as many of the usual folks will be either traveling to or at
Flock during the normal meeting time, I don't think that scheduling the
regular QA Devel meeting would be incredibly productive.
If there are other opinions, please start/have that conversation here.
Tim
7 years, 4 months
Request for Testing: New Auth Method for Phabricator
by Tim Flink
I've been working on moving our phabricator instance off of persona
before that system is turned off in a few months.
I have an extension deployed in staging and I'd like it to see a bit
more testing before looking into deploying it in production.
https://phab.qa.stg.fedoraproject.org/
To link your existing account (on staging, this won't work on the
production instance yet) to the new auth method:
1. Click on the "user" button next to the search bar when logged in
2. Click on "manage" on the left hand side of the screen
3. Click on "edit settings" on the right hand side of the screen
4. Click on "External Accounts"
5. Click on "Ipsilon" under "Add External Account
6. Log in with your FAS credentials.
Please let me know if you try this and are successful or if you run
into problems. I haven't been able to reproduce the 500 issue with
persona on stg but I suspect it's intermittant and will try again later
to see if I can fix it enough to be somewhat reliable.
Tim
7 years, 4 months
Python Version Check for Taskotron
by Miro Hrončok
Hi.
I've prepared a check that makes sure packages do not require both
Pythons (2 & 3), except explicitly listed packages. It is a common
mistake when porting stuff to Python 3, that shebangs leave the
dependency on Python 2 as well etc.
The review is here: https://phab.qadevel.cloud.fedoraproject.org/D948
I'm doing this for the first time, to please be patient with me.
Thanks,
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
7 years, 4 months
rpmgrill in taskotron
by Kamil Paral
Hey Ralph (ccing qa-devel),
just to let you know, I added some code to Koji directive to download build logs. The patch is posted here:
https://phab.qadevel.cloud.fedoraproject.org/D916
(you can use 'arch patch D916' to apply the diff in your libtaskotron checkout)
The corresponding changes for task-rpmgrill are in feature/buildlog branch:
https://bitbucket.org/fedoraqa/task-rpmgrill/branch/feature/buildlog
I could have implemented shuffling the build.log files around in run_rpmgrill.py, but it seemed easier to have it in a bash script. I moved all the rpmgrill* commands in there as well, and used our new bash directive to execute it (it still has rough edges, we're working on that). But having it in a bash script is not necessary, if you prefer to do it all in python, we definitely don't have to merge the code as it is :)
I also removed your failsafe decorator, but again, it's just a suggestion. The first reason was that since I moved most of the setup code and rpmgrill execution into the bash directive, the decorator didn't have any affect on it anyway. The second reason is that we seem to be of an opinion that ResultsDB should only contain real results (passed, failed), and crashes and similar execution statuses should be only present in ExecDB [1] (which, however, cannot be searched yet). This is all up to discussion, and our current solutions have a lot of rough edges, so if you want to continue sending CRASHED to ResultsDB in case of errors, we have no problem with it, and we can convert task-rpmgrill once we're 100% sure how we want things to look like and have it implemented properly. Please note, though, that we currently receive emails for all tests that crash hard, so we will be able to spot any task-rpmgrill issues even if not wrapped in the failsafe decorator.
If you have any questions or concerns, please ask :)
Cheers,
Kamil
[1] https://taskotron.fedoraproject.org/execdb/
7 years, 5 months
Proposal to CANCEL: 2016-07-04 Fedora QA Devel Meeting
by Tim Flink
Monday is a holiday in the US so I won't be around to lead the QA devel
meeting this week and as far as I know, several of the usual suspects
are also not going to be able to make the meeting this week.
I'm proposing that we cancel the QA devel meeting this week. If there is
a desire to meet and someone else is willing to lead, feel free to do so.
Tim
7 years, 5 months
