Knapsack Pro

DEV Community (dev.to) / dev.to / Cypress tests / Build ID 60204812-f4f7-4a50-8eef-e4909d15c7d0

Build Details

Back to CI builds

Public
Commit hash Branch Nodes Tests execution time Created at
02ef12c refs/pull/20753/merge 8 19 minutes 53.62 seconds   11% 2024-03-12 09:40:47 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 1 minute 39.94 seconds. The shorter this time is, the better.

Loading...

Parallel CI nodes

The first CI node finished its work at 2024-03-12 09:44:14 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 2 minutes 29.21 seconds.

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

Node index Finish time Tests execution time (19 minutes 53.62 seconds)
0 2024-03-12 09:44:19 UTC 2 minutes 18.26 seconds
1 Finished First 2024-03-12 09:44:14 UTC 2 minutes 9.35 seconds
2 2024-03-12 09:44:18 UTC 2 minutes 21.87 seconds
3 2024-03-12 09:44:20 UTC 2 minutes 28.22 seconds
4 2024-03-12 09:44:18 UTC 2 minutes 22.18 seconds
5 Finished Last 2024-03-12 09:45:54 UTC 3 minutes 41.67 seconds
6 2024-03-12 09:44:27 UTC 2 minutes 17.92 seconds
7 2024-03-12 09:44:24 UTC 2 minutes 14.16 seconds

Test Files recorded on parallel CI nodes

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

Running 10 parallel nodes should result in an optimal build time (~1.99 minutes)


Test file path (Displaying entries 101 - 121 of 121 in total files) Execution time
cypress/e2e/seededFlows/moderationFlows/modNavigation.spec.js 3.33 seconds 2% Trend
cypress/e2e/seededFlows/dashboardFlows/managePost.spec.js 3.3 seconds Trend
cypress/e2e/seededFlows/notificationsFlows/subscribeToCommentsFromNotifications.spec.js 3.28 seconds 4% Trend
cypress/e2e/seededFlows/homeFeedFlows/timeFixer.spec.js 3.22 seconds 2% Trend
cypress/e2e/seededFlows/listingFlows/deleteListing.spec.js 3.22 seconds 5% Trend
cypress/e2e/seededFlows/profileFlows/organisationStats.spec.js 3.11 seconds 7% Trend
cypress/e2e/seededFlows/settingsFlows/updateProfileSettings.spec.js 3.11 seconds 3% Trend
cypress/e2e/seededFlows/adminFlows/navigationLinks/navigationLinks.spec.js 2.99 seconds 6% Trend
cypress/e2e/seededFlows/notificationsFlows/followUserFromNotifications.spec.js 2.96 seconds 1% Trend
cypress/e2e/seededFlows/adminFlows/apps/editListingCategory.spec.js 2.93 seconds 9% Trend
cypress/e2e/seededFlows/adminFlows/config/rateLimitSection.spec.js 2.76 seconds 25% Trend
cypress/e2e/seededFlows/registrationFlows/emailRegistration.spec.js 2.58 seconds 7% Trend
cypress/e2e/seededFlows/adminFlows/consumerApps/createConsumerApp.spec.js 2.54 seconds 32% Trend
cypress/e2e/seededFlows/notificationsFlows/notificationNavigation.spec.js 2.11 seconds 39% Trend
cypress/e2e/seededFlows/loggedOutFlows/tagIndex.spec.js 1.92 seconds 6% Trend
cypress/e2e/seededFlows/loggedOutFlows/homeFeed.spec.js 1.75 seconds 4% Trend
cypress/e2e/seededFlows/toggleFeatureFlags.spec.js 360 miliseconds 9% Trend
cypress/e2e/seededFlows/homeFeedFlows/events.spec.js 142 miliseconds 3% Trend
cypress/e2e/seededFlows/dashboardFlows/dashboardNavigation.spec.js 129 miliseconds 7% Trend
cypress/e2e/seededFlows/podcastFlows/togglePodcastPlayback.spec.js 111 miliseconds 6% Trend
cypress/e2e/seededFlows/homeFeedFlows/profilePreviewCards.spec.js 107 miliseconds Trend

Start using Knapsack Pro

Sign up and speed up your tests.