stty: High Level GNU Testsuite Issue Tracker

[ChrisDryden]

Given that getting all of the stty tests to run on the integration test suite requires a overarching strategy on how the support running the test suite on Github Actions.

I did a bunch of investigating across open source projects to see how others have dealt with this issue and came across a "hack" that supposedly is all we need to be able to support running the stty tests. #9336

There are still a few underlying compatibility issues in the current stty implementation that are causing issues with the GNU test suite to get them to pass but I was able to get a draft with the tests passing locally for the following issues:

• The Baud value parsing for configuration values is able to parse a wide range of inputs that currently is not supported stty: Fixing baud parsing compatibility #9339
• There is no ability to parse MAC addresses when exporting the state and then re-importing the state
• The COLUMN env variable is not being parsed and used when printing the output

The other problem that we have is that the existing rust unit test infrastructure is that we are not able to run unit tests for this command because we have "ignore" flags set because cargo test does not run on a tty. In the long run a plan to add support for this should be added to test correctly.

I will try and split up the fixes to each of these sub problems into separate CR's.

[ChrisDryden]

The integration suite was run on the TTY config change and the tests are now running instead of being skipped! #9336

[ChrisDryden]

There does seem to be multiple issues with the print state currently, it appears that somehow the GNU implementation is able to tell which flags are used on which platforms and sets the ones that aren't to 0 and only reads the ones that are used. Right now on some platforms certain control flags are being printed with different values from the GNU version and that needs to be addressed in the long term. This doesn't cause failures in the GNU test suite but its something to keep in mind

[ChrisDryden]

The fixed baud value parser was implemented in this PR: #9454
The ability to restore a saved state and integration tests for it are implemented in: #9480

There are three open PR's that address the three other open issues:

• being able to parse hex and oct row col inputs for tests/stty/stty-row-col: Stty: implemented hex and octal parsing for rows and columns #9516
• recognizing the env variable COLUMNS for outputting to a terminal for tests/stty/stty stty: columns env support and integration testing #9490
• Setting the cfsetispeed alongside the cfsetospeed for tests/stty/bad-speed Stty: Implemented input and output baud rate setting for stty #9517

The approach I'll be taking for running this in the github runners is in this PR: #9336

I'm very excited, this can move 5 tests at the same time from skipped to passing 🥳