⚠ This page is served via a proxy. Original site: https://github.com
This service does not collect credentials or authentication data.
Skip to content

Conversation

@kmiller68
Copy link
Contributor

Right now the results end in a reverse alphabetically sorted order. This looks weird. Ideally we would just change the order that we run tests but I worry that will change the results in a non-trivial way (although I didn't try directly).

In future JetStream versions we should revert this and sort the tests in the other direction.

Right now the results end in a reverse alphabetically sorted order. This
looks weird. Ideally we would just change the order that we run tests
but I worry that will change the results in a non-trivial way (although
I didn't try directly).

In future JetStream versions we should revert this and sort the tests in
the other direction.
@netlify
Copy link

netlify bot commented Jan 13, 2026

Deploy Preview for webkit-jetstream-preview ready!

Name Link
🔨 Latest commit 1b3f6bd
🔍 Latest deploy log https://app.netlify.com/projects/webkit-jetstream-preview/deploys/6966cd1367605f00087f7ff1
😎 Deploy Preview https://deploy-preview-253--webkit-jetstream-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@danleh
Copy link
Contributor

danleh commented Jan 14, 2026

I'd still be happy to change the order of execution to alphabetical. If this causes a big change in score for a particular line-item on any engine, let's investigate. (Part of the discussion around iteration sizes was to not be so dependent, e.g., on GC timing, so if we still are, I'd rather know it.)

@camillobruni
Copy link
Contributor

+1 to changing the underlying order
-1 to having a mismatch between UI and execution order. I always found it very confusing to follow the execution order in the old UI (looking a line item, it's visually moving around while this is not the case currently anymore). The current version makes this very clear (and actually does expose the "weird" underlying reverse execution order)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants