emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] FYI: Org mode testing framework, Emacs 23 and 22


From: David Maus
Subject: Re: [O] FYI: Org mode testing framework, Emacs 23 and 22
Date: Sun, 18 Sep 2011 11:01:49 +0200
User-agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (Gojō) APEL/10.8 Emacs/23.2 (i486-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)

At Sat, 17 Sep 2011 14:56:09 -0600,
Eric Schulte wrote:
>
> Hi David,
>
> >
> > For Emacs22 the only thing we need from simple.el is the definition of
> > special-mode; going to factor it out and trim it to Emacs22.
> >
>
> Sounds great, thanks.

Done. Conditionally defined in org-test.el when Emacs version = 22.

>
> >
> > With HEAD at dbf0e6d5bcbe94c8ee57d68889d3c25bf9cdef55 and a fix for
> > the check for featurep 'org (37db5deea5ef75186bb7413b196fa0c96e5bdfb9)
> > I got:
> >
>
> Thanks for compiling this information.
>
> >
> >
> > Selector: "\\(org\\|ob\\)"
> > Passed: 99
> > Failed: 10 (10 unexpected)
> > Total:  109/109
> >
> > Started at:   2011-09-16 06:56:59+0200
> > Finished.
> > Finished at:  2011-09-16 06:57:04+0200
> >
> > ......FF...................................................FF..F.F.......FF.................F..............F.
> >
> > F ob-fortran/list-var
> >     Test real array input
> >     (void-function characterp)
> >
> > F ob-fortran/list-var-from-table
> >     Test real array from a table
> >     (void-function characterp)
> >
>
> I've replaced the use of `characterp' in ob-fortran with integerp, which
> should be backwards-compatible with emacs22.

These errors are gone.

>
> >
> > F test-ob-exp/org-babel-exp-src-blocks/w-no-file
> >     Testing export from buffers which are not visiting any file.
> >     (wrong-type-argument stringp nil)
> >
> > F test-ob-exp/org-babel-exp-src-blocks/w-no-headers
> >     Testing export without any headlines in the org-mode file.
> >     (wrong-type-argument stringp nil)
> >
> > F test-ob-lob/export-lob-lines
> >     Test the export of a variety of library babel call lines.
> >     (wrong-type-argument stringp nil)
> >
>
> I have no idea what could be going wrong with these executions, would it
> be difficult to generate backtraces for these failures?

No, its really easy (as expected w/ Emacs): Section on interactive
debugging ERT mentions "b" to create the backtrace.

In case of w-no-file and w-no-headers `org-todo-line-regexp' is bound
to nil, in export-lob-lines `org-maybe-keyword-time-regexp' is bound
to nil. Backtraces are attached.

Best,
  -- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... address@hidden
Email..... address@hidden

Attachment: test-ob-exp--org-babel-exp-src-blocks--w-no-headers.backtrace.gz
Description: Binary data

Attachment: test-ob-exp--org-babel-exp-src-blocks--w-no-file.backtrace.gz
Description: Binary data

Attachment: test-ob-lob--export-lob-lines.backtrace.gz
Description: Binary data

Attachment: pgpfG4v3HeQ8c.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]