We had a recent failure on a beats PR: elastic/beats#26749, however when we investigated further it was determined that the actual code that was altered (basically some output being printed to screen) was not being seen. This led us to look into the test logs to verify that the code submitted in the PR was not the actual code being tested.

Next steps:

• Determine if the gcp bucket contains a built image for that particular PR
• Verify that the contents within that image match the code that was submitted in the PR
• Verify that e2e-testing references the correct image when executing the test suite