-
Notifications
You must be signed in to change notification settings - Fork 29
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
Segment Validation test never completes #602
Comments
probably related to #604 |
We merged #611 can you please check if this fixes your problem |
https://beta.conformance.dashif.org is currently unavailable (503). Issue still present with https://conformance.dashif.org/ |
Still present on https://beta.conformance.dashif.org/. Probably related to processes that are not terminating, @Phencys is already addressing these issues in refactor phase. To be evaluated against version 2.1.0 and 2.2.0 |
There are quite a few bugst that could be related to this, and some of them are probably due to issues with the segment validator. The pull request above sets a maximum running time for the segment validator, and exists upon various health issues as described in it. On top of this, there are also some known-issues in the current Front-End, that are hard to pin down to a specific reason. These issues should however not be applicable anymore once the new UI is released |
My latest batch of commits on the SegmentValidator should fix this. |
Fixed on https://staging.conformance.dashif.org/Conformance-Frontend-JCCP/#home , output is now generated |
Currently the Segment Validation test never completes when running it via https://conformance.dashif.org/
For example, using:
https://dash.akamaized.net/WAVE/vectors/cfhd_sets/15_30_60/t1/2022-10-17/stream.mpd
With additional tests:
Segment Validation
CMAF
CTA WAVE
The following is shown and remains this way indefinitely (hours later):
The text was updated successfully, but these errors were encountered: