Open galibzon opened 9 months ago
Note that this appears to pass if using a clean build: https://jenkins.build.o3de.org/blue/organizations/jenkins/o3de-extras/detail/development/123/pipeline, however the subsequent incremental runs fails again.
We may want to consider having Jenkins set this error as a non-blocking, rather than failing the AR run completely. Here's an example of how that's implemented in Linux: https://github.com/o3de/o3de/pull/8832
Describe the bug The
o3de-extras
jenkins jobs fail randomly during theasset_profile
step. The failure is always the same, but it occurs randomly:Some examples of jenkins jobs that have failed like that: https://jenkins.build.o3de.org/blue/organizations/jenkins/o3de-extras/detail/development/111/pipeline https://jenkins.build.o3de.org/blue/organizations/jenkins/o3de-extras/detail/PR-664/8/pipeline
Assets required N/A
Steps to reproduce Run a jenkins a job under the o3de-extras repo.
Expected behavior
asset_profile
should passActual behavior
asset_profile
fails randomly, sometimes requiring to re-run the job at least 3 times for around 9hrs+ of waste compute time.Screenshots/Video N/A
Found in Branch latest development of o3de-extras + o3de
Desktop/Device (please complete the following information):
Additional context Add any other context about the problem here.