Re: New automated test coverage: openQA tests of critical path updates

2017-03-01 18:04 GMT+01:00 Adam Williamson : > I'm not so sure it's really necessary, and doing it is actually tricky > for openQA. Only the openQA job itself knows what packages it actually > tested, and it doesn't have an easy way to get the associated > timestamp.

Re: New ExecDB

Proposal looks good to me, I don't have any strong objections. 1. If you don't like blame: UNIVERSE, why not use blame: TESTBENCH? 2. I think that having enum values in details in crash structure would be better, but I don't have strong opinion either way. Jan

Re: 2016-09-14 @ 14:00 UTC - QA Tools Video "Standup" Meeting

Sorry, but I need to go to the bank, so I won't attend. Jan ___ qa-devel mailing list qa-devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/qa-devel@lists.fedoraproject.org

Re: 2016-05-23 @ 14:00 UTC - Fedora QA Devel Meeting

Sorry, I have some errands today and I cannot attend. 2016-05-23 6:51 GMT+02:00 Tim Flink : > # Fedora QA Devel Meeting > # Date: 2016-05-23 > # Time: 14:00 UTC > (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) > # Location: #fedora-meeting-1 on irc.freenode.net > >

Re: openQA git master bump and new workers

> We could also look at going to single-CPU VMs; this is how SUSE runs, > apparently. We ought to be able to up the worker count considerably if > we do that. > I thought that Anaconda would be unusably slow with single-core CPU. ___ qa-devel mailing

Re: 2016-02-22 @ 15:00 UTC - Fedora QA Devel Meeting

I too won't be able to attend. 2016-02-22 10:52 GMT+01:00 Kamil Paral : > > # Fedora QA Devel Meeting > > # Date: 2016-02-22 > > # Time: 15:00 UTC > > (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) > > # Location: #fedora-meeting-1 on irc.freenode.net > > Sorry, I

Re: 2015-07-22 @ 21:00 - Taskotron Outage and qadevel Migration

I've also noticed that phab.qadevel.cloud.fedoraproject.org stopped working via HTTP - now it works only through HTTPS, so if anybody thinks that Phabricator stopped working for him, first check that you are using correct protocol. Jan ___ qa-devel

Re: openQA vs. Rawhide

Great article! I'm little bit frustrated - things like this doesn't make it easy for us. On the other hand, if it wasn't for OpenQA, we perhaps wouldn't notice it at all. - Original Message - From: Adam Williamson adamw...@fedoraproject.org To: Fedora QA Development

Re: openQA vs. Rawhide

also I think the Boston box is on git master branch (of openqa_fedora and openqa_fedora_tools), not develop, and I think is missing some of the latest commits Just a side-note - yes, Boston machine is running on master. I thought of it as production machine. But it raises questions - should we