GNU bug report logs -
#24402
25.1.50; testcover-start breaks should-error
Previous Next
Reported by: Gemini Lasswell <gazally <at> runbox.com>
Date: Sat, 10 Sep 2016 02:19:01 UTC
Severity: normal
Tags: confirmed, fixed, patch
Found in versions 25.1.50, 26.0.50
Fixed in version 26.1
Done: npostavs <at> users.sourceforge.net
Bug is archived. No further changes may be made.
Full log
Message #47 received at 24402 <at> debbugs.gnu.org (full text, mbox):
Alex <agrambot <at> gmail.com> writes:
> npostavs <at> users.sourceforge.net writes:
>
>> Does it also work when loading the elc version of the test file? (try
>> 'make check TEST_LOAD_EL=no')
>
> Oh, it doesn't load the elc version by default? That's surprising; I
> think that should be documented in the test README.
>
> I get 3 test failures with TEST_LOAD_EL=no, but I don't believe they're
> because of me. On a mostly clean master (d014a5e15) those 3 also error.
> One of them is simple to fix (the (require 'subr-x) should not be inside
> eval-when-compile in dom-tests).
Ah, the `should' blocks inlining during compilation. Is that necessary?
Probably yes if we expect to catch errors during macroexpansion I guess.
> The other failing tests are
> subr-test-backtrace-integration-test and cl-lib-defstruct-record.
Hmm, I'll see if I can fix these.
>> What about tests like this?
>>
>> (ert-deftest check-error-handling ()
>> (should
>> (eq 42
>> (condition-case ()
>> (/ 1 0)
>> (arith-error 42)))))
>
> It works for me, yes. As long as `debugger' is set to a symbol. I can
> make it a bit more robust by using an additional defvar in
> ert--run-test-internal.
>
> Are you asking because it doesn't work for you?
No, I'm just trying to explore the edges of this solution. Isn't
`debugger' bound to a non-symbol while running the the tests? I'm
confused as to why this solution works.
This bug report was last modified 7 years and 133 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.