Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Testrunner fails to find `clojure.core/pcalls` in unit test even though it works locally

Open
#38 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
clojure
Domain
testing

Research direction

Start by reproducing the failure with lein test, then inspect the unit test that uses clojure.core/pcalls and compare it with the site's submission path. Done means the bank-account solution passes in the testrunner environment without a Could not resolve symbol: pcalls analysis error.

Written by the indexing model from the issue text.

Description

I have a solution to bank-account:

(ns bank-account)

(defn open-account []
  (atom 0))

(defn close-account [account]
  (reset! account nil))

(defn get-balance [account]
  @account)

(defn update-balance [account amount]
  (swap! account + amount))

which works fine when doing lein test locally but fails with:

----- Error --------------------------------------------------------------------
Type:     clojure.lang.ExceptionInfo
Message:  Could not resolve symbol: pcalls
Phase:    analysis

when submitting the solution to the site. I had a different and more verbose solution earlier and it seems to have passed.

pcalls is used in one of the unit tests which from what I understand are not user-changeable. Also pcalls is part of clojure.core which should be automatically require:d unless explicitly excluded in clojure.

Not sure what is going on here.

Dominant language
Clojure
Stars
2
Forks
10
Avg merge
10m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from exercism/clojure-test-runner

All issues in exercism/clojure-test-runner

Similar issues

More Clojure issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.