Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
M MTSA
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 68
    • Issues 68
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lafhis
  • MTSA
  • Issues
  • #15

Closed
Open
Created May 26, 2025 by Pablo Laciana@placianaOwner

Prioritization does not work with set labels

Adding a simpler spec of the problem.

‌

In

set A = {a, b, c}
P = (A -> P2 | d -> P2),
P2 = (d->P).
||Q = (P) << {A}.
||S = (P) << {a, b, c}.

I would expect S and Q to be the same. However, they are different.

The correct result is S.

The problem in Q is that the set A should be interpreted as {a, b, c, a?, b?, c?} but is being interpreted as {a?, b?, c?}

‌

PLEASE ADD TEST FOR THIS TOO.

‌

‌

‌



-In this example, prioritization is not applied when the set to prioritize is given by a set id. It does work if the set is provided inline.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking