From: Bastien <bzg@altern.org>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: "make test" failure
Date: Mon, 11 Feb 2013 18:33:43 +0100 [thread overview]
Message-ID: <87fw12bvrc.fsf@bzg.ath.cx> (raw)
In-Reply-To: <1810.1360603147@alphaville> (Nick Dokos's message of "Mon, 11 Feb 2013 12:19:07 -0500")
[-- Attachment #1: Type: text/plain, Size: 249 bytes --]
Hi Nick,
Nick Dokos <nicholas.dokos@hp.com> writes:
> Just pulled and ran "make test". I get one failure with the
> appended backtrace:
I submitted this patch to Nicolas so that he can approve/apply
it. I think the test is wrong, not the code.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: test-fix.patch --]
[-- Type: text/x-patch, Size: 709 bytes --]
diff --git a/testing/lisp/test-org.el b/testing/lisp/test-org.el
index dac5fd2..561ac98 100644
--- a/testing/lisp/test-org.el
+++ b/testing/lisp/test-org.el
@@ -677,10 +677,7 @@ Outside."
;; headline at the same level.
(goto-line 3)
(org-backward-element)
- (should (looking-at (regexp-quote "* Head 1")))
- ;; 4.3. At the first top-level headline: should error.
- (goto-line 2)
- (should-error (org-backward-element)))
+ (should (looking-at (regexp-quote "** Head 1.1"))))
;; 5. At beginning of first element inside a greater element:
;; expected to move to greater element's beginning.
(org-test-with-temp-text "Before.\n#+BEGIN_CENTER\nInside.\n#+END_CENTER"
[-- Attachment #3: Type: text/plain, Size: 14 bytes --]
--
Bastien
next prev parent reply other threads:[~2013-02-11 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 17:19 "make test" failure Nick Dokos
2013-02-11 17:33 ` Bastien [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-31 20:49 ``make test'' failure Nick Dokos
2017-11-01 20:57 ` Nicolas Goaziou
2017-11-02 16:15 ` Nick Dokos
2017-11-03 21:17 ` Nicolas Goaziou
2017-11-06 0:32 ` Nick Dokos
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=87fw12bvrc.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.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).