Jasmine tests failing on CI

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Atira Odhner <aodhner(at)pivotal(dot)io>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Jasmine tests failing on CI
Date: 2017-04-06 09:15:08
Message-ID: CA+OCxowu2QyhoB5HC9Bra2mMheok7-tA=UZjyx3mDjnjrCw9mA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi Tira,

The Jasmine tests have started failing on jenkins.pgadmin.org. They
still pass on my laptop, and were working fine prior to today. I've
not changed anything in the code that I would expect to break
anything:

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents(at)^1(dot)0(dot)0
(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
fsevents(at)1(dot)1(dot)1: wanted {"os":"darwin","arch":"any"} (current:
{"os":"linux","arch":"x64"})
npm WARN web No description
npm WARN web No repository field.
npm WARN web No license field.
[33m06 04 2017 09:08:54.653:WARN [watcher]: [39mAll files matched by
"/var/lib/jenkins/workspace/pgadmin4-master-python34/web/regression/javascript/test-main.js"
were excluded or matched by prior matchers.
[32m06 04 2017 09:08:54.754:INFO [karma]: [39mKarma v1.6.0 server
started at http://0.0.0.0:9876/
[32m06 04 2017 09:08:54.755:INFO [launcher]: [39mLaunching browser
PhantomJS with unlimited concurrency
[32m06 04 2017 09:08:54.762:INFO [launcher]: [39mStarting browser PhantomJS
[32m06 04 2017 09:08:55.017:INFO [PhantomJS 2.1.1 (Linux 0.0.0)]:
[39mConnected on socket EoHSMp65Ic2FQa5ZAAAA with id 23708146
[33m06 04 2017 09:09:05.017:WARN [PhantomJS 2.1.1 (Linux 0.0.0)]:
[39mDisconnected (1 times), because no message in 10000 ms.
PhantomJS 2.1.1 (Linux 0.0.0) ERROR
Disconnected, because no message in 10000 ms.

[https://jenkins.pgadmin.org/job/pgadmin4-master-python33/lastFailedBuild/console]

Googling is showing numerous other people with the same problem
(including that it only fails on some machines such as CI servers), in
some cases able to fix it with random tweaks to timeout and retry
settings.

Do you have any idea what's really going on? I'm loathe to start
randomly tweaking settings without understanding the real issue.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Browse pgadmin-hackers by date

  From Date Subject
Next Message Murtuza Zabuawala 2017-04-06 14:05:42 Re: i18n GER, suggestions, questions
Previous Message Dave Page 2017-04-06 08:56:56 pgAdmin 4 commit: Fix validation on the table dialogue so the Save butt