Skip to content
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

[iOS only] Negative duration for some test executions #984

Open
msd117c opened this issue Nov 20, 2024 · 2 comments
Open

[iOS only] Negative duration for some test executions #984

msd117c opened this issue Nov 20, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@msd117c
Copy link

msd117c commented Nov 20, 2024

Describe the bug
For a given (iOS) test, the test runner is writing a (huge) negative duration in the influxDB bucket we use for Marathon.
Captura de pantalla 2024-11-20 a las 15 05 14
These durations belong to the same test.

To Reproduce
It is hard to reproduce the issue because the data comes from executions during development and it is not the only one reporting data for that time window, making it harder to locate the logs.

Expected behavior
I would expect a positive test duration or 0 if something unexpected happened, though that would introduce noise in the metrics (less than actual noise with that negative value though).

Logs and reports
I can't access the logs but the test was reported as not successful to the influxDB instance (so I guess we can expect a greater than 0 duration).

Devices (please complete the following information):

  • Device: iPhone 16
  • OS: iOS 18

Additional context
I will try to manually reproduce the issue to have access to the logs. This only happened with an iOS setup (afaik Android never had this issue).

@msd117c msd117c added the bug Something isn't working label Nov 20, 2024
@Malinskiy
Copy link
Member

The huge negative value is a negative unix epoch in milliseconds. duration = end - begin, so a huge negative value means that some specific test didn't report an end value.
Without a reproducer, it's hard to debug such an issue. I'm happy to review a PR with a fix as well if you can't provide a reproducer.

Thanks!

@msd117c
Copy link
Author

msd117c commented Nov 21, 2024

@Malinskiy I opened a draft PR trying to address the issue here. Let me know if you think that could solve the issue. I will try to reproduce the issue locally when possible and try the branch build to compare.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants