emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Bug] Tests for experimental org-features should expect to fail if not activated by the user
Date: Sun, 04 Mar 2012 16:46:58 +0100	[thread overview]
Message-ID: <87r4x8e5cd.fsf@gmail.com> (raw)
In-Reply-To: <87hay4v4aj.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 04 Mar 2012 15:17:40 +0100")

Achim Gratz <Stromeko@nexgo.de> writes:

> Well, that is likely because you run the test on uncompiled source,
> while I am running it on compiled orgmode... maybe one of these pesky
> byte-compiler warnings shouldn't have been ignored.  I can't reproduce
> the 24 unexpected results, but they probably have a similar origin
> (partially compiled orgmode?).

It's possible. I have two different Org installations. One compiled for
my work, and the other, uncompiled for development. Both are latest git
version.

When batch running tests on my compiled Org, I get:

--8<---------------cut here---------------start------------->8---
Ran 130 tests, 105 results as expected, 25 unexpected (2012-03-04 15:42:25+0100)
9 expected failures

25 unexpected results:
   FAILED  ob-emacs-lisp/commented-last-block-line-no-var
   FAILED  ob-emacs-lisp/commented-last-block-line-with-var
   FAILED  ob-exp/exports-both
   FAILED  ob-exp/mixed-blocks-with-exports-both
   FAILED  ob-exp/noweb-no-export-and-exports-both
   FAILED  ob-exp/noweb-on-export
   FAILED  ob-exp/noweb-on-export-with-exports-results
   FAILED  ob-exp/noweb-strip-export-ensure-strips
   FAILED  test-ob-lob/do-not-eval-lob-lines-in-example-blocks-on-export
   FAILED  test-ob-sh/dont-error-on-empty-results
   FAILED  test-ob/commented-last-block-line-no-var
   FAILED  test-ob/commented-last-block-line-with-var
   FAILED  test-ob/org-babel-remove-result--results-default
   FAILED  test-org-babel/combining-scalar-and-raw-result-types
   FAILED  test-org-babel/elisp-in-header-arguments
   FAILED  test-org-babel/inline-src-blocks
   FAILED  test-org-babel/inline-src_blk-default-results-replace-line-1
   FAILED  test-org-babel/just-one-results-block
   FAILED  test-org-babel/multi-line-header-arguments
   FAILED  test-org-babel/parse-header-args
   FAILED  test-org-babel/parse-header-args2
   FAILED  test-org-babel/simple-named-code-block
   FAILED  test-org-babel/simple-variable-resolution
   FAILED  test-org-footnote/normalize-outside-org
   FAILED  test-org-table/simple-formula
--8<---------------cut here---------------end--------------->8---

So, indeed, the second failing test appears.  It should pass now (at
least it does even on my compiled Org installation).

I think the others come from a file-error ("Opening output file").

Thanks for your help.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2012-03-04 15:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-26 20:24 [Bug] Tests for experimental org-features should expect to fail if not activated by the user Achim Gratz
2012-02-29 16:18 ` Eric Schulte
2012-02-29 20:07   ` Achim Gratz
2012-02-29 20:52     ` Eric Schulte
2012-02-29 21:02       ` Achim Gratz
2012-03-01 21:18       ` Achim Gratz
2012-03-02 14:15         ` Nicolas Goaziou
2012-03-02 17:38           ` Achim Gratz
2012-03-03 17:28           ` Achim Gratz
2012-03-03 21:50             ` Nicolas Goaziou
2012-03-04  9:59               ` Achim Gratz
2012-03-04 13:42                 ` Nicolas Goaziou
2012-03-04 14:17                   ` Achim Gratz
2012-03-04 15:46                     ` Nicolas Goaziou [this message]
2012-03-04 17:04                       ` Achim Gratz
2012-03-03 22:59             ` Sebastien Vauban
2012-03-04  9:39               ` Achim Gratz
2012-03-03 17:21         ` Achim Gratz

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=87r4x8e5cd.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=Stromeko@nexgo.de \
    --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).