-
Notifications
You must be signed in to change notification settings - Fork 5
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
only two characters of each line displayed #58
Comments
Very weird. Can you try adding # test_helper.exs
Mneme.start(action: :reject) |
Also, could download and run the example tour locally and see whether things work as expected or whether the same issue occurs?
|
It seems to work fine :)
The issue doesn't occur anymore, and I get this instead: It may be relevant to share my ExUnit.configure(
formatters:
[ExUnit.CLIFormatter, ExUnitNotifier]
)
ExUnit.start(
timeout: 120_000,
assert_receive_timeout: 1000,
exclude: [],
# only show log for failed tests (Can be overridden for individual tests via `@tag capture_log: false`)
capture_log: true
)
Mneme.start() |
Mneme wraps the default ExUnit formatter; it's possible that there's some compatibility issue with # please comment out the existing ExUnit.configure/start/etc.
ExUnit.start()
Mneme.start() This will help me determine whether it's a configuration/compatibility issue or a terminal compatibility issue. Are you using the built-in MacOS Terminal.app? |
Same result unfortunately.
I was using iTerm, but tried that instead, and also using |
Thank you for the extra info! At this point, I really need to be able to replicate this locally in order to figure out what's going on. Some things that would help:
|
While preparing the below answer for you I tried something different and found the apparent culprit: https://hexdocs.pm/mix_test_watch/ Using the below project, if I run This is actually on an open-source project, so if you're willing to jump through some hoops to run it (i.e. having The tool versions used are at https://github.com/bonfire-networks/bonfire-app/blob/main/.tool-versions |
Here's what I see:
Running on zsh, let me what other details you may need.
The text was updated successfully, but these errors were encountered: