-
Notifications
You must be signed in to change notification settings - Fork 564
Fix panic on RUST_LOG=<filter> during tests #1154
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
It doesn't seem like this is related to |
…om/risc0/risc0 into cardosaum/hotfix/test-log-features
@@ -14,7 +14,8 @@ tracing = { version = "0.1", features = ["log"] } | |||
tracing-subscriber = { version = "0.3", features = ["env-filter"] } | |||
|
|||
[dev-dependencies] | |||
test-log = { version = "0.2", default-features = false, features = ["trace"] } | |||
env_logger = "0.10" | |||
test-log = { version = "0.2", features = ["trace", "log"] } |
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.
The default already contains log
test-log = { version = "0.2", features = ["trace", "log"] } | |
test-log = { version = "0.2", features = ["trace"] } |
@@ -8,8 +8,9 @@ homepage = { workspace = true } | |||
repository = { workspace = true } | |||
|
|||
[dev-dependencies] | |||
env_logger = "0.10" |
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.
why is both env_logger and tracing subscriber a part of this? I thought that we only needed tracing
and tracing-subscriber
I found the underlying issue that some of us have run into, it's likely because we were using an older version of |
I'm opening this PR to address a bug report encountered when running a test with
RUST_LOG=info
. The bug causes a panic due to a regex parse error related to Unicode-aware case insensitivity matching - exactly like the issue described in tracing-subscriber. I have tried to fix it by specifyingtest-log
feature to bothlog
andtrace
in theCargo.toml
file.I can't validate the fix on my machine yet, since this seems to arise only when
-F cuda
is passed, and I don't have the required hardware to test it.