There are some inconsistent errors like this in built fuzzing. It is curious enough that @jonathanolson and I would like to make an issue to track and investigate. We just increased the number of "full snapshots" (not erasing the data) to 20, so if we find this again, we will have a couple days to try to reproduce locally. I believe it started popping up when we switched over to the node-based client: https://github.com/phetsims/aqua/issues/178. Not just if it is because of the testing-style, or if the older tests were hiding this error.
wave-interference : fuzz : built
http://127.0.0.1/continuous-testing/ct-snapshots/1684120385794/wave-interference/build/phet/wave-interference_en_phet.html?continuousTest=%7B%22test%22%3A%5B%22wave-interference%22%2C%22fuzz%22%2C%22built%22%5D%2C%22snapshotName%22%3A%22snapshot-1684120385794%22%2C%22timestamp%22%3A1684121632072%7D&fuzz
Query: fuzz
TypeError: tn() is not a constructor
phet.chipper.runWebpack/</<@http://127.0.0.1/continuous-testing/ct-snapshots/1684120385794/wave-interference/build/phet/wave-interference_en_phet.html?continuousTest=%7B%22test%22%3A%5B%22wave-interference%22%2C%22fuzz%22%2C%22built%22%5D%2C%22snapshotName%22%3A%22snapshot-1684120385794%22%2C%22timestamp%22%3A1684121632072%7D&fuzz:1003:1472946
at phet.chipper.runWebpack/</< (http://127.0.0.1/continuous-testing/ct-snapshots/1684120385794/wave-interference/build/phet/wave-interference_en_phet.html?continuousTest=%7B%22test%22%3A%5B%22wave-interference%22%2C%22fuzz%22%2C%22built%22%5D%2C%22snapshotName%22%3A%22snapshot-1684120385794%22%2C%22timestamp%22%3A1684121632072%7D&fuzz:1003:1472946)
at phet.chipper.runWebpack/< (http://127.0.0.1/continuous-testing/ct-snapshots/1684120385794/wave-interference/build/phet/wave-interference_en_phet.html?continuousTest=%7B%22test%22%3A%5B%22wave-interference%22%2C%22fuzz%22%2C%22built%22%5D%2C%22snapshotName%22%3A%22snapshot-1684120385794%22%2C%22timestamp%22%3A1684121632072%7D&fuzz:1003:2483770)
at phet.chipper.runWebpack (http://127.0.0.1/continuous-testing/ct-snapshots/1684120385794/wave-interference/build/phet/wave-interference_en_phet.html?continuousTest=%7B%22test%22%3A%5B%22wave-interference%22%2C%22fuzz%22%2C%22built%22%5D%2C%22snapshotName%22%3A%22snapshot-1684120385794%22%2C%22timestamp%22%3A1684121632072%7D&fuzz:1003:2483774)
at i (http://127.0.0.1/continuous-testing/ct-snapshots/1684120385794/wave-interference/build/phet/wave-interference_en_phet.html?continuousTest=%7B%22test%22%3A%5B%22wave-interference%22%2C%22fuzz%22%2C%22built%22%5D%2C%22snapshotName%22%3A%22snapshot-1684120385794%22%2C%22timestamp%22%3A1684121632072%7D&fuzz:1004:1021)
at t (http://127.0.0.1/continuous-testing/ct-snapshots/1684120385794/wave-interference/build/phet/wave-interference_en_phet.html?continuousTest=%7B%22test%22%3A%5B%22wave-interference%22%2C%22fuzz%22%2C%22built%22%5D%2C%22snapshotName%22%3A%22snapshot-1684120385794%22%2C%22timestamp%22%3A1684121632072%7D&fuzz:1004:1049)
at <unknown> (http://127.0.0.1/continuous-testing/ct-snapshots/1684120385794/wave-interference/build/phet/wave-interference_en_phet.html?continuousTest=%7B%22test%22%3A%5B%22wave-interference%22%2C%22fuzz%22%2C%22built%22%5D%2C%22snapshotName%22%3A%22snapshot-1684120385794%22%2C%22timestamp%22%3A1684121632072%7D&fuzz:1004:1074)
at <unknown> (http://127.0.0.1/continuous-testing/ct-snapshots/1684120385794/wave-interference/build/phet/wave-interference_en_phet.html?continuousTest=%7B%22test%22%3A%5B%22wave-interference%22%2C%22fuzz%22%2C%22built%22%5D%2C%22snapshotName%22%3A%22snapshot-1684120385794%22%2C%22timestamp%22%3A1684121632072%7D&fuzz:1004:1176)
id: Sparky Playwright Firefox
Snapshot from 5/14/2023, 9:13:05 PM
There are some inconsistent errors like this in built fuzzing. It is curious enough that @jonathanolson and I would like to make an issue to track and investigate. We just increased the number of "full snapshots" (not erasing the data) to 20, so if we find this again, we will have a couple days to try to reproduce locally. I believe it started popping up when we switched over to the node-based client: https://github.com/phetsims/aqua/issues/178. Not just if it is because of the testing-style, or if the older tests were hiding this error.