-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop CMake out of source tests running on 16.04 #5233
Stop CMake out of source tests running on 16.04 #5233
Conversation
Running the out of source CMake test on Ubuntu 16.04 using more than one processor (as the CI does) can create a race condition whereby the build fails to see a generated file, despite that file actually having been generated. This problem appears to go away with 18.04 or newer, so make the out of source tests not supported on Ubuntu 16.04 Signed-off-by: Paul Elliott <paul.elliott@arm.com>
@@ -2676,6 +2676,36 @@ component_test_valgrind () { | |||
fi | |||
} | |||
|
|||
support_test_cmake_out_of_source () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems not to be called anywhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code in all.sh
automatically calls support_$name
if it exists when deciding whether to call component_$name
.
@@ -0,0 +1,4 @@ | |||
Bugfix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure a changelog entry is warranted for a CI fix
The point of this patch was to fix CI on #5155 so it's been included into that PR. |
Description
Running the out of source CMake test on Ubuntu 16.04 using more than one processor (as the CI does) can create a race condition whereby the build fails to see a generated file, despite that file actually having been generated. This problem appears to go away with 18.04 or newer, so make the out of source tests not supported on Ubuntu 16.04
This is our mitigation for #5223 - Given 16.04 is already out of support, it seemed the simplest option rather than trying to chase down the race condition.
Status
READY
Requires Backporting
NO
Migrations
NO
Todos
Steps to test or reproduce
CMake out of source tests should run clean on CI 100%