Knapsack Pro

My organization (team117-LIMS@sanger.ac.uk) / Sequencescape / Cucumber Tests / Build ID a701e261-ee6d-475a-b58e-977cf637b5ff

Build Details

Back to CI builds

Public
Commit hash Branch Nodes Tests execution time Created at
331df71 refs/pull/4079/merge 2 8 minutes 20.32 seconds   4% 2024-04-11 20:18:44 UTC

Parallel CI nodes

All parallel CI nodes finished their work.

The time span between the finish times of the CI node that Finished First and the one which Finished Last is 2 minutes 2.99 seconds. The shorter this time is, the better.

Loading...

Parallel CI nodes

The first CI node finished its work at 2024-04-15 13:34:36 UTC. CI nodes that finished at least 60s later are highlighted.

The reason for slow CI nodes might be too large test files (see the Test Files tab). You may want to try the Knapsack Pro Queue Mode (Ruby) to improve the distribution of your tests. Learn more about dynamic test suite split here.

Note: if you run a CI build for the same commit again (for instance when you retry a CI build), then you will see the data updated below. Some of the nodes might be highlighted until the whole CI build is complete.

The average test execution time per CI node is 4 minutes 10.16 seconds.

The time span between the finish times of the CI node that Finished First and the one which Finished Last is 2 minutes 2.99 seconds. The shorter this time is, the better.

Node index Finish time Tests execution time (8 minutes 20.32 seconds)
0 Finished Last 2024-04-15 13:36:39 UTC 5 minutes 11.04 seconds
1 Finished First 2024-04-15 13:34:36 UTC 3 minutes 9.28 seconds

Test Files recorded on parallel CI nodes

You can likely decrease your CI build time by around 2 minutes 31 seconds by running more parallel CI nodes.

Running 5 parallel nodes should result in an optimal build time (~1.67 minutes)


Test file path (Displaying entries 101 - 140 of 140 in total files) Execution time
features/data_release/8487329_array_express_accession_number.feature 325 miliseconds 11% Trend
features/api/tag_qc/lots.feature 321 miliseconds 9% Trend
features/api/sequencing_requests.feature 321 miliseconds 24% Trend
features/api/sample_manifests/sample_tubes.feature 305 miliseconds 18% Trend
features/api/searches/find_source_assets_by_destination_asset_barcode.feature 301 miliseconds 9% Trend
features/api/order_templates.feature 293 miliseconds 2% Trend
features/api/batches.feature 275 miliseconds 5% Trend
features/batch/show_created_at_date.feature 272 miliseconds 13% Trend
features/administration/robots.feature 271 miliseconds 7% Trend
features/api/samples.feature 270 miliseconds 19% Trend
features/administration/admin_barcode_printer.feature 267 miliseconds Trend
features/studies/5859843_create_study_owner_bug.feature 253 miliseconds 2% Trend
features/submission/27012705_prevent_inactive_projects_from_being_selected_at_submission.feature 247 miliseconds 28% Trend
features/studies/study_state.feature 234 miliseconds 8% Trend
features/samples/workflow_filtering_views.feature 222 miliseconds 17% Trend
features/studies/4295391_study_xml_needs_to_be_reverted_to_old_version.feature 222 miliseconds Trend
features/api/custom_metadatum_collections.feature 219 miliseconds 7% Trend
features/api/library_events.feature 218 miliseconds 24% Trend
features/studies/user_group.feature 218 miliseconds 7% Trend
features/api/tag_qc/lot_types.feature 192 miliseconds 7% Trend
features/api/npg/11438075_request_xml_exception_on_nil_study.feature 184 miliseconds 42% Trend
features/api/users.feature 171 miliseconds 24% Trend
features/api/sample_tubes.feature 171 miliseconds 38% Trend
features/api/tag_qc/robots.feature 171 miliseconds 271% Trend
features/batch/print_label_cluster_info_bug.feature 166 miliseconds 23% Trend
features/api/reference_genomes.feature 162 miliseconds 33% Trend
features/api/searches/find_robots_by_barcode.feature 157 miliseconds 63% Trend
features/samples/6110751_correct_volume_unit_for_samples.feature 151 miliseconds 16% Trend
features/api/searches/find_user_by_swipcard_code.feature 150 miliseconds 199% Trend
features/api/barcode_printers.feature 132 miliseconds 11% Trend
features/api/searches/find_user_by_login.feature 128 miliseconds 13% Trend
features/api/studies.feature 126 miliseconds 7% Trend
features/api/suppliers.feature 92 miliseconds 109% Trend
features/api/asset_groups.feature 89 miliseconds 5% Trend
features/api/searches/find_lot_by_lot_number.feature 77 miliseconds 15% Trend
features/samples/xml_interface.feature 71 miliseconds 12% Trend
features/api/projects.feature 64 miliseconds 18% Trend
features/api/searches/find_deprecated.feature 53 miliseconds 32% Trend
features/api/users/swipecard_code.feature 48 miliseconds 23% Trend
features/api/searches.feature 43 miliseconds 30% Trend

Start using Knapsack Pro

Sign up and speed up your tests.