Re: [Fedora-packaging] May I file 1000 bugs aka upstream test suite tracking

2014-02-21 Thread Alexander Todorov

На 21.02.2014 16:27, Richard W.M. Jones написа:

Is it correct that you're only going to be filing bugs when upstream
tarballs already contain test suites, but they are just not enabled in
the Fedora package?


Hi Richard,
I meant just the opposite. However I will also do what you suggest but this will 
result in far less number of bugs (probably around 100).


I want to track which packages *DO NOT* have any tests and later be able to 
focus on creating them (be it working with volunteers, GSoC participants or 
whoever is willing to step up to this task).


I don't intend to force package maintainers to write tests if they don't want to 
(or can't).



--
Alex
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Fedora-packaging] May I file 1000 bugs aka upstream test suite tracking

2014-02-21 Thread Matthias Clasen
On Fri, 2014-02-21 at 16:51 +0200, Alexander Todorov wrote:

 I want to track which packages *DO NOT* have any tests and later be able to 
 focus on creating them (be it working with volunteers, GSoC participants or 
 whoever is willing to step up to this task).

In that case, I suggest simply keeping a list of good candidate packages
for adding testsuites on the wiki somewhere. That is much less of a
hassle than hundreds of bugs.


-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Fedora-packaging] May I file 1000 bugs aka upstream test suite tracking

2014-02-21 Thread Daniel P. Berrange
On Fri, Feb 21, 2014 at 04:22:42PM +0200, Alexander Todorov wrote:
 Hi guys,
 (note: devel, packaging and test lists) previously I've done a
 little experiment and counted how many packages are likely to have
 upstream test suites and how many don't:
 http://atodorov.org/blog/2013/12/24/upstream-test-suite-status-of-fedora-20/
 
 In general around 35% do have test suites, the rest don't.
 
 My goal is to bring down the number of packages which ship without
 any sort of test suite inside their code base.
 
 The first step is to identify them and track them in Bugzilla.
 
 
 My question is:
 **Is everyone, especially package maintainers OK with me filing 1000+ bugs ?**
 
 
 Last time I did so (around 100 bugs) it got a few people unhappy so
 better ask this time!

If you have code that can fairly reliably detect whether a test suite
exists in the source tar.gz, then I think you would be justified
in filing bugs for spec files which have not enabled the test suite.

What I wouldn't do is blindly mass file bugs against every package
and ask the maintainer to investigate whether the test suite exists
or not. Basically you want to minimize the risk of false bug reports
against tests not being enabled, to avoid wasting maintainers time.

Regards,
Daniel
-- 
|: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org  -o- http://virt-manager.org :|
|: http://autobuild.org   -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc :|
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Fedora-packaging] May I file 1000 bugs aka upstream test suite tracking

2014-02-21 Thread Aleksandar Kurtakov
- Original Message -
 From: Alexander Todorov atodo...@redhat.com
 To: Discussion of RPM packaging standards and practices for Fedora 
 packag...@lists.fedoraproject.org,
 Development discussions related to Fedora de...@lists.fedoraproject.org
 Cc: For testing and quality assurance of Fedora releases 
 test@lists.fedoraproject.org
 Sent: Friday, February 21, 2014 4:51:52 PM
 Subject: Re: [Fedora-packaging] May I file 1000 bugs aka upstream test suite  
 tracking
 
 На 21.02.2014 16:27, Richard W.M. Jones написа:
  Is it correct that you're only going to be filing bugs when upstream
  tarballs already contain test suites, but they are just not enabled in
  the Fedora package?
 
 Hi Richard,
 I meant just the opposite. However I will also do what you suggest but this
 will
 result in far less number of bugs (probably around 100).
 
 I want to track which packages *DO NOT* have any tests and later be able to
 focus on creating them (be it working with volunteers, GSoC participants or
 whoever is willing to step up to this task).

These are upstream bugs and having them open in Fedora bz would do no good. 
While this value is valuable it's not Fedora bug and list of packages that are 
missing test suites in general would better be kept on e.g. wiki page where 
volunteers can pick one and work with upstream to add test suite. 
For packages that has test suites but don't compile/run it's another story.

Alexander Kurtakov
Red Hat Eclipse team

 
 I don't intend to force package maintainers to write tests if they don't want
 to
 (or can't).
 
 
 --
 Alex
 --
 test mailing list
 test@lists.fedoraproject.org
 To unsubscribe:
 https://admin.fedoraproject.org/mailman/listinfo/test
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Fedora-packaging] May I file 1000 bugs aka upstream test suite tracking

2014-02-21 Thread Alexander Todorov

На 21.02.2014 16:55, Daniel P. Berrange написа:


If you have code that can fairly reliably detect whether a test suite
exists in the source tar.gz, then I think you would be justified
in filing bugs for spec files which have not enabled the test suite.



At present I'm aware of 11 different location (directory or file names) which 
represent tests. Not sure how accurate is this though.



What I wouldn't do is blindly mass file bugs against every package
and ask the maintainer to investigate whether the test suite exists
or not.


I try to avoid that to the extent possible.

--
Alex
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Fedora-packaging] May I file 1000 bugs aka upstream test suite tracking

2014-02-21 Thread Alexander Todorov

На 21.02.2014 16:58, Tom Hughes написа:

On 21/02/14 14:57, Daniel P. Berrange wrote:

On Fri, Feb 21, 2014 at 02:53:55PM +, Tom Hughes wrote:

On 21/02/14 14:51, Alexander Todorov wrote:


I want to track which packages *DO NOT* have any tests and later be able
to focus on creating them (be it working with volunteers, GSoC
participants or whoever is willing to step up to this task).


Why would you file a bug in the Fedora bug tracker when the package
has no test suite upstream? That makes no sense - if the upstream
package has no tests then the bug belongs upstream not in Fedora.


I don't believe that is what he is proposing. I read it as meaning
filing bugs where upstream *does* have a test suite, but the RPM
specfile has not enabled it in %check.


That was what I thought he really meant originally, and that was what the wiki
page suggested, but it doesn't seem to be what he is saying in the message I
quoted.



Guys I can do both.

1) Report packages which *have* test suites but they are *not* executed in 
%check

2) Report packages which *don't* have any test suites at all.

1) is easy but I'm more interested in 2)

--
Alex

--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Fedora-packaging] May I file 1000 bugs aka upstream test suite tracking

2014-02-21 Thread Ralf Corsepius

On 02/21/2014 05:43 PM, Nikos Roussos wrote:

On February 21, 2014 4:51:52 PM EET, Alexander Todorov atodo...@redhat.com 
wrote:

На 21.02.2014 16:27, Richard W.M. Jones написа:

Is it correct that you're only going to be filing bugs when upstream
tarballs already contain test suites, but they are just not enabled

in

the Fedora package?


Hi Richard,
I meant just the opposite. However I will also do what you suggest but
this will
result in far less number of bugs (probably around 100).

I want to track which packages *DO NOT* have any tests and later be
able to
focus on creating them (be it working with volunteers, GSoC
participants or
whoever is willing to step up to this task).


And what happens if you create a testing suite for a project but the upstream 
is unwilling to integrate?
It seems that it would make more sense to do it in cooperation with upstream, 
thus filing the bug there.
Exactly. However most upstreams who are confronted with bugs telling 
them Your package is lacking a testsuite, please add one, without 
being presented a concrete proposaly will simply close this bug and 
consider the submitter to be troll.



Ralf


--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test