Bug #7291: [Workbench] When Xvfb is not running, Workbench integration tests take 8 hours to fail - Arvados

Actions

Copy link

Bug #7291

closed

[Workbench] When Xvfb is not running, Workbench integration tests take 8 hours to fail

Added by Joshua Randall over 10 years ago. Updated about 6 years ago.

Status:

Closed

Priority:

Normal

Assigned To:

Joshua Randall

Category:

Workbench

Target version:

Story points:

Description

If an X server is not running (or DISPLAY is not set), selenium's firefox driver cannot possibly work, yet the apps/workbench test suit proceeds to attempt every test anyway, taking 60s for each failed selenium invocation.

Actions

Copy link

Updated by Joshua Randall over 10 years ago

% Done changed from 50 to 90

Sanity checks implemented in https://github.com/curoverse/arvados-dev/pull/2

Please review.

Actions

Copy link

Updated by Brett Smith over 10 years ago

Subject changed from When Xvfb is not running, apps/workbench tests run for 8 hours to [Workbench] When Xvfb is not running, Workbench integration tests take 8 hours to fail
Category changed from Tests to Workbench