From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Errors get suppressed by org-babel-execute-src-block
Date: Fri, 12 Feb 2016 12:59:13 -0500 [thread overview]
Message-ID: <87oablrery.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 87ziv5kf80.fsf@gmail.com
Aaron Ecay <aaronecay@gmail.com> writes:
> Hi Nick,
>
> 2016ko otsailak 11an, Nick Dokos-ek idatzi zuen:
>>
>> Not sure if there are tests for remote babel execution,
>
> AFAIK no. It would be useful to have these. All the machines I use run
> Linux and are configured very similarly. Many of the problems in remote
> execution come from differences in environments. So it would be good if
> someone could figure out how to test common configurations. Until that
> happens, we have to rely on ad hoc testing or user reports.
>
I think tramp is pretty good at handling environment differences (and if
not, Michael is pretty responsive at modifying it to fix whatever
breakage people uncover), so for org-mode even simple tests in homogeneous
environments should be useful (e.g. using localhost as the "remote", or
the name of the machine that runs the test: not sure how much
optimization is done at various levels, but it might be enough to test
the remote code paths.)
>> but if not, please make sure to test that (with :dir set to some
>> directory on a different machine). Michael Albinus had done some work
>> to get that working a few years ago:
>
> AFAICS my patch does not affect the work Michael did. I will test some
> simple remote execution scenarios before I push the patch, just in case.
>
OK - good!
>> BTW, I tried to test, but applying the patch to current master
>> (8eff64cffee8627578edc33de485201ae579fafe) fails:
>
> Nicolas pushed some big changes to babel just after I sent my patch.
> (Big in terms of the diff to the code, not necessarily in terms of
> changing user behavior). I haven’t looked in detail, but it’s almost
> guaranteed that the patch now needs to be rebased, which I’ll do as
> soon as I can.
Thanks! If you post the patch, I'll try out some simple tests over the
weekend too.
--
Nick
next prev parent reply other threads:[~2016-02-12 17:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 19:02 Errors get suppressed by org-babel-execute-src-block Gary Oberbrunner
2016-02-10 20:23 ` Aaron Ecay
2016-02-10 22:57 ` Nicolas Goaziou
2016-02-12 17:22 ` Aaron Ecay
2016-02-11 17:08 ` Nick Dokos
2016-02-12 17:31 ` Aaron Ecay
2016-02-12 17:59 ` Nick Dokos [this message]
2016-02-14 16:07 ` Aaron Ecay
2016-02-20 13:01 ` Nicolas Goaziou
2016-02-20 13:33 ` Nick Dokos
2016-02-22 16:05 ` Aaron Ecay
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oablrery.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).