Skip to content

Conversation

@aescolar
Copy link
Member

@aescolar aescolar commented May 6, 2024

#69705
Introduced a regression in main in which tests/subsys/logging/log_timestamp started failing.

Let's revert the PR. It can be submitted after with the issue fixed.

Fixes #72344

aescolar added 4 commits May 6, 2024 11:00
…tatic"

This reverts commit 7c03e5d.

zephyrproject-rtos#69705
Introduced a regression in main in which
tests/subsys/logging/log_timestamp
started failing. (See
zephyrproject-rtos#72344
for more info).
Let's revert the PR. It can be submitted after with the issue
fixed.

Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
This reverts commit 8eabf80.

zephyrproject-rtos#69705
Introduced a regression in main in which
tests/subsys/logging/log_timestamp
started failing. (See
zephyrproject-rtos#72344
for more info).
Let's revert the PR. It can be submitted after with the issue
fixed.

Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
…sec"

This reverts commit fd8ca83.

zephyrproject-rtos#69705
Introduced a regression in main in which
tests/subsys/logging/log_timestamp
started failing. (See
zephyrproject-rtos#72344
for more info).
Let's revert the PR. It can be submitted after with the issue
fixed.

Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
… at runtime"

This reverts commit d82f4a9.

zephyrproject-rtos#69705
Introduced a regression in main in which
tests/subsys/logging/log_timestamp
started failing. (See
zephyrproject-rtos#72344
for more info).
Let's revert the PR. It can be submitted after with the issue
fixed.

Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
@aescolar aescolar added the Hotfix Fix for issues blocking development, i.e. upstream CI issues, tests failing in upstream CI , etc. label May 6, 2024
@aescolar aescolar requested a review from jhedberg May 6, 2024 09:05
@jhedberg
Copy link
Member

jhedberg commented May 6, 2024

@aescolar did you consider reverting just the one commit that @fabiobaltieri identified as the culprit? I was able to verify that simply reverting it also fixes the issue.

@aescolar
Copy link
Member Author

aescolar commented May 6, 2024

@aescolar did you consider reverting just the one commit that @fabiobaltieri identified as the culprit? I was able to verify that simply reverting it also fixes the issue.

I did, but I was concerned that reverting only that one I would leave something else broken. It just seemed the cleaner and safer thing to do was revert the whole PR; And once the author identifies the cause behind the issue the PR can be resubmitted with it fixed.

Copy link
Member

@jhedberg jhedberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aescolar did you consider reverting just the one commit that @fabiobaltieri identified as the culprit? I was able to verify that simply reverting it also fixes the issue.

I did, but I was concerned that reverting only that one I would leave something else broken. It just seemed the cleaner and safer thing to do was revert the whole PR; And once the author identifies the cause behind the issue the PR can be resubmitted with it fixed.

Ok. Fair enough.

@najumon1980
Copy link
Contributor

The regression is due to following reason:
sys_clock_hw_cycles_per_sec() used in log_core_init() which invoked during cstart (EARLY init) but HPET driver init is PRE_KERNEL_2. So the z_clock_hw_cycles_per_sec need to init with some default CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC (though it is not right) or ideally need to init z_clock_hw_cycles_per_sec run time during cstart (EARLY init).

@aescolar
Copy link
Member Author

aescolar commented May 6, 2024

Thanks @najumon1980 , does that mean you will be able to have a patch ready and passing soon? (in a matter of an hour or so). Otherwise we can just merge the revert and the original PR can be resubmitted without time pressure.

@najumon1980
Copy link
Contributor

let see I can provide a fix for this

@najumon1980
Copy link
Contributor

Provided following fix for the regression:
#72352

@aescolar
Copy link
Member Author

aescolar commented May 6, 2024

@najumon1980 The fix in #72352 does not seem too trivial. I'm quite inclined to merge this revert PR and unblock main.
If you don't say otherwise in the next few minutes I'll go ahead and merge this one.

@jhedberg jhedberg assigned jhedberg and unassigned andyross May 6, 2024
@jhedberg
Copy link
Member

jhedberg commented May 6, 2024

@najumon1980 The fix in #72352 does not seem too trivial. I'm quite inclined to merge this revert PR and unblock main. If you don't say otherwise in the next few minutes I'll go ahead and merge this one.

Yes, I think it's better to give the correct fix some more time for review, especially from @andyross, so let's merge the revert first.

@jhedberg jhedberg merged commit 0b87cb1 into zephyrproject-rtos:main May 6, 2024
@aescolar aescolar deleted the revert_69705 branch May 6, 2024 11:52
@andyross
Copy link
Contributor

andyross commented May 6, 2024

Random aside: this is the second time in a week we've seen core tests regress from PR's that didn't see them in CI? Is something getting skipped? Basically how was this not caught?

kartben added a commit to kartben/zephyr that referenced this pull request Dec 4, 2025
Last activity: 18 months ago (review)

Recent activities:

- review: Review on 'x86: ia32: linker: move bss/noinit sections after data
  section'
  zephyrproject-rtos#73044
  (2024-05-22T06:47:31Z)
- pr: kernel: timer: fixes for log_timestamp test case failer due to timer
  PR regression
  zephyrproject-rtos#72352
  (2024-05-06T10:47:53Z)
- review: Review on 'Revert 69705 and fix zephyrproject-rtos#72344'
  zephyrproject-rtos#72345
  (2024-05-06T09:53:31Z)

Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: Kernel area: Timer Timer Hotfix Fix for issues blocking development, i.e. upstream CI issues, tests failing in upstream CI , etc. platform: X86 x86 and x86-64

Projects

None yet

Development

Successfully merging this pull request may close these issues.

tests/subsys/logging/log_timestamp/ failing on qemu_x86[_64] on main

7 participants