-
Notifications
You must be signed in to change notification settings - Fork 423
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
No files found
(OTP 26? MacOS?)
#1080
Comments
I observed the same behaviour with Elixir 1.14.4 and OTP 25 . The |
This seems weird, and while this might very well have to do with OTP 26, I can not reproduce it on my machine. Let's gather more data about how many people have this problem. |
Checking in: Is this still a problem with newer versions of Erlang/Elixir/Credo? |
Yes, still same issue |
I'm also experiencing this issue with Mac OS Sonoma and OTP 26. But I'm not able to reproduce it consistently, it only happens sometimes. I'm also experiencing this weird behavior when compiling anything with elixir + erlang OTP26, I keep getting these pop-up windows from the OS with a message that looks like: It seems that credo fails with the "Some source files were not parsed" error when I get these pop-ups. |
Precheck
Environment
mix credo -v
): 1.7.0elixir -v
): 1.14.5 - OTP 26What were you trying to do?
Basically, just run
mix credo
ormix credo diff master
locally.Expected outcome
Normal credo run with the warnings, alerts, etc.
Actual outcome
When we run it locally, we always get
info: Some source files were not parsed in the time allotted:
Then it lists all files and messages:
No files found!
The weird part is that it runs flawlessly in the CI pipeline (GH action using Ubuntu 20.04 and the same Elixir/OTP), which points to be related to either multi-core system or OSX itself, alongside OTP 26. It only started after we updated to OTP 26.
We tried to remove some checks and increase the timeout with no success.
Please let me know if I'm missing any details.
The text was updated successfully, but these errors were encountered: