This issue can be found on Bionic 4.15 AWS as well.
I tried to reproduce this manually, however with instance c5.large (which is failing with this case on B-AWS-4.15), I can't reproduce this with 4.15.0-1065-aws / 4.15.0-1066-aws by just running this clock_nanosleep02 test case.
This issue can be found on Bionic 4.15 AWS as well.
I tried to reproduce this manually, however with instance c5.large (which is failing with this case on B-AWS-4.15), I can't reproduce this with 4.15.0-1065-aws / 4.15.0-1066-aws by just running this clock_nanosleep02 test case.