Skip to content

[CHORE] Track region job ended up running in #142

Description

@darcyclarke

📋 Description

Right now we don't track where the runner is located with could have an effect from one to the next run.

📂 Category

Code Refactoring - Improve code structure/quality

🎯 Motivation

The assumption today is that there isn't some consistent bias but we should track this data either way for debugging & ensure one variant/fixture/tool isn't somehow unfairly advantaged.

🎌 Scope of Work

Add verbose logs as well as output to end-user UI.

📊 Impact Level

Low - Minor improvements, no breaking changes

⏰ Urgency

Low - Can be done when time permits

⚠️ Breaking Changes

No response

🧪 Testing Strategy

No response

✅ Definition of Done

  • Changes implemented as described
  • Existing functionality verified unaffected
  • Tests updated and passing
  • Documentation updated if needed
  • Code reviewed and approved
  • Performance impact assessed
  • Breaking changes documented
  • Migration guide provided (if applicable)
  • Rollback plan prepared (if high risk)

🔗 Dependencies

No response

⏱️ Estimated Timeline

No response

📎 Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions