3 source plates should be ordered by bed number and scanner has CR suffix failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

Robot minimum volumes should be considered failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

Source volumes should be updated once failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

Robot minimum volumes should be considered for water failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

Barcode scanners with carriage return should not submit page until end failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

A study is created and it appears in Pending ethical approval true failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

A study is created and it appears in Pending ethical approval true failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

A study is created and it appears in Pending ethical approval true failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

A study is created and it appears in Pending ethical approval true failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

A study is created and it appears in Pending ethical approval true failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

The job was canceled because "_2_0" failed.

When the data release is standard failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

When the data release is immediate failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

When the data release is delayed for PhD study failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

When the data release is never but the prevention other comment is not supplied failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

When the data release is never and the prevention other comment is supplied failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

When the data release is never and the prevention comment is supplied failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

Approving the plate layout failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

Approving the plate layout failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

Creating plates where the scanner appends a carriage return failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

Listing individual types of studies failed: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir

Batches controller request zero comments link

Batches controller reordering requests

Labwhere reception displays the correct labwhere error messages

Labwhere reception user can scan plates into the reception

stamping of stock stamping of stock

View study properties view open study properties

Asset submission upload a qc file

Lab view User can update concentrations

Process completed with exit code 1.

The job was canceled because "_3_2" failed.

Cherrypicking pipeline where there is a control plate and a single destination behaves like a cherrypicking procedure running the cherrypicking pipeline Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:384

Cherrypicking pipeline where there is a control plate and a single destination when the number of plates exceeds number of beds (Several runs) behaves like a cherrypicking procedure running the cherrypicking pipeline Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:403

Cherrypicking pipeline where the number of plates does not exceed the max beds for the robot behaves like a cherrypicking procedure running the cherrypicking pipeline Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:329

Cherrypicking pipeline where there is a control plate and multiple destinations behaves like a cherrypicking procedure running the cherrypicking pipeline Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:435

Cherrypicking pipeline where there is a control plate and multiple destinations when the number of plates exceeds number of beds (Several runs) behaves like a cherrypicking procedure running the cherrypicking pipeline Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:460

Cherrypicking pipeline when creating batches requests leave the inbox once a batch has been created

Cherrypicking pipeline where there are multiple destination plates and the number of plates exceeds the max beds for the robot behaves like a cherrypicking procedure running the cherrypicking pipeline Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:367

Cherrypicking pipeline where the number of plates exceeds the max beds for the robot behaves like a cherrypicking procedure running the cherrypicking pipeline Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:339

Cherrypicking pipeline where picking by ng/µl for a tecan robot when robot is using 96-Trough buffer (Tecan v1) behaves like a cherrypicking procedure running the cherrypicking pipeline Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:165

Cherrypicking pipeline where picking by ng/µl for a tecan robot when robot is using 8-Trough buffer (Tecan v2) behaves like a cherrypicking procedure running the cherrypicking pipeline Shared Example Group: "a cherrypicking procedure" called from ./spec/features/pipelines/cherrypick/cherrypick_pipeline_spec.rb:273

The job was canceled because "_3_2" failed.

Asset submission Validation of Flowcell Type field for request types that require a Flowcell Type displays an error if Flowcell Type is not set

Asset submission Validation of Flowcell Type field for request types that require a Flowcell Type creates a new request successfully when Flowcell Type is correctly set

Asset submission Validation of Flowcell Type field for request types that do not require a Flowcell Type creates a new request successfully even when Flowcell Type is not specified

Asset submission when an admin with a new request_type behaves like it allows additional sequencing request additional sequencing Shared Example Group: "it allows additional sequencing" called from ./spec/features/assets/asset_submission_spec.rb:239

Asset submission when an admin with the original request_type behaves like it allows additional sequencing request additional sequencing Shared Example Group: "it allows additional sequencing" called from ./spec/features/assets/asset_submission_spec.rb:233

Asset submission when an admin when cross study pooled behaves like it allows cross study sequencing request additional sequencing without study Shared Example Group: "it allows cross study sequencing" called from ./spec/features/assets/asset_submission_spec.rb:251

Asset submission when an admin when cross study pooled behaves like it allows cross study sequencing request additional sequencing with override study Shared Example Group: "it allows cross study sequencing" called from ./spec/features/assets/asset_submission_spec.rb:251

Asset submission when study does not have an accession number behaves like it shows an error message about study has error message Shared Example Group: "it shows an error message about study" called from ./spec/features/assets/asset_submission_spec.rb:268

Asset submission when a regular user behaves like it forbids additional sequencing the link is not visible Shared Example Group: "it forbids additional sequencing" called from ./spec/features/assets/asset_submission_spec.rb:258

Asset submission The request form does not set default values when the user selects a request type does not set flowcell type to default value

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

No files were found with the provided path: tmp/capybara/. No artifacts will be uploaded.

No files were found with the provided path: tmp/capybara/. No artifacts will be uploaded.

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636