Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • lava lava
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 96
    • Issues 96
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 64
    • Merge requests 64
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lava
  • lavalava
  • Issues
  • #590

Closed
Open
Created Feb 21, 2023 by Igor Ponomarev@igo95862Contributor

`scheduler/running` page Running and Jobs columns are equivalent

Open https://validation.linaro.org/scheduler/running?page=1#table

Compare the "Running" and "Jobs" columns and observe that they have equal values.

This is because the job can only be TestJob.STATE_RUNNING when the device is Device.STATE_RUNNING

Test jobs goes to state running:

https://git.lavasoftware.org/lava/lava/-/blob/master/lava_scheduler_app/models.py#L1554

and it sets the device to running:

https://git.lavasoftware.org/lava/lava/-/blob/master/lava_scheduler_app/models.py#L1559

Therefore I think the "Jobs" column can be eliminated. (or altered?)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking