Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P piglit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 37
    • Issues 37
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 73
    • Merge requests 73
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mesa
  • piglit
  • Issues
  • #47

Closed
Open
Created Jan 14, 2021 by Emma Anholt@anholtOwner

quick-shader.py output differs each build

Mesa CI is having issues with piglit because it seems the set of tests run changes on each build. I'm having a hard time visualizing the diff, but the diff after this command sequence should be empty:

touch tests/quick_shader.py
ninja
gzip -dc tests/quick_shader.xml.gz > a

touch tests/quick_shader.py
ninja
gzip -dc tests/quick_shader.xml.gz > b

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