5
88%
master: 88%

Ran 09 May 2018 06:14AM UTC

Files 52

Run time 2s

Badge

Embed ▾

Committed 09 May 2018 06:14AM UTC coverage: 80.21%. First build

Job # TEST_CMD="./lein-261 with-profile +1.8,+plugin.mranderson/config,+test-clj test"

Build Type

Pull #341

travis-ci

Committed by Chris Perkins

Commit Message

Don't step in to clojure.core functions

The new step-in command makes it easy to step in (often accidentally) to
a function in clojure.core. But instrumenting clojure core functions is
dangerous, and can result in a stack overflow that crashes the nrepl
process. In fact, just instrumenting `clojure.core/symbol?` (without
even debugging it) causes a stack overflow. I'm not entirely sure yet
how this happens, but it seems safest to just prevent stepping in to all
core functions by default.

This commit starts to make that configurable - the default is to only
skip step-in for clojure.core, but you can add names or patterns to the
atom `step-in-blacklist` to prevent step-in for other namespaces.

Pull Request Pull Request #341: Don't step in to clojure.core functions

Run Details

3591 of 4477 relevant lines covered (80.21%)

0.8 hits per line

clojure-emacs / cider-nrepl / 1152 / 5
88%
master: 88%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1152.5 (TEST_CMD="./lein-261 with-profile +1.8,+plugin.mranderson/config,+test-clj test")

clojure-emacs / cider-nrepl / 1152 / 5 88% master: 88%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1152.5 (TEST_CMD="./lein-261 with-profile +1.8,+plugin.mranderson/config,+test-clj test")

clojure-emacs / cider-nrepl / 1152 / 5
88%
master: 88%

README BADGES
x