Using the same CI Build ID with different spec files - ambiguous behaviour

[agoldis]

Before opening, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I acknowledge that I will attach a full debug log, otherwise the issue will be closed with no response.

Environment information

# Put output below this line

Describe the bug

Reusing the same ci build id with different spec files gives an ambiguous message. It's better to show an explicit message.
Also need to check why isn't backed rejected the request for a different list of specs for classic load-balancing.

Example:

Can't run because no spec files were found.

We searched for specs matching this glob pattern:

  > /Users/agoldis/currents-demo/cypress/e2e_03/item.spec.js,cypress/e2e_03/smoke.spec.js,cypress/e2e_smoke/smoke.spec.js

  Reporting results and artifacts in background...  

 WARNING  Cannot find run result for spec "cypress/e2e_03/item.spec.js"
 WARNING  Cannot determine run result for spec "cypress/e2e_03/item.spec.js"
 WARNING  Cannot find run result for spec "cypress/e2e_03/smoke.spec.js"
 WARNING  Cannot determine run result for spec "cypress/e2e_03/smoke.spec.js"
 WARNING  Cannot find run result for spec "cypress/e2e_smoke/smoke.spec.js"
 WARNING  Cannot determine run result for spec "cypress/e2e_smoke/smoke.spec.js"

Expected behavior

Show an informative message

Command and Setup

Running cc with different spec files and the same ci build id

Full log and debug output

// Put your logs below this line