emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [babel] BUG in :session
Date: Mon, 26 Sep 2011 15:59:25 +0200	[thread overview]
Message-ID: <80r533l802.fsf@somewhere.org> (raw)
In-Reply-To: 877h4vxzja.fsf@gmail.com

Hi Eric,

Eric Schulte wrote:
> "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> Martyn Jago wrote:
>>> "Sebastien Vauban"
>>> <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>>>> Loading /cygdrive/c/home/sva/src/org-mode/testing/lisp/test-ob-R.el (source)...
>>>> peculiar error
>>
>> Just git pull'ed, and re-tested:
>>
>>     ┏━━━━
>>     ┃ Ran 111 tests, 104 results as expected, 7 unexpected (2011-09-26 08:20:06+0200)
>>     ┃ 
>>     ┃ 7 unexpected results:
>>     ┃    FAILED  ob-fortran/command-arguments
>>     ┃    FAILED  ob-fortran/fortran-var-program
>>     ┃    FAILED  ob-fortran/input-var
>>     ┃    FAILED  ob-fortran/list-var
>>     ┃    FAILED  ob-fortran/list-var-from-table
>>     ┃    FAILED  ob-fortran/preprosessor-var
>>     ┃    FAILED  ob-fortran/simple-program
>>     ┗━━━━
>>
>> "Normal", I don't have any fortran installed. Maybe, some sort of protection
>> should have to be applied to these too.
>
> I've just improved the code which checks for executables as the previous
> version was probably linux-specific.  The following should now throw an
> error on your system which should inhibit loading of the fortran tests.
>
> (org-test-for-executable "gfortran")

New status:

    ┏━━━━
    ┃ Ran 102 tests, 102 results as expected (2011-09-26 15:54:14+0200)
    ┗━━━━

Perfect...


>>>> This is on Windows XP SP3, with a Cygwin Emacs (when run from terminal;
>>>> otherwise, it is a Win32 binary from the FSF).
>>>
>>> Its really great to hear you are running the tests on Windows. At some
>>> point I hope to test with the EmacsW32 port.
>>
>> I can do it as well. I should automate this -- not difficult, though.
>>
>> If there is some shared place to place such results, I can imagine running
>> them every couple of hours (cron'ed), or so, and publish the resulting HTML. I
>> could do this when being online, that is more or less half of the time.
>
> This sounds great.  I agree that a public place to post results would be
> useful.  Also, while we don't have any HTML export right now, simply
> redirecting the results of the test execution to a file should be
> sufficient.

We can put such in place. For Windows tests, it could be someone else, if
someone promises to be 24/7 online -- what won't be my case. Otherwise, I'm
willing to do it, simply know that there will be holes in the update of the
results.

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2011-09-26 13:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 11:19 [babel] BUG in :session Rainer M Krug
2011-09-21 12:57 ` Eric Schulte
2011-09-21 16:56   ` Martyn Jago
2011-09-21 18:54     ` Sebastien Vauban
2011-09-21 19:32       ` Eric Schulte
2011-09-21 19:32     ` Eric Schulte
2011-09-21 20:09       ` Sebastien Vauban
2011-09-21 21:20         ` Martyn Jago
2011-09-22  2:23           ` Eric Schulte
2011-09-23 11:36             ` Martyn Jago
2011-09-23 15:59               ` Eric Schulte
2011-09-23 16:12                 ` Martyn Jago
2011-09-23 22:16                   ` Sebastien Vauban
2011-09-24 22:13                     ` Eric Schulte
2011-09-25  8:37                     ` Martyn Jago
2011-09-26  7:54                       ` Sebastien Vauban
2011-09-26 12:23                         ` Eric Schulte
2011-09-26 13:59                           ` Sebastien Vauban [this message]
2011-09-24 22:12                   ` Eric Schulte
2011-09-25  8:31                     ` Martyn Jago
2011-09-21 17:09   ` Rainer M Krug

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=80r533l802.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).