-
-
Notifications
You must be signed in to change notification settings - Fork 645
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
Fix some TravisCI issues #2059
Fix some TravisCI issues #2059
Conversation
test/cider-checks.el
Outdated
@@ -20,5 +20,9 @@ | |||
"\\`[^.].*\\.el\\'" t))) | |||
(dolist (file files) | |||
(checkdoc-file file)) | |||
(when (get-buffer "*Warnings*") | |||
(message "Failing due to checkdoc warnings...") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should dump the contents of the warnings buffer as well, otherwise it would be really hard for people to figure out what exactly is wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Warnings are already dumped line-by-line.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, OK. Thought they were only in the warnings buffer.
.travis.yml
Outdated
- EMACS_BINARY=emacs-25.1-travis MAKE_TEST=test | ||
- EMACS_BINARY=emacs-25.1-travis MAKE_TEST=test-bytecomp | ||
- EMACS_BINARY=emacs-25.1-travis MAKE_TEST=test-checks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should add 25.2 here as well, as it was recently released. Probably in a couple of releases we should drop support for Emacs 24 completely, but it seems too early now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅
test/cider-checks.el
Outdated
@@ -6,6 +6,9 @@ | |||
;; This assumes that all CIDER dependencies are already on the package dir | |||
;; (probably from running `cask install'). | |||
|
|||
;; NOTE: `checkdoc-file' is introduced in Emacs 25, so do not run this check with | |||
;; Emacs 24.x |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess you can also add a version check around the code itself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅
`directory-files-recursively` is [introduced in Emacs 25](https://github.com/purcell/package-lint/blob/4e4b34fc4f12ef2f7965fa959c5809aacdb6af63/package-lint.el#L186).
Most tests are passing, but there's an outstanding issue with byte-compilation tests for Emacs 24.x. |
Yeah, probably this is a bug, or something changed in Emacs 25. I guess you can simply replace |
Doing so causes a [byte-compiler error](https://travis-ci.org/clojure-emacs/cider/jobs/256287467#L1214) under Emacs 24. See: https://emacs.stackexchange.com/questions/34341/error-called-with-1-args-to-fill-0-format-fields/34350#34350
R.e. the |
`'nil` is fine in Emacs 25, but not in Emacs 24.
@bbatsov All tests pass. |
Quite interesting. Thanks for tackling all of this! Great work! |
P.S. It would be great if you can do all of this for |
@bbatsov would you be so kind and give some more consideration to the parameter order and double space "conventions"? Double space is unnatural and never used in other contexts. So you are bound to forget those and run into Same goes with order of arguments, wasting precious minutes of how to twist untwistable and forcing users to read pseudo-english is rather silly. As to the "conventions" argument, no-one seems to care about that in the Emacs proper. Pretty much every core file I tried has checkdoc issues much more serious than double spaces and order of arguments. Conventions which don't benefit the user or the programmer are silly and deserve to be disregarded anyways. These two are clearly of that sort. |
The order of arguments check is already turned off. The two-space rule is an Emacs convention that should be followed. We could turn it off by setting |
Why is that exactly? Even auto-fill doesn't respect it, why should you? Double space adds more inefficiencies because it happens more often. So, if you already disabled order of args you should consider disabling double space. |
We've maintained the codebase consistent in this regard since day 1 of the project and I see little point to change this now. It's not a big effort and you simply get used to this after a while. Most Elisp projects stick to this convention so it stopped bothering me after a while. I'm also using
I certainly don't want to inconvenience anyone, but I'm big on consistency in the codebase of a project. Can't really go back on this given how much code was written following this style - "fixing" this would create a diff that would obscure half the codebase and would create inconsistency with all of my other projects, that I don't want to introduce. |
auto-fill doesn't change spacing around punctuation, so I don't see how this is relevant. |
I was never happy with flycheck for emacs. Most of the libraries have checkdoc issues and that would mean constantly seeing those annoying highlights. Cider could be honorable exception where I can keep it active though, but ... it doesn't work in Cider project. I am getting
All other projects are fine. Any ideas?
Fair enough.
It used to be the case in previous emacses, when you could end up with a sentence starting a new para. But I think that was fixed in 25.x as I haven't encountered the issue for a while. |
I am unable to run test-bytecomp and test-checks on my local machine with emacs 25.2 and 26. I am getting cryptic stuff like:
and
Any pointers on this? |
The second failure looks like some missing require in the tests - |
Cannot reproduce on Emacs 25.1.1. Have you run |
(BTW, Yes, but cask doesn't pick the
I thought the problem was that
It turned out to be the load path. For some unclear reason when I ran
which is bizarre :( |
It's on the cask's side (cask/cask#335, cask/cask#295, cask/cask#260 seem to be relevant). I am not following all of that but |
@bbatsov originally raised this issue when discussing #2057.