Lars T Hansen [:lth] Reporter
	Description • 7 years ago

Currently (see bug 1346068 comment 14) agent tests are disabled in the browser because the test cases are not suitable for the browser and the $262.agent framework is insufficient for dealing with a browser.

Work items:
 
- fix $262.agent framework upstream (tc39/test262#928)
- fix the test cases upstream (ditto)
- fix our implementation of $262.agent in js/src/tests/test262-host.js and
  js/src/tests/test262/shell.js
- remove the opt-outs in js/src/tests/jstests.list

	Lars T Hansen [:lth] Reporter
	Comment 1 • 7 years ago

https://treeherder.mozilla.org/#/jobs?repo=try&revision=6c0d83e7ba5b80e56bb54a88b6b4ff3c8df25b3e

	Lars T Hansen [:lth] Reporter
	Comment 2 • 7 years ago

https://treeherder.mozilla.org/#/jobs?repo=try&revision=c18d6eaf11df973ad0d56c78f5706ad19580f0a2

	Lars T Hansen [:lth] Reporter
	Comment 3 • 7 years ago

https://treeherder.mozilla.org/#/jobs?repo=try&revision=282e5f185da3e581413dab572a850963ed90f4d9

	Lars T Hansen [:lth] Reporter
	Comment 4 • 7 years ago

This has a new harness with a new API and rewritten test cases.  It is *roughly* right and it passes locally when run in a browser with a simplified context, but fails on try, see the links in previous comments.

The error is invariably that 'no output' is produced for the test cases.  I think that what's most likely happening is that when $262.agent.start() returns to the event loop, as it must for the workers to be created properly, and also when it tries to wait for results from the workers, then the test runner may conclude that the test is done (because the script returned).  But the only way to determine that is either to see test output, or to time out.

	Jason Orendorff [:jorendorff]
	Comment 5 • 6 years ago

I'm updating test262. It looks like the API being tested here has changed, and basically none of the tests will run for us anymore. I'm going to disable them in jstests.list.

	Lars T Hansen [:lth] Reporter
	Comment 6 • 6 years ago

Bug 1470490 is about renaming wait as notify, I hope nothing else is a problem.  And the rename (really - introduce an alias, for now) is all but trivial.  And that bug should be unblocked now.