Skip to content

Conversation

@ChrisDryden
Copy link
Collaborator

@ChrisDryden ChrisDryden commented Jan 10, 2026

There's a bunch of deviation from our implementation of Yes and Timeout and the gnu version and a long time ago, the gnu tests were patched so that for some tests it used the system yes and timeout. Now that we have proper signal handling implementations for our utilities we can revert this change and also see the gaps in our yes and timeout implementation and the gnu implementation by removing the overrides.

One key area that this will fail is the env-signal-handler test. It was relying on a bunch on non-implemented functionality in timeout that we need to implement for this test to pass. Mainly related to the non standard posix signals like RTMAX/RTMIN which is described here: #6218

@ChrisDryden
Copy link
Collaborator Author

Somehow every SELinux test failed here

@ChrisDryden
Copy link
Collaborator Author

I think I might take the approach of splitting this to first deploy the timeout and yes fixes and then make the change to revert the overrides.

@ChrisDryden
Copy link
Collaborator Author

I'm discovering how much the timeout utility has changed between now and the launch of 9.9, its quite different when it comes to signal handling

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.

1 participant