Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Return cider-test result keys more specifically #282

Merged
merged 2 commits into from
Jan 5, 2016

Conversation

cap10morgan
Copy link

This brings in commit a62f937 to be compatible with a bug fix going into cider 0.10.1.

* Override `clojure.test` implementation of `test-var` to differentiate
  between errors occurring in assertions and test faults that do not.
* Set the same fault flag on errors occurring in test fixtures.
* Update the `report` function to return only keys that properly
  describe the test event: Failed tests return `actual`; errors return
  `error`. Test assertions have and `expected` value; non-assertion
  faults do not.
@bbatsov
Copy link
Member

bbatsov commented Jan 3, 2016

@benedekfazekas Seems that the new mranderson doesn't work with Java 6, right?

@benedekfazekas
Copy link
Member

It should work with a workaround, see our discussion here #247

@bbatsov
Copy link
Member

bbatsov commented Jan 4, 2016

Yeah, I remembered this. Guess it's not important at all, as at the end of the day I create the jars under JDK8.

@bbatsov
Copy link
Member

bbatsov commented Jan 4, 2016

Probably this should be backported as well 6b7fcb8

Add source file path, relative path, line and column number to
compiler errors. Trim the message to a simple description.
bbatsov added a commit that referenced this pull request Jan 5, 2016
Return cider-test result keys more specifically
@bbatsov bbatsov merged commit 0fc5fa7 into clojure-emacs:v0.10 Jan 5, 2016
@bbatsov
Copy link
Member

bbatsov commented Jan 5, 2016

Hmm, I've got one failing test in the branch:

FAIL in (test-cause-data-pretty-printing) (stacktrace_test.clj:110)
compilation errors
expected: (re-find #"Error compiling: .* Unable to resolve symbol: not-defined in this context" (:message (first causes3)))
  actual: (not (re-find #"Error compiling: .* Unable to resolve symbol: not-defined in this context" "Unable to resolve symbol: not-defined in this context"))

However, I cut the release, as I didn't have time to investigate - hopefully it's nothing major.

@bbatsov
Copy link
Member

bbatsov commented Jan 5, 2016

Damn, just looked at the build - everything is failing.

@jeffvalk
Copy link
Contributor

jeffvalk commented Jan 5, 2016

@bbatsov This commit broke a test. I didn't notice that until just now because @cichli had already fixed the test in fbbd303. If you pull in that commit, things should be good.

@cap10morgan
Copy link
Author

I opened a PR with that commit on the v0.10 branch: #283

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants