Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
M
mesa_jenkins
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container 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
  • Mesa_CI
  • mesa_jenkins
  • Issues
  • #36

Closed
Open
Opened Jan 31, 2019 by Emil Velikov@evelikov

dEQP/CTS NotSupported tests are flagged as "failed"

Based on [1] and [2] seems that dEQP/CTS tests reporting Not Supported are flagged as fail. Did I understand this correctly, what the reason behind this?

In piglit we use "skip" for similar cases and I think the CI has such a state.

Thanks

[1] https://mesa-ci.01.org/wip_18_3/builds/23/results/2940440 [2] https://github.com/KhronosGroup/VK-GL-CTS/blob/master/external/vulkancts/modules/vulkan/wsi/vktWsiDisplayTests.cpp#L2089

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: Mesa_CI/mesa_jenkins#36