Piglit

Piglit
Name	Piglit
Developer	Mesa developers, Collabora, Intel, Red Hat
Released	2008
Programming language	C, Python, Bash
Operating system	Linux, FreeBSD
License	MIT License

Piglit

Piglit is an open-source collection of automated tests for graphics drivers and implementations, primarily focused on OpenGL and related APIs. It provides a harness for running conformance, regression, and performance tests against implementations from vendors such as Intel, AMD, NVIDIA, and projects like Mesa and X.Org. Piglit integrates with continuous integration systems used by organizations including Red Hat, Collabora, Valve, and Intel to validate changes to graphics stacks.

Overview

Piglit is designed to exercise implementations of OpenGL, OpenGL ES, GLX, and related extensions across drivers such as Intel Graphics, AMDGPU, and legacy NVIDIA drivers. It complements conformance suites from organizations like the Khronos Group by offering a flexible test harness suitable for integration into projects like Mesa (computer graphics), Wayland, and X.Org Server. Piglit tests run on platforms including Linux, FreeBSD, and on continuous integration platforms used by companies like Red Hat and projects like Debian, Fedora, and Ubuntu. It is often used alongside tools such as GDB, Valgrind, and performance profilers from Intel Corporation and AMD.

History

Piglit originated in the late 2000s as a community-driven effort within the Mesa (computer graphics) project to provide broader testing beyond vendor-provided suites. Early contributors included developers from projects like X.Org Foundation, Canonical (company), and Collabora. Over time, corporations including Intel Corporation, Red Hat, SUSE, and Valve Corporation have contributed test cases and infrastructure. The suite evolved to support new APIs and extensions introduced by the Khronos Group, adapting to changes in graphics stacks driven by projects such as Wayland and drivers like AMDGPU.

Architecture and Components

Piglit is composed of a test harness, individual test programs, result aggregation, and reporting tools. The harness supports multiple backends including GLX, EGL, and off-screen renderers used by Mesa (computer graphics), and integrates with window systems like X.Org Server and compositors such as Weston. Test cases are implemented in C and Python and interact with driver internals similar to how projects like drm and libdrm operate. Components for logging and regression tracking can be integrated with CI systems provided by organizations such as Jenkins (software), GitLab, and GitHub Actions.

Test Suites and Coverage

Piglit includes thousands of tests covering core functionality, extension behavior, shader compilation, buffer manipulation, and rendering outcomes. Tests are designed to exercise functionality specified by the Khronos Group for APIs like OpenGL ES and extensions referenced by drivers from Intel Corporation and AMD. Coverage spans shader stages relied upon by projects such as Mesa and game engines like Godot Engine and Unreal Engine. Specialized suites exist for features relevant to vendors and platforms including Vulkan interop tests, compatibility checks for Libre Software distributions, and regression tests used by companies like Valve Corporation.

Usage and Workflow

Users run Piglit via its command-line harness to execute suites against target drivers, capturing pixel diffs and logs that can be analyzed with tools used by developers at Intel Corporation and Red Hat. Typical workflows integrate Piglit into CI pipelines on systems managed by Jenkins (software), GitLab, or internal platforms at organizations such as Collabora and SUSE. Results feed into bug trackers like Bugzilla and GitHub Issues where developers from projects including Mesa (computer graphics), X.Org Foundation, and vendor teams from NVIDIA and AMD triage failures. Piglit output is often combined with trace analysis tools from Mesa and profiling utilities provided by Intel.

Development and Contribution

Development occurs collaboratively in public repositories hosted on platforms including GitLab and GitHub, with contributors from communities like X.Org Foundation, Mesa (computer graphics), and corporations such as Collabora, Intel Corporation, and Red Hat. Contribution workflows follow practices common to open-source projects, using merge requests, code review, and CI provided by services like Jenkins (software) and GitLab CI/CD. Test authors reference specifications from the Khronos Group and conform to coding standards used across projects like Mesa and X.Org Server. Outreach and coordination happen at conferences and events such as FOSDEM, XDC (X.Org Developer Conference), and vendor summits hosted by Intel and AMD.

Reception and Impact

Piglit has been widely adopted by open-source graphics developers and vendors for regression detection, contributing to the stability of stacks like Mesa and compositors such as Wayland and Weston. Organizations including Red Hat, SUSE, Canonical (company), and Valve Corporation cite Piglit in internal testing pipelines, while projects like Debian and Fedora benefit from its integration. Piglit’s role in catching driver regressions has been recognized in discussions within communities like the X.Org Foundation and at events including FOSDEM and XDC (X.Org Developer Conference), influencing testing practices across the ecosystem.

Category:Graphics software