Hi All ! This is 3rd attempt to review a package. There was old topic, but I decided to create a new one, to stay focused. I have a proposal package review - and proposal package review procedure. Example package review: =============================================== "iperf" - IP Performance benchmark Description: Iperf is a tool to measure maximum TCP bandwidth, allowing the tuning of various parameters and UDP characteristics. Iperf reports bandwidth, delay jitter, datagram loss. This package is in OBS. Current maintainer: James Oakley (James also interested in contributing to "contrib" repo, so he may become a package maintainer) Alternative maintainer: me (Alexey Eromenko "Technologov") (if James don't wan't or can't support his child package) URL : http://dast.nlanr.net/Projects/Iperf/ URL 2 : http://sourceforge.net/projects/iperf License: custom OSS-compatible, BSD-like (http://dast.nlanr.net/Projects/Iperf/ui_license.html) Latest update: v2.0.4 Apr 2008 (which means, that package is maintained) OBS URL: http://download.opensuse.org/repositories/home:/jimfunk/openSUSE_11.0/src/ Testing: Package received some testing from me. Everything tested found to work. No crashes. =============================================== 1. What do you think of the review process 2. What do you think of the package -------------------------- In the previous set no one had any objection over the package - except maintenance. I think if no objection will happen now we will link (or copy) this package right from James Oakley OBS into contrib. -- -Alexey Eromenko "Technologov" -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-contrib+help@opensuse.org
Alexey Eremenko wrote:
I think if no objection will happen now we will link (or copy) this package right from James Oakley OBS into contrib.
Please don't. First, there rules aren't there yet. Second, the request should come from the package maintainer (if you are going to maintain the package and not James, then copy it to your home). Michal -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-contrib+help@opensuse.org
On Mon, Sep 15, 2008 at 2:43 PM, Michal Marek <mmarek@suse.cz> wrote:
Alexey Eremenko wrote:
I think if no objection will happen now we will link (or copy) this package right from James Oakley OBS into contrib.
Please don't. First, there rules aren't there yet. Second, the request should come from the package maintainer (if you are going to maintain the package and not James, then copy it to your home).
I have already copied, as I use this package myself. + James was positive about this idea. And as I said, I'm the "backup package maintainer" of sorts. -- -Alexey Eromenko "Technologov" -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-contrib+help@opensuse.org
On Sunday 14 September 2008 11:59:09 Alexey Eremenko wrote:
Testing: Package received some testing from me. Everything tested found to work. No crashes.
There was an issue where it simply deadlocked in server mode (forking *and* threading is always fun) which was fixed in 2.0.3. I just updated to 2.0.4 and it now works, but the server thread it creates appears to never stop and consumes 100% CPU indefinitely. I'm going to file a bug, and maybe take a look myself. I'd rather not push this for review until this issue is resolved. However, I would like to help kickstart the project so I will submit another package for review. The trick is finding something I have that isn't developer-oriented, has a wider appeal, and has no issues that I am aware of. :-) -- James Oakley jfunk@funktronics.ca -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-contrib+help@opensuse.org
On Tue, Sep 16, 2008 at 5:17 PM, James Oakley <jfunk@funktronics.ca> wrote:
On Sunday 14 September 2008 11:59:09 Alexey Eremenko wrote:
Testing: Package received some testing from me. Everything tested found to work. No crashes.
There was an issue where it simply deadlocked in server mode (forking *and* threading is always fun) which was fixed in 2.0.3. I just updated to 2.0.4 and it now works, but the server thread it creates appears to never stop and consumes 100% CPU indefinitely.
I use iperf 2.0.2 for quite some time, and experience no deadlocks and no high CPU consumption. (when iperf is idle) There is only CPU consumption, when it runs test, which is normal. How to reproduce the problem you have ? -- -Alexey Eromenko "Technologov" -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-contrib+help@opensuse.org
On Wednesday 17 September 2008 03:50:53 Alexey Eremenko wrote:
On Tue, Sep 16, 2008 at 5:17 PM, James Oakley <jfunk@funktronics.ca> wrote:
On Sunday 14 September 2008 11:59:09 Alexey Eremenko wrote:
Testing: Package received some testing from me. Everything tested found to work. No crashes.
There was an issue where it simply deadlocked in server mode (forking *and* threading is always fun) which was fixed in 2.0.3. I just updated to 2.0.4 and it now works, but the server thread it creates appears to never stop and consumes 100% CPU indefinitely.
I use iperf 2.0.2 for quite some time, and experience no deadlocks and no high CPU consumption. (when iperf is idle) There is only CPU consumption, when it runs test, which is normal. How to reproduce the problem you have ?
It only happens in daemon mode: rciperf start iperf -c 127.0.0.1 Once the test ends, the server thread continues to consume 100% CPU. Maybe it's only on the systems I have (x86_64), but if you want to test it on your machines, I'd like to know the results. -- James Oakley jfunk@funktronics.ca -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-contrib+help@opensuse.org
participants (3)
-
Alexey Eremenko -
James Oakley -
Michal Marek