emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marco Wahl <marcowahlsoft@gmail.com>
To: emacs-orgmode@gnu.org
Cc: Skip Collins <skip.collins@gmail.com>,
	Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Question about running the tests
Date: Sat, 11 Feb 2017 12:22:32 +0100	[thread overview]
Message-ID: <84d1epq8ef.fsf@tm6592> (raw)
In-Reply-To: CABUh-74WYQ5MZSwJgFeLGZ-2HMHCWfVv-XSgzd=-CyoHvK081g@mail.gmail.com


> Perhaps the bundled org in stock emacs interfered with a newer
> downloaded version because load-path is not configured properly. If a
> mixed-version installation happened to Carsten, it is probably
> happening to lots of people. I also use a Mac and it's happened to me
> before. What else can be done to prevent this from affecting normal
> users? Would it be possible for org to do a quick self-consistency
> check on startup?

There could be done a lot, I guess.

But I think the situation currently is quite good.

There is http://www.randomsample.de:4457/waterfall which shows the
last build on a reference platform.

You can checkout a fresh orgmode source-tree and activate it with a
minimal configuration file.

If there are problems with an individually configured installation you
have no other choice than to somehow find out what is the culprit
AFAICS.  E.g. debugging and comparing to a reference.

Btw for the concrete issue in this thread about "ob-sh" and "sh" the
user-individual settings for BTEST_OB_LANGUAGES in the local*.mk
makefiles could be of interest.


Best regards

                       Marco

      reply	other threads:[~2017-02-11 11:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10  8:57 Question about running the tests Carsten Dominik
2017-02-10 13:16 ` Marco Wahl
2017-02-10 22:21   ` Skip Collins
2017-02-11 11:22     ` Marco Wahl [this message]

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=84d1epq8ef.fsf@tm6592 \
    --to=marcowahlsoft@gmail.com \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=skip.collins@gmail.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.
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).