public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Waldmann <tw@waldmann-edv.de>
To: cygwin@cygwin.com
Subject: borgbackup test fail on cygwin (only) - cygwin pipe issues?
Date: Wed, 11 Jan 2017 03:47:00 -0000	[thread overview]
Message-ID: <8d66dac6-689d-972f-d06a-f4c1869b6b87@waldmann-edv.de> (raw)

Hi,

borgbackup uses a RPC protocol via a ssh pipe to implement client/server
communication.

borg client --pipe-- ssh --tcp-- sshd --pipe-- borg serve

This works very reliable, we have tests running on linux, freebsd,
netbsd, openbsd, OS X. It even works on win10 linux subsystem.

But on Cygwin, only the local tests work, but the remote tests (which
need the pictured ssh pipe) fail or hang.

When trying to find out what's going wrong, I noticed corrupted data
coming over the pipe.

I've found some other pipe issues on the cygwin mailing list, maybe this
is related?

Our issue about this:

https://github.com/borgbackup/borg/issues/1268

Note:

I am one of the borgbackup developers, but I am not a windows developer
(and I personally don't use windows or cygwin except for testing
borgbackup on this platform).

What I could offer is to run the tests on a fixed version.

Thanks for looking into this,

Thomas

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2017-01-11  3:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11  3:47 Thomas Waldmann [this message]
2017-01-12 16:53 ` cyg Simple
2017-01-12 17:32   ` Thomas Waldmann
2017-01-13 18:19   ` Thomas Waldmann
2017-01-13 19:08     ` Thomas Waldmann
2017-01-14 15:38       ` Corinna Vinschen

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=8d66dac6-689d-972f-d06a-f4c1869b6b87@waldmann-edv.de \
    --to=tw@waldmann-edv.de \
    --cc=cygwin@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).