FTBFS on Maverick (hangs on external.sh test)

[Stefano Rivera]

Binary package hint: darcs

Darcs doesn't seem to have been built successfully since lucid.

Logs show:

make[1]: Entering directory `/build/buildd/darcs-2.4.4'
./Setup test

Session terminated, killing shell...make[1]: *** wait: No child processes. Stop.
make[1]: *** Waiting for unfinished jobs....
make[1]: *** wait: No child processes. Stop.
make: *** wait: No child processes. Stop.
make: *** Waiting for unfinished jobs....
make: *** wait: No child processes. Stop.
 ...killed.
Build killed with signal 15 after 150 minutes of inactivity

Some more digging shows external.sh to be the issue.

[Stefano Rivera (stefanor)]

LP Bug auto-closing is currently broken:

darcs (2.4.4-2ubuntu1) maverick; urgency=low

  * Disable external.sh test (requires network connectivity). LP: #636603

[Iain Lane (laney)]

Nice fix! I wonder why the builds didn't fail on Debian then... Indeed logs there show:

  Running external.sh ... passed.

anyway, I guess these problems should be sent upstream (that's upstream upstream)

  * external.sh requires connectivity even though it shouldn't
  * darcs /hangs/ when connectivity is expected, instead of timing out after a reasonable period

could you do that?

Cheers again for the fix, it's much appreciated,
Iain

[Stefano Rivera (stefanor)]

There's another issue in that the test runner buffers output (or it would have been obvious which test was blocking).

I was hoping the Debian maintainer would forward upstream, but he appears to be on holiday so I can do it - although I don't speak haskell and can't write patches for everything :P

[Iain Lane (laney)]

On Mon, Sep 13, 2010 at 08:33:47AM -0000, Stefano Rivera wrote:
>There's another issue in that the test runner buffers output (or it
>would have been obvious which test was blocking).
>
>I was hoping the Debian maintainer would forward upstream, but he
>appears to be on holiday so I can do it - although I don't speak haskell
>and can't write patches for everything :P

Yeah, I'm not expecting you to patch it, just to inform them of the issue!

[Stefano Rivera (stefanor)]

Looks like someone's eyes are open. I hadn't even reported it yet:

Mon Sep 13 11:41:32 SAST 2010 Eric Kow <email address hidden>
  * Mark ssh test as skipped if REMOTE is not set.
    hunk ./tests/network/ssh.sh 42
    - exit 0 # exit normally in case we are being run from the shell harness
    + exit 200

Mon Sep 13 11:40:48 SAST 2010 Eric Kow <email address hidden>
  * Move external and ssh tests to network directory.
    move ./tests/external.sh ./tests/network/external.sh
    move ./tests/ssh.sh ./tests/network/ssh.sh