-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[APM] e2e are failing when running them locally with some snapshot
#65422
Comments
Pinging @elastic/apm-ui (Team:apm) |
Try deleting the snapshots.js file. I think something could have happened to that during the NP migration. |
Do you mean What did I do?
|
What happens if you create it as an empty file: module.exports = {}; |
That's interesting, I actually created the file with the empty content as suggested, and after running the scripts, the file got changed as below: diff --git a/x-pack/plugins/apm/e2e/cypress/integration/snapshots.js b/x-pack/plugins/apm/e2e/cypress/integration/snapshots.js
index dc164f3e..07782866 100644
--- a/x-pack/plugins/apm/e2e/cypress/integration/snapshots.js
+++ b/x-pack/plugins/apm/e2e/cypress/integration/snapshots.js
@@ -1 +1,10 @@
-module.exports = { }
\ No newline at end of file
+module.exports = {
+ "__version": "4.2.0",
+ "APM": {
+ "Transaction duration charts": {
+ "1": "350 ms",
+ "2": "175 ms",
+ "3": "0 ms"
+ }
+ }
+} It works with the retry tweak after 6 tries :) How did I run the e2e?
Do you need any further details? |
Great, that's also what I'd expect (it should recreate the snapshot).
Ouch. Do you know why it failed the first 5? Is it still because we can't reliably determine when Kibana is up and running?
|
That's already reported in #61942 A bit of context, I've already tried running Kibana in prod mode instead of dev a few times and did not work: That's the reason I enabled the retry tweak in #61803 and it does work, the good thing, what people run locally with the e2e it's also validated in the CI, therefore no running discrepancies in the CI and locally. |
I think we should find out why the retries are necessary so we can get rid of them. |
I'll close this done since it's now solved in #66373 |
Kibana version:
master branch
Elasticsearch version:
master branch
Server OS version:
macosx
10.15.4
Browser version:
Cypress e2e UI
Browser OS version:
N/A
Original install method (e.g. download page, yum, from source, etc.):
From source
node --version
- v10.19.0nvm --version
- 0.34.0Description of the problem including expected versus actual behavior:
e2e tests are failing with
Steps to reproduce:
Run all the below steps from scratch:
Since there is an issue when running from scratch, see #61942
I recommend to change the
x-pack/plugins/apm/e2e/run-e2e.sh
with something like the below diff:Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Describe the feature:
The text was updated successfully, but these errors were encountered: