Skip to content

Commit

Permalink
Change wehe e2e tests to use the amazon replay instead of applemusic (#…
Browse files Browse the repository at this point in the history
…1066)

* Changes wehe e2e test from using applemusic to amazon

I noticed that many e2e tests in sandbox were timing out at 50s from the
timeout setting configured for the wehe_client script. But in production the
tests were completing in around 10 or 15 seconds.

I turned on debug logging for wehe-cmdline.jar and noticed that for some odd
reason there was a 20s delay when sending packet number 13 our of 15. And this
happens twice during the test, making the test very long.

Looking at the wehe-cmdline repository, I noticed that a new version was
released just a couple months ago which updated all the replay files.
Inspecting the applemusic replay file (which is JSON), I noticed that the
timestamp field of the 13th packet in the array has a value of ~20s, which I
think explain why there is always a 20s delay when sending the 13th packet.

I looked through the available replay files looking for one where the final
packet's timestamp value was low, and it turns out that the amazon test fit
that bill. This should cause wehe e2e tests to complete much more quickly.

* Reduces the script-exporter timeout for wehe back to 50s
  • Loading branch information
nkinkade authored Oct 25, 2024
1 parent ef397e3 commit 9b6ee7b
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions config/federation/script-exporter/script_exporter.yml
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,8 @@ scripts:
script: >
EXPERIMENT=wehe cache_exit_code.sh 600
monitoring-token -machine=${TARGET} -service=wehe/replay --
wehe-client.sh -n applemusic -t wehe-cmdline/res/ -c
timeout: 55
wehe-client.sh -n amazon -t wehe-cmdline/res/ -c
timeout: 50
- name: 'ndt7_client'
script: >
EXPERIMENT=ndt7 cache_exit_code.sh 3600
Expand Down

0 comments on commit 9b6ee7b

Please sign in to comment.