<< Back to previous view

[CLJS-407] cljs.import-test not run in test suite / ordering problem in the compiler Created: 24/Oct/12  Updated: 03/Jan/15  Resolved: 03/Jan/15

Status: Closed
Project: ClojureScript
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Defect Priority: Minor
Reporter: Herwig Hochleitner Assignee: Unassigned
Resolution: Completed Votes: 0
Labels: None

Attachments: Text File 0001-CLJS-407-Hook-up-cljs.import-test-to-the-test-runner.patch    


The test code from CLJS-312 is not hooked up to the test suite, which is trivially fixed.

Hooking up the test, however reveals a deeper problem (besides that it has a failing assumption):

Presumably due to the goog.provides later in the files, the compiler orders the output wrong, which results in not provided errors.
Most interestingly, this problem goes away, when compiling from a prepopulated out directory, presumably because then the closure compiler handles the ordering?

Comment by Herwig Hochleitner [ 24/Oct/12 3:23 AM ]

Patch hooks up the tests into the test suite.

If you want to see the provide error, delete out before compiling.

If you want to see the failing assertion from the original test, compile a second time.

Comment by David Nolen [ 24/Oct/12 11:01 AM ]

In order to better understand tickets it best not to complect different issues If there's a problem not addressed by the patch please mention that in another ticket (and feel to reference that one here).

I assume the patch fixes one thing, but reveals an unresolved issue, am I correct?

Comment by Herwig Hochleitner [ 24/Oct/12 11:26 AM ]

You're right, the ordering problem could be a different ticket. Sorry for that.

To clarify, there are three issues at play:

1) Part of the testsuite not executed (fixed by the patch)
2) The part that is now executed fails, didn't have time this morning to find out the original intention of MichaƂ, can probably do tomorrow, if he doesn't pick it up.
3) The compilate is different depending on whether the .js file is cached in out/. This might require some deeper investigation.

The reason I decided to roll it into one ticket is that only addressing one of 2) and 3) leaves the test suite failing. I almost wanted to reopen CLJS-312, but decided against it, since it's water under the bridge.

Comment by David Nolen [ 21/Dec/12 6:07 PM ]

I fixed some dependency ordering issue in another patch, would be nice to know if the ordering issues are addressed. What part of this ticket is still relevant? This is why tickets that only address one thing at a time are nice

Comment by David Nolen [ 03/Jan/15 6:16 PM ]

This no longer seems to be an issues with the arrival of cljs.test

Generated at Fri Sep 22 22:59:51 CDT 2017 using JIRA 4.4#649-r158309.