Fork workaround

[TingDaoK]

Issue #, if available:

• We don't support fork and we probably will not support fork any time soon
• As the current user, if you have to use fork, provide some caveat and a test as an example how you can make it work.
• Updated submodules to bring CrossProcess lock -- don't unlock, just close fd aws-c-common#1192

aws-c-auth         v0.8.6 -> v0.8.7
aws-c-common       v0.12.0 -> v0.12.1
aws-c-http         v0.9.3 -> v0.9.5
aws-c-s3           v0.7.12 -> v0.7.13
aws-lc             v1.48.1 -> v1.48.5

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[graebm]

exit() just raises an exception (stackoverflow)

and didn't you say exceptions from fork handlers are ignored?

maybe fail harder with os._exit(-1) ... though that wouldn't flush any buffers so we might not see the error. Maybe flush stdout and stderr and then exit hard?

[TingDaoK]

https://github.com/awslabs/aws-crt-python/actions/runs/13904462279/job/38904049353
looks like it flushes the output and makes the exception raised for unittest
but the process still hangs...

[graebm]

looking good. Just some questions about the arm64 runners

[graebm]

🤩

[graebm]

Yikes, but what's up with this in the logs?

Running: SetupCrossCICrtEnvironment
Tests not needed for project. Skipping setting test environment variables
Finished: SetupCrossCICrtEnvironment

Does aws-crt-builder think this is a cross-compile?

[TingDaoK]

by default, builder doesn't run tests on arm https://github.com/awslabs/aws-crt-builder/blob/main/builder/core/data.py#L318-L329

But, we run our tests via the build action in AWSCrtPython.

So, it still runs the action, but mqtt stuff was skipped.