Test timed out again and again..

[ghost]

Hi everybody,

I manage to run some funcunit test on testswarm but some of my test takes a long time to run and testswarm give me a beautiful test timed out...

I try to change increase the time of the timeout like this :

"client": {
                "cooldownSleep": 0,
                "nonewrunsSleep": 10,
                "pingTime": 30,
                "pingTimeMargin": 10,
                "runTimeout": 300,
                "saveReqTimeout": 10,
                "saveRetryMax": 3,
                "saveRetrySleep": 5,
                "requireRunToken": false,
                "refreshControl": 0
}

but I still got the time out message.. I even try to set 900sec but the test just wait all this time and after time out..

Is there is a possibility to, at least show the result of the previous test on the testswarm page, instead to have this "Test timed out" message ?

And also, is it possible to set testswarm just pass the time out test and go to the next one ?

That could be awesome !!

[edit] : I just figure out that even for a small test, after the test is done, testswarm is still waiting for something (until the timeout). I don't know how to make testswarm stop the test and just take the result.

Thanks a lot for your help ! :)

Marc.

[Krinkle]

Which test framework are you using?

If you implemented a custom one, please consider submitting a PR so that I can review it for you and point out where it went wrong.

It sounds like you forgot to bind the proper handlers for either the ping, complete or submit events. As a result, even when the test is actually done, the inject script isn't being notified and as such keeps doing nothing until eventually the server discards the client when it still hasn't submitted any results. At this point the job is put back in the pool of pending tests for another client to run.

[ghost]

I'm using funcunit framework, I didn't wrote it yet in the inject.js because I didn't use it so far.. (I know its weird)

I'm using the steal.js to make my test from the framework funcunit. I thought that it would works at least a bit because its like the Qunit test no ?

I'm sorry if I ask too much, but I really don't know how to implement this new framework into testswarm.. :/

[JamesMGreene]

It's like QUnit except that it has a dependency on Selenium. Does your TestSwarm setup now how to handle that?

[Krinkle]

I haven't used FuncUnit specifically much, but in general, until you show some code, I can only recommend:

• Move it to inject.js; Look at inject.js#section-qunit for how to write the small bridge you need to add. Add a similar one for FuncUnit.
• Verify that you are loading TestSwarm's inject.js from your own TestSwarm server (not github, not swarm.jquery.org) in your test suite (jQuery example, MediaWiki example)

[jeff-harnois]

I ran into a similar issue; mine turned out to be the order of the scripts. inject.js needs to be included last, so that it can register some hooks into the test, so if you are not careful with your script order (mine was because I had it in the wrong place using require) then the hook doesn't attach properly and won't ever fire back.