Closed Bug 1088846 Opened 11 years ago Closed 11 years ago

taskcluster-client: Tests for WebListener under phantomjs fails with some SSL issue

Categories

(Taskcluster :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jonasfj, Unassigned)

Details

I suspect this issue is related to POODLE, but I have no proof.. It just arrived around the same time, which is suspicious. No code changed as far as I know. We're talking about this issue: mocha-phantomjs -R spec \ test/browserify_test.html \ ; browserify ✓ loaded Error loading resource https://queue.taskcluster.net/v1/ping (6). Details: SSL handshake failed Error loading resource https://queue.taskcluster.net/v1/ping (6). Details: SSL handshake failed Error loading resource https://queue.taskcluster.net/v1/ping (6). Details: SSL handshake failed 1) ping queue Error loading resource https://queue.taskcluster.net/v1/ping (6). Details: SSL handshake failed Error loading resource https://events.taskcluster.net/v1/listen/info (6). Details: SSL handshake failed 2) connect and close WebListener Error loading resource https://events.taskcluster.net/v1/listen/info (6). Details: SSL handshake failed 3) connect, bind and close WebListener Note, afaik the WebListener works fine, it's only the tests that are broken somehow.
Finally fixed in phantomjs, a suspected it was a POODLE issue: https://github.com/ariya/phantomjs/issues/12670 I love it when bugs just disappear one their own.. In a2c7791 I've forced us to use version 1.9.8+ for phantomjs, that should solve the issue in existing installations after an run with "npm install".
Ups, this is resolved fixed :)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Component: TaskCluster → General
Product: Testing → Taskcluster
Target Milestone: --- → mozilla41
Version: unspecified → Trunk
Resetting Version and Target Milestone that accidentally got changed...
Target Milestone: mozilla41 → ---
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.