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

Segment Validation test never completes #602

Closed
nicholas-fr opened this issue Nov 2, 2022 · 7 comments
Closed

Segment Validation test never completes #602

nicholas-fr opened this issue Nov 2, 2022 · 7 comments
Assignees
Milestone

Comments

@nicholas-fr
Copy link

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):
image

@dsilhavy dsilhavy added this to the v2.0.0 milestone Nov 9, 2022
@dsilhavy
Copy link
Contributor

dsilhavy commented Nov 9, 2022

probably related to #604

@dsilhavy
Copy link
Contributor

dsilhavy commented Nov 9, 2022

We merged #611 can you please check if this fixes your problem

@nicholas-fr
Copy link
Author

https://beta.conformance.dashif.org is currently unavailable (503).

Issue still present with https://conformance.dashif.org/

@dsilhavy dsilhavy modified the milestones: v2.0.0, v2.1.0 Nov 11, 2022
@dsilhavy
Copy link
Contributor

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

@Phencys Phencys self-assigned this Nov 18, 2022
@Phencys
Copy link
Collaborator

Phencys commented Nov 18, 2022

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

@rbouqueau
Copy link
Collaborator

My latest batch of commits on the SegmentValidator should fix this.

@dsilhavy dsilhavy modified the milestones: v2.1.0, v2.2.0 Dec 6, 2022
@dsilhavy
Copy link
Contributor

Fixed on https://staging.conformance.dashif.org/Conformance-Frontend-JCCP/#home , output is now generated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants