ci.testling.com Service Timeout #88

Open
RGBboy opened this Issue Jul 14, 2014 · 63 comments

Projects

None yet
@RGBboy
RGBboy commented Jul 14, 2014

For the past 2 weeks I have been getting a Service Timeout when my Github hook is sent to Testling. I noticed that GitHub has changed their web hook interface but I'm pretty sure I have all the settings correct:

Payload URL: http://git.testling.com
Content type: application/x-www-form-urlencoded
Trigger: Just the push event

It worked before. I have tried redelivering the event as well as deleting and creating the hook again but I still get a Service Timeout.

Am I doing something wrong or is it a problem on the Testling server?

@orangemug

I've been experiencing the same issue, it did seem to get resolved yesterday for a short time.

@orangemug

@RGBboy it seems to be working for me now

@RGBboy
RGBboy commented Jul 17, 2014

I have tried redelivering the hook and it still fails.

@gobwas
gobwas commented Jul 20, 2014

The same problem for me. Also question is - which content type is right?

@chrisveness

Is testling still running? I'm just getting Service Timeout also. (using application/x-www-form-urlencoded) It's ok, just me being impatient, I guess... though it only worked briefly, I still seem to get nothing but service timeouts

@oncletom

Timeouts are systematic since a couple of days for git.testling.com.

Any idea how to fix it?

@cmcnulty

Getting nothing but Service Timeout here as well.

@subhaze
subhaze commented Jul 30, 2014

Getting a Service Timeout as well.

@spoike
spoike commented Jul 31, 2014

Got service timeout too for the past couple of days.

@spoike spoike referenced this issue in reflux/refluxjs Jul 31, 2014
Closed

Add web tests #3

@nickb1080

Same. Can anyone confirm the correct settings for Payload URL, Content type, and Trigger?

@Munter
Munter commented Aug 4, 2014

Also experiencing webhook timeouts

@JamesKyburz

me too

@h2non
h2non commented Aug 6, 2014

Me too. What's the real problem? There is any new about this @substack?

@oncletom
oncletom commented Aug 6, 2014

He mentioned the following:

the server keeps running out of memory
I think we need to sandbox the chroot jobs better
I've been poking at a think using docker tonight

So he's investigating and so far we have to deal with it (or give a hand to fix this).

@benjamine

same here

Same. Can anyone confirm the correct settings for Payload URL, Content type, and Trigger?

@h2non h2non referenced this issue in h2non/thread.js Aug 7, 2014
Closed

Add support for Testling CI #5

@gobwas
gobwas commented Aug 12, 2014

Still sleeping... =((

@evanshortiss

Looks like this is an ongoing issue still?

@nickb1080

@evanshortiss unfortunately yes

@jgillich

@substack Any official words about this?

@krillr
krillr commented Aug 29, 2014

So... how are we supposed to run builds while this is broken?

@svnlto
svnlto commented Sep 2, 2014

Same issue here.

@jesseditson

😢

@DCKT
DCKT commented Sep 6, 2014

Hi guys, there are no news about this error ?

@nickb1080

Unfortunately no

@bripkens
bripkens commented Sep 8, 2014

We just switched Reflux to Karma + SauceLabs since testling doesn't seems to be maintained any longer :(. The necessary changes can be seen in this pull request: reflux/refluxjs#61

@nickb1080

Any thoughts on the switch? Going well so far?

On Mon, Sep 8, 2014 at 8:54 AM, Ben Ripkens notifications@github.com
wrote:

We just switched Reflux to Karma + SauceLabs since testling doesn't seems to be maintained any longer :(. The necessary changes can be seen in this pull request: reflux/refluxjs#61

Reply to this email directly or view it on GitHub:
#88 (comment)

@bripkens
bripkens commented Sep 8, 2014

Testing locally works fine so war. @spoike is still fiddling with the Travis setup as far as I can tell. Creating a demo project right now to document necessary migration steps.

@nickb1080

Awesome, would you throw a link here once the demo is up and running? Would love to take a peek, thanks!

On Mon, Sep 8, 2014 at 8:58 AM, Ben Ripkens notifications@github.com
wrote:

Testing locally works fine so war. @spoike is still fiddling with the Travis setup as far as I can tell. Creating a demo project right now to document necessary migration steps.

Reply to this email directly or view it on GitHub:
#88 (comment)

@bripkens
bripkens commented Sep 8, 2014

Unfortunately the karma-sauce-launcher is currently lacking a required parameter for SauceLabs status images (public test result visibility). I opened a PR just now which adds this capability. Once done, the SauceLabs configuration could be done in minutes (but unfortunately not as trivial as testling). Will keep you posted.

@spoike
spoike commented Sep 9, 2014

Following up from Reflux: @nickb1080 @bripkens I've managed to set the project up to run the tests on Sencha, with some barebones hacky configuration. I need to do more set up (adding meta info, working out grunt config) in order to get the testing badge.

@benjamine

it would be nice to have an official word about his before moving to another platforms (which unfortunately have setups far from the simplicity of testling), is testling for open source really not going to come back?

@jesseditson

I guess it's been broken since July, so my best guesses as to a path forward is to:
a) drop testling support on your app
b) pony up and pay for it (assuming testling enterprise works)
c) build our own testling hosts (and maybe share with the community?), as I believe all parts of this are OSS.

