public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] nosleep 0.1.3-1 (needs GTG)
Date: Fri, 30 Sep 2011 15:57:00 -0000	[thread overview]
Message-ID: <r1pb8791s5dshole1qc65n3rsn4rc824tt@4ax.com> (raw)
In-Reply-To: <4E85CB52.1070008@cwilson.fastmail.fm>

> Packaging is GTG.

Thanks.

>  I didn't check the application's functionality.

Right.  Unfortunately there's no fast or easy way to do that.  You have to run a
command that takes longer than your idle sleep timer, for example, and check
that the machine doesn't go to sleep.  I have done that and verified that each
of the options works as described, at least on my Windows 7 laptop.  But as I
describe in the man page, it's just hard to completely stop a host from going to
sleep, so it's always going to be hard to completely test that nosleep is
working as intended.

> Since you don't have a test suite, you might want to define a src_test
> function in the cygport:
> 
> src_test() {
> 	:
> }

OK, I'll do that.  

Package uploaders:  please wait for an RFU for nosleep 0.1.3-3.

Maybe in time I can develop a proper test suite, but it will always be a bit
labor-intensive.

Andrew.

  reply	other threads:[~2011-09-30 15:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-25 10:15 [ITP] nosleep 0.1.3-1 Andrew Schulman
2011-09-27 18:33 ` Christopher Faylor
2011-09-27 19:05   ` Reini Urban
2011-09-27 19:18 ` Charles Wilson
2011-09-28 13:53   ` Buchbinder, Barry (NIH/NIAID) [E]
2011-09-28 16:27     ` Andrew Schulman
2011-10-09 19:46       ` Reini Urban
2011-10-11 15:02         ` Andrew Schulman
2011-09-27 21:16 ` Chris Sutcliffe
2011-09-28 15:31 ` Christian Franke
2011-09-30 10:01 ` [ITP] nosleep 0.1.3-1 (needs GTG) Andrew Schulman
2011-09-30 14:00   ` Charles Wilson
2011-09-30 15:57     ` Andrew Schulman [this message]
2011-09-30 17:13       ` Reini Urban
2011-09-30 19:57         ` Andrew Schulman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=r1pb8791s5dshole1qc65n3rsn4rc824tt@4ax.com \
    --to=schulman.andrew@epamail.epa.gov \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).