-
Notifications
You must be signed in to change notification settings - Fork 72
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
[BUG] Failing utils spec tests #1880
Comments
Can you provide DEBUG output? There was a recent PR we pushed and merged because it was passing spec tests in the github runners but found that it was likely passing using cached data as they were now failing after we destroyed and recreated new runners after the github repo URL change. I want to verify if this is one of the causes as a fix is underway with a revert of the contants.cr file that was a cause of the found issue. |
I already run that test as debug (configured log level in config.yaml). Or I need to run it in different way? FYI: Spec tests also failed for 5G RAN (ran_spec) and 5G core (core_spec) but I didn't have time to create tickets for them. Maybe it will be same issue as with this one. |
Yes, we're working on the 5g tests too.
…On Wed, 7 Feb 2024 at 13:29, Tomáš Macák ***@***.***> wrote:
I already run that test as debug (configured log level in config.yaml). Or
I need to run it in different way?
FYI: Spec tests also failed for 5G RAN (ran_spec) and 5G core (core_spec)
but I didn't have time to create tickets for them. Maybe it will be same
issue as with this one.
—
Reply to this email directly, view it on GitHub
<#1880 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADNPFFAC6MNKVYZOVIJ623TYSPI2XAVCNFSM6AAAAABC54CWRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZSG4ZDONJSGE>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
@macaktom The spec tests were only running correctly when LOG_LEVEL=info mode was set because of the below commands:
When not running in 'info' mode those commands didn't execute at all. Which was causing the test failure. This is now fixed by this commit: 3f138cc |
…_1880 Fix bug with utils spec lfn-cnti#1880
@denverwilliams But fixing this by switching LOG_LEVEL to 'info' is more like a workaround than a real solution of this issue. I think it has to be possible to execute spec tests with different log level and have green results. |
Oh, I was just alerted that a ticket has already been created for that issue -> #1495 |
@horecoli This fix wasn't simply switching 'LOG_LEVEL to 'info'. The fix here makes it so spec tests will now execute regardless of the log level. See: 3f138cc#diff-e46af2840c1b39bfc5a893dfe850e3748f90f0339f72436b344a789747e9646cR194 The spec will now execute tasks regardless of the log level and assign the output to a variable. |
Describe the bug
Utils spec tests are failing, when running them (individually or via command crystal spec).
To Reproduce
crystal spec
or
crystal spec ./spec/utils/utils_spec.cr
Expected behavior
A clear and concise description of what you expected to happen.
Device (please complete the following information):
How will this be tested? aka Acceptance Criteria (optional)
For verification successfully running
crystal spec ./spec/utils/utils_spec.cr
should be enough.Additional context
The text was updated successfully, but these errors were encountered: