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

CT: unable to find node from unique Trail id #605

Closed
pixelzoom opened this issue May 20, 2020 · 3 comments
Closed

CT: unable to find node from unique Trail id #605

pixelzoom opened this issue May 20, 2020 · 3 comments

Comments

@pixelzoom
Copy link
Contributor

pixelzoom commented May 20, 2020

scenery-phet has been failing CT since yesterday afternoon. Looks like changes to PDOMPointer made by @jessegreenberg for phetsims/scenery#1048

scenery-phet : interactive-description-fuzzBoard : unbuilt
https://bayes.colorado.edu/continuous-testing/ct-snapshots/1589932208678/scenery-phet/scenery-phet_en.html?continuousTest=%7B%22test%22%3A%5B%22scenery-phet%22%2C%22interactive-description-fuzzBoard%22%2C%22unbuilt%22%5D%2C%22snapshotName%22%3A%22snapshot-1589932208678%22%2C%22timestamp%22%3A1589937430844%7D&brand=phet&ea&fuzzBoard&supportsDescriptions&memoryLimit=1000
Query: brand=phet&ea&fuzzBoard&supportsDescriptions&memoryLimit=1000
Uncaught Error: Assertion failed: unable to find node from unique Trail id
Error: Assertion failed: unable to find node from unique Trail id
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1589932208678/assert/js/assert.js:22:13)
at Function.Trail.fromUniqueId (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1589932208678/scenery/js/util/Trail.js:957:17)
at PDOMPointer.updateTrail (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1589932208678/scenery/js/input/PDOMPointer.js:97:25)
at Input.dispatchA11yEvent (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1589932208678/scenery/js/input/Input.js:1024:38)
at Input.focusinAction.Action.phetioPlayback (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1589932208678/scenery/js/input/Input.js:560:14)
at Action.execute (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1589932208678/axon/js/Action.js:225:18)
at HTMLDivElement.<anonymous> (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1589932208678/scenery/js/input/Input.js:733:30)
at KeyboardFuzzer.chooseNextElement (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1589932208678/scenery/js/accessibility/KeyboardFuzzer.js:72:21)
at KeyboardFuzzer.fuzzBoardEvents (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1589932208678/scenery/js/accessibility/KeyboardFuzzer.js:161:10)
at https://bayes.colorado.edu/continuous-testing/ct-snapshots/1589932208678/joist/js/Sim.js:263:27
id: Bayes Chrome
Snapshot from 5/19/2020, 5:50:08 PM
@pixelzoom
Copy link
Contributor Author

This same failure is occurring in coulombs-law, greenhouse-effect, and tambo.

@jessegreenberg
Copy link
Contributor

Thanks, the related issue is phetsims/scenery#921. Offending lines were removed earlier today until this can be fixed.

@jessegreenberg
Copy link
Contributor

This was fixed in phetsims/scenery#921 and is no longer showing up on CT.

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

No branches or pull requests

2 participants