Skip to content

Conversation

@sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Dec 21, 2022

These alarms/signals will now fire if when waiting on a lock (i.e. they don't depend on the event loops running).

Fixes: #12415

@sbc100 sbc100 requested review from kleisauke and kripken December 21, 2022 21:09
@sbc100 sbc100 force-pushed the getitimer branch 9 times, most recently from b2984c9 to 6c3ee4e Compare December 22, 2022 18:34
@sbc100 sbc100 enabled auto-merge (squash) December 22, 2022 20:10
@sbc100 sbc100 changed the title Remove custom alarm impl in favor of lower level itimer syscalls Remove custom alarm impl in favor of lower level itimer API Dec 22, 2022
@sbc100
Copy link
Collaborator Author

sbc100 commented Jan 5, 2023

gentle ping..

@sbc100 sbc100 force-pushed the getitimer branch 2 times, most recently from b2f724c to ab7ae19 Compare January 9, 2023 23:45
@sbc100 sbc100 force-pushed the getitimer branch 2 times, most recently from ddd211c to d23c1c8 Compare January 10, 2023 10:54
@sbc100 sbc100 force-pushed the getitimer branch 3 times, most recently from 597932d to 4b16914 Compare January 12, 2023 16:50
Copy link
Member

@kripken kripken left a comment

Choose a reason for hiding this comment

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

lgtm aside from testing questions.

Sorry for the long review here!

These alarms/signals will now fire if when waiting on a lock (i.e. they
don't depend on the event loops running).

Fixes: #12415
@sbc100
Copy link
Collaborator Author

sbc100 commented Jan 12, 2023

We can adjust ERROR_MARGIN if we start seeing this test fail in CI

@sbc100 sbc100 disabled auto-merge January 12, 2023 19:45
@sbc100 sbc100 merged commit aef3f83 into main Jan 12, 2023
@sbc100 sbc100 deleted the getitimer branch January 12, 2023 19:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

nanosleep autoconf check hangs forever

3 participants