Flaky subtest of web-platform-tests/html/dom/interfaces.html (XMLDocument#all)

Not reproducible Issue #12047069

Details

Author
Philip J.
Created
May 17, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

This came up in https://github.com/w3c/web-platform-tests/pull/5942 on Edge 14, but has also been confirmed in Edge 15.

At wpt commit 7005b60351c6bd8dc6be07e2a290f5df3909f134, http://w3c-test.org/html/dom/interfaces.html does not produce reliable results.

The subtest that sometimes fails and sometimes passes is 'Document interface: document.implementation.createDocument(null, "", null) must inherit property “all” with the proper type (75)'

The test itself is probably invalid, but when it fails it’s here:
https://github.com/w3c/web-platform-tests/blob/7005b60351c6bd8dc6be07e2a290f5df3909f134/resources/idlharness.js#L636

It seems like the "property = obj[member.name]" bit in “IdlInterface.prototype.test_interface_of” doesn’t always result in the same value.

An attempt to minify the test in https://github.com/w3c/web-platform-tests/pull/5963 made the problem go away.

In https://github.com/w3c/web-platform-tests/pull/5942#issuecomment-301896566 gsnedders has guesses about the cause.

Attachments

0 attachments

    Comments and activity

    • I’ve been unable to reproduce this in Edge 15 at all; in Edge 14 it’s completely stable with the devtools open which suggests my hypothesis about it being a JIT issue is accurate.

      I’m fairly certain property = obj[member.name] is consistent; it’s when it then calls a function, binding that property to value as an argument and then doing typeof value it’s inconsistent, sometimes returning “undefined” and sometimes "object". Given the magic around HTMLAllCollection, this isn’t the most surprising of bugs. :)

    • OK, no, finally got it to repro. After many, many, many reloads. Can’t really tell if having devtools open makes any difference because it’s so rare.

    • Microsoft Edge Team

      Changed Assigned To to “Brian T.”

      Changed Assigned To from “Brian T.” to “Paul L.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Paul L.” to “Sandeep A.”

      Changed Assigned To from “Sandeep A.” to “Louis L.”

      Changed Assigned To from “Louis L.” to “Thomas M.”

    • Hey Geoffrey/Philip it looks like that file no longer exists there - I’ve told Thomas (the dev currently looking at this bug) to look at this one since zcorpan and others have been working on it and it has the same name: http://w3c-test.org/dom/interfaces.html please let us know if this isn’t correct.

    • Pretty sure it’s http://w3c-test.org/html/dom/interfaces.https.html — per my comment above, it seemed to be about JIT compilation of idlharness.js when dealing with HTMLAllCollection, and the DOM idlharness.js test doesn’t touch HTMLAllCollection.

    • Microsoft Edge Team

      Changed Assigned To from “Thomas M.” to “Greg W.”

      Changed Status from “Confirmed” to “Not reproducible”

    • Hello,

      Thank you for providing this information about the issue. After thorough testing, we are unable to reproduce this problem in Edge with the information at hand. If you can repro the problem, please use the Feedback Hub to collect more information. https://www.microsoft.com/en-us/store/p/feedback-hub/9nblggh4r32n

      1. Open the Feedback Hub app on your device 
      2. Click on the “Feedback” tab 
      3. Click on the " Add new feedback" button 
      4. Click "Problem", fill in the title/details and select “Microsoft Edge” as the category and the appropriate sub-category 
      5. Under "Recreate the problem", press “Start capture” 
      6. Once the capture has started, run through the steps required to reproduce your issue 
      7. Click “Stop capture” back in the Feedback Hub app 
      8. Attach a screenshot of the behavior 
      9. Press “Submit” 

      This will provide us with a trace we can use to debug the issue further. Once you’ve submitted this, please paste a link to the newly created Feedback Hub issue in this bug so that we can link the two together and continue to investigate.

      Best Wishes,
      The MS Edge Team

    You need to sign in to your Microsoft account to add a comment.

    Sign in