-
Notifications
You must be signed in to change notification settings - Fork 95
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
Pragmatic displayed impl #445
Pragmatic displayed impl #445
Conversation
…ity` and `display` attributes
Looks like the tests passed! 🎉 |
@daveyarwood: As for testing locally, I've not seen that error yet myself.
|
Aha! That was the issue. I was running an old version of Babashka, 0.4.4. I've updated to the latest and now the tests are running. 👍 |
@lread Maybe specify |
Most of the tests passed, but some of them (looks to be tests related to window size/position) failed. I'm attaching the log here in case it's helpful. |
Thanks @daveyarwood! Can you run |
|
That all looks good to me @daveyarwood. Not sure about your window size/positioning failures. |
Re-running the failed job. It seems to be not unusual for a job or two to sometimes fail on GitHub Actions. If they still fail after a re-run then we likely have an issue to deal with (which is not the case here I am pretty certain!) |
@daveyarwood, I raised an issue for your local failure #447 |
We have learned that displayed-ness is more complex than we had originally imagined. It requires more research and maybe more hammock time. Effectively rolls back PR clj-commons#445 for issue clj-commons#444.
This hopefully fixes #444.
Unfortunately, I wasn't able to run the tests due to a variety of technical issues.
I don't have Docker on this machine, so I attempted running
bb test all
directly.I got an error about the Cognitect test runner library missing
:sha
from the coordinate, which I've read can be caused by using an older version of the Clojure CLI. But then I updated to the latest Clojure CLI version and the problem persisted. I was able to work around that by adding an additional:sha
entry for all deps that have a:git/sha
entry.Having worked that out, I ran
bb test all
and got this error which I don't understand:I hope it's OK if I submit this PR anyway. If you have CI hooked up to run the tests, or if a volunteer could check out my branch and run them, that would be helpful! If the tests aren't passing, I can try to dig deeper.