If I get some spare time I'll explore option c, as I'd love to see this available to people again.

@h2non
h2non commented Sep 11, 2014

Hey @jesseditson
I've been also thinking about this from a long time (the C option, I mean)... however I would like introduce some architectural improvements in order to partially avoid some of the existent problems with Testling

Could you be interested to talk more about this?
Any other is also interested?

@gobwas
gobwas commented Sep 11, 2014

@h2non , @jesseditson I am interested too in any kinds of help.

@nickb1080

@h2non Definitely interested in exploring the "C option"

@svnlto
svnlto commented Sep 16, 2014

A little bit of an update on this issue:

11:42 <substack> svnlto: working on that, need to roll out batchdb stuff to queue things properly
@gobwas
gobwas commented Sep 25, 2014

Any news guys?

@nickstenning nickstenning referenced this issue in openannotation/annotator Oct 15, 2014
Merged

Browser tests via Karma #453

@aeoril
aeoril commented Oct 18, 2014

I am having this issue - which of the two content types should we use? (json/x-www-form-urlencoded)

@jgillich

@aeoril I don't think that setting matters, the service is just not working at all.

@aeoril
aeoril commented Oct 18, 2014

@jgillich ok, thanks for the quick reply - do you mean on the github side or testling? Is there any other way to use testling?

@fourcube

http://git.testling.com/ cannot be resolved. Any ETA on when the service will be back up again?

This was referenced Oct 28, 2014
@pkrumins

I apologize about the situation with Testling. Unfortunately the software isn't working well and I'll need to rewrite it to get it back working. This will take a couple of months.

@tarmolov
tarmolov commented Nov 1, 2014

It will be a great New Year present for all of us :)

@deepsweet

This will take a couple of months.

so.. do you have such plans? 😧

@evanshortiss

@pkrumins thanks for the update.

@bripkens
bripkens commented Nov 5, 2014

@nickb1080 and others: I wrote a short Karma + SauceLabs how to for CommonJS modules. You can basically use it as a migration guide from Testling to Karma and SauceLabs.

The demo project can be found on GitHub as well.

@noyobo
noyobo commented Nov 14, 2014

me too

@JamesKyburz

testling was awesome when it worked, hope it comes back soon!

In the meantime for open sauce projects needing test love, check out zuul.

It took no time to setup an open source account with saucelabs, and the code was nearly identical to the testling code.

Here shows the commit from testling to zuul.

defunctzombie has great docs to get you started.

@mightyiam

@JamesKyburz I'm beginning to like zuul. Thank you for pointing it out.

@bevacqua

Zuul is a great alternative. FYI I just wrote zuulnice to get it to configure browserify properly. Might come in handy. Esp. when setting up things like proxyquire on the client.

@Kikobeats

same issue here :(

@miguelmota

An update on this? I'm getting Service Timeouts like the rest

@TehShrike

See this reply by @pkrumins.

Testling is effectively unavailable, until a rewrite can be done - I would suggest that a collaborator lock this issue until then.

A few suggestions for alternatives to testling have been posted in the thread above.

@gobwas
gobwas commented Feb 12, 2015

@pkrumins maybe any news? =)

@adrai
adrai commented Mar 3, 2015

really any news (positive or negative)?

@tarmolov
tarmolov commented Mar 4, 2015

I've switched to zuul and sause lab. Works great for me.

@gobwas
gobwas commented Mar 4, 2015

@tarmolov +1, but want to testling alive! =)

@differui
differui commented Mar 5, 2015

same here =((

@jessehattabaugh

Please put up a warning on your homepage that this service isn't functioning. I just wasted a day setting it up only to find out now that it's been broken for half a year! "SyntaxError: Unexpected end of input" is not sufficient.

@RobertWHurst

Also kind of pissed. I paid for a premium account last year, and then It broke two weeks later. I couldn't find a way to get any support. I tried tweeting at @substack and the Testling account and got no response. You guys haven't really communicated what is going on, and I kind of want my money back. At least tell us what's going on here.

@nelsonic nelsonic added a commit to dwyl/learn-testling that referenced this issue May 20, 2015
@nelsonic nelsonic Known issue: substack/testling#88 599c879
@nelsonic

Sad times. We really want to use Testling!
Posted question to StackOverflow: http://stackoverflow.com/questions/30310409/how-do-i-setup-testling-ci-with-qunit-qunit-tap
If this gets resolved please let us know!
Thanks!

@mweststrate

Same issue here

@zzolo
zzolo commented Jun 1, 2015

Please update the website and github project or take it down all together.

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