From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marco Wahl Subject: Re: Question about running the tests Date: Sat, 11 Feb 2017 12:22:32 +0100 Message-ID: <84d1epq8ef.fsf@tm6592> References: <84shnm18zo.fsf@tm6592> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46465) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ccVlQ-0003Ly-B1 for emacs-orgmode@gnu.org; Sat, 11 Feb 2017 06:22:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ccVlN-0001m2-67 for emacs-orgmode@gnu.org; Sat, 11 Feb 2017 06:22:48 -0500 Received: from [195.159.176.226] (port=40884 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ccVlM-0001lg-UG for emacs-orgmode@gnu.org; Sat, 11 Feb 2017 06:22:45 -0500 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1ccVlE-0007sQ-Vm for emacs-orgmode@gnu.org; Sat, 11 Feb 2017 12:22:36 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Cc: Skip Collins , Carsten Dominik > 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