emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Two unexpected failures in `make test'
Date: Mon, 01 Apr 2019 16:46:10 -0400	[thread overview]
Message-ID: <871s2lqwrx.fsf@alphaville.usersys.redhat.com> (raw)

Running `make test' on the current git version () showed two
unexpected failures:

==============
Ran 816 tests, 814 results as expected, 2 unexpected (2019-04-01 16:35:17-0400, 22.330179 sec)
11 expected failures

2 unexpected results:
   FAILED  ob-emacs-lisp/dynamic-lexical-edit
   FAILED  test-ob-shell/session

make: *** [mk/targets.mk:105: test] Error 1

==============
The first one:

Test ob-emacs-lisp/dynamic-lexical-edit backtrace:
  signal(user-error ("Cannot modify an area being edited in a dedicate
  apply(signal (user-error ("Cannot modify an area being edited in a d
  (setq value-188 (apply fn-186 args-187))
  (unwind-protect (setq value-188 (apply fn-186 args-187)) (setq form-
  (if (unwind-protect (setq value-188 (apply fn-186 args-187)) (setq f
  (let (form-description-190) (if (unwind-protect (setq value-188 (app
  (let ((value-188 'ert-form-evaluation-aborted-189)) (let (form-descr
  (let* ((fn-186 #'eq) (args-187 (condition-case err (let ((signal-hoo
  (progn (let* ((fn-171 #'eq) (args-172 (condition-case err (let ((sig
  (let* ((--cl-execute-- #'(lambda (text) (let ((file ...) (kill-buffe
  (lambda nil (let* ((--cl-execute-- #'(lambda (text) (let (... ... ..
  ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
  ert-run-test(#s(ert-test :name ob-emacs-lisp/dynamic-lexical-edit :d
  ert-run-or-rerun-test(#s(ert--stats :selector "\\(org\\|ob\\)" :test
  ert-run-tests("\\(org\\|ob\\)" #f(compiled-function (event-type &res
  ert-run-tests-batch("\\(org\\|ob\\)")
  ert-run-tests-batch-and-exit("\\(org\\|ob\\)")
  (let ((org-id-track-globally t) (org-test-selector (if org-test-sele
  org-test-run-batch-tests("\\(org\\|ob\\)")
  eval((org-test-run-batch-tests org-test-select-re))
  command-line-1(("--eval" "(setq vc-handled-backends nil org-startup-
  command-line()
  normal-top-level()
Test ob-emacs-lisp/dynamic-lexical-edit condition:
    (user-error "Cannot modify an area being edited in a dedicated buffer")
   FAILED   28/816  ob-emacs-lisp/dynamic-lexical-edit (0.019215 sec)


===========
The second:

Test test-ob-shell/session condition:
    (wrong-type-argument markerp nil)
   FAILED  177/816  test-ob-shell/session (0.004367 sec)

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

             reply	other threads:[~2019-04-01 20:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 20:46 Nick Dokos [this message]
2019-04-01 22:10 ` Two unexpected failures in `make test' 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=871s2lqwrx.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.com \
    --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).