-
Notifications
You must be signed in to change notification settings - Fork 48
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
Update latest WPT Manifest for go_test #6958
Update latest WPT Manifest for go_test #6958
Conversation
Head branch was pushed to by a user without write access
4b0ed47
to
4c390b0
Compare
Head branch was pushed to by a user without write access
4c390b0
to
9d901e8
Compare
Head branch was pushed to by a user without write access
9d901e8
to
b7b97c4
Compare
Head branch was pushed to by a user without write access
b7b97c4
to
de13c03
Compare
Head branch was pushed to by a user without write access
de13c03
to
a08a069
Compare
Head branch was pushed to by a user without write access
a08a069
to
76e7b14
Compare
This is failing because of this PR: web-platform-tests/wpt#49342. Will need to remove/rename references |
@KyleJu Do you have an idea of what is going on? For example, I tried to modify the META.yml files and it still cannot find the test in the manifest. For example. Given this file: wpt-metadata/performance-timeline/META.yml Lines 1 to 8 in 3288dc7
I tried to change the test line value to:
But I see it there: |
@jcscottiii with my limited knowledge in how testharness.js work, I believe that web-platform-tests/wpt#49342 introduced a new type of scope keywords, which is not the list of filename suffixes that wpt.fyi generates. It broke the manifest file generation. Let's remove these renamed tests for now and merge this PR. It needs a fix on the manifest generation. |
Head branch was pushed to by a user without write access
34b4890
to
c17b9a6
Compare
@Ms2ger I saw you commented on that PR. Would you happen to know how we could fix this problem? |
Not sure, unless this is the same issue @jgraham hit (and that I mentioned at the end of the meeting), where you need to regenerate the manifest from scratch? |
This automated pull request updates the MANIFEST.json file to the latest WPT manifest daily. GitHub checks run against this manifest. If checks fail in this PR, the failing metadata should be either renamed or deleted according to the WPT repository.