Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Yocto ptest checks package-level tests on the target device; LAVA handles getting an image onto a device, booting it, running those tests, and collecting results. To make the workflow reliable, first ensure the image contains the ptest packages, then run and record their outcomes, and finally inspect individual test cases—not just the LAVA job’s overall state.
How ptest and LAVA fit together
A ptest is a package’s test suite, run on the target machine. The package supplies the tests and a run-ptest launcher that starts them. Yocto documents per-test outcomes as PASS, FAIL, or SKIP followed by a test name. Yocto Project: Testing Packages With ptest
As an Amazon Associate I earn from qualifying purchases.
LAVA operates at a different level: a job describes the device, deployment, boot process, and tests to execute. A LAVA server accepts and schedules jobs, provides logs and results, and coordinates with workers that run jobs on physical or virtual devices. The job YAML and the test definition are related but separate: the job configures the pipeline; a test definition describes commands or scripts executed on the target.
Prepare the AGL image to contain ptest packages
Enabling ptest support and installing ptest packages into the image are separate configuration steps. The current Yocto development manual describes the following patterns; check the Yocto version and layer behavior for the AGL release you are building before copying them.
#1 Best Overall
- Featuring a 1GHz processor and SGX530 Graphics Engine.
- IntegratedNEON SIMD coprocessor；
- On board eMMC memory
- This development board offer high-speed USBconnectivity, an HDMIcompatible interface, and expandable memory option.
- Advanced for BeagleBone Black AM335x CortexA8 Development Board
- Enable ptest support in the distribution: add
DISTRO_FEATURES:append = " ptest". This enables building and packaging ptest for recipes that support it; it does not, by itself, add the test packages to the image. - Choose which tests to include: to include all generated ptest packages, add
EXTRA_IMAGE_FEATURES += "ptest-pkgs". To include selected suites instead, add their package-test packages throughIMAGE_INSTALL:append, using the package names applicable to your build. - Check recipe support: a recipe commonly enables ptest by inheriting the ptest class with
inherit ptest. The manual also identifies framework-specific classes, including ones for Go, Cargo, GNOME, Perl, and pytest. A recipe without applicable test support will not gain a suite merely because the distribution feature is enabled. - Build and verify the image: confirm the selected ptest packages were built and installed. The manual describes installed test files under
/usr/lib/package/ptest. Verify the actual image contents before treating a missing suite as a runtime test failure.
Include all suites or select a subset?
| Choice | When it fits | Trade-off |
|---|---|---|
All generated ptest packages via ptest-pkgs |
A broad test image or a run intended to exercise available package tests | May increase image size, build work, and runtime; the Yocto manual does not quantify those costs. |
Selected packages via IMAGE_INSTALL:append |
A focused image or a run targeting specific components | Requires choosing suites deliberately and provides narrower coverage; cost savings are not quantified in the manual. |
Run ptest on the target and preserve the evidence
Once the image boots, run ptest-runner on the target. The runner executes installed suites sequentially, reports totals and failures, and returns exit status 1 if a run-ptest fails. Retain the per-suite output as well as the summary: the summary tells you that something failed, while the suite log helps identify what and where. Yocto Project ptest documentation
For a manual check, capture both standard output and the exit code in whatever logging mechanism your target shell or test harness uses. A nonzero runner status is a failed test run, not proof that the image failed to boot or that the LAVA infrastructure failed.
What belongs in a LAVA job versus a test definition?
A LAVA job is a YAML description of the job to execute. It selects the device and describes deployment, boot, and test actions. Server-side submission performs basic validation; workers carry out full validation at runtime. LAVA job schema
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →A LAVA test-shell definition supplies target-side commands through an overlay. It runs after boot and requires a POSIX system on the target. LAVA builds the script from the definition, transfers the overlay, boots the target, retrieves output, and processes it into results. LAVA test definition guide
Rank #3
- There are several options for this item, this option is with header. Please click the image 2 to check the package content.
- Luckfox Lyra is a cost-effective Linux micro development board based on the Rockchip RK3506G2 to provide a simple and efficient development platform. Onboard multiple high-speed interfaces including MIPI DSl, RMll, USB, etc. to meet various application scenarios.
- The low-speed interfaces utilize Rockchip Matrix l0 design which supports multiplexing 98 function siqnals on GPlO pins, and can freely combine PWM, UART, 12C, SPl, and l2S for quick development and debugging.
- Tripe-core ARM Cortex-A7 32-bit core, with integrated VFP to support single- and double-precision floating-point operations. Built-in ARM Cortex-M0 MCU design, supports SMP and AMP configuration. Built-in 128MB DDRL3 for multi-core applications
- The low-speed interfaces adopt Rockchip Matrix IO design, which allows rich function signals to share the limited chip pins, making peripheral circuit adaptation more flexible. Built-in audio and video codec, supports multiple audio inputs and outputs, providing high-quality audio playback and recording functions
- Job YAML: the device, deployment method, boot actions, and which tests or definitions to run.
- Test definition: commands or scripts that run on the target and report test outcomes.
- Result recording: use
lava-test-casein a test script, or a suitable parser/custom script, to record named cases. The command supports pass, fail, skip, and unknown outcomes, as well as optional measurements with units.
Shell execution uses set -e, so an unhandled failing command can stop the test script. Handle commands deliberately when you need to capture a failure and continue to report additional cases. Older parse-pattern and fixup features are deprecated in the guide in favor of custom scripts that explicitly call lava-test-case.
AGL’s LAVA toolkit recommends keeping reusable test definitions in the AGL qa-testdefinitions repository and provides QEMU and physical-device patterns. Treat its templates as starting points and confirm their current state and compatibility with your instance. AGL LAVA toolkit
Rank #4
- ZYNQ-7000 ARM+FPGA SoC: Powered by Xilinx ZYNQ XC7Z010/020 with dual-core ARM Cortex-A9 and programmable logic—ideal for embedded and FPGA development.
- Integrated Interfaces for Versatile Applications: Features HDMI, USB 2.0 Host, UART, JTAG, Gigabit Ethernet (PS & PL), SD card, and 40-pin expansion for AD/DA, LCD, and camera modules.
- Robust Memory & Storage: Equipped with 512MB/1GB DDR3, 128Mb QSPI Flash, 64Kbit EEPROM, and boot selection via JTAG/QSPI/SD for flexible design setups.
- Industrial-Grade Design: Compact 90x60mm board with immersion gold finish, suitable for industrial environments. 5V/1A power input supports stable operation.
- Support for Linux and Hardware Demos: Supports embedded Linux system, MIPI CSI camera input (7020 only), and comes with HDL demos—perfect for research and education.
Choose a device and deployment path that your instance supports
Test execution can use an existing shared LAVA instance or a self-managed instance, and a virtual target such as QEMU or physical hardware. There is no universally best option: shared access reduces the need to administer the service but depends on available devices and permissions; self-management offers control over configuration but adds server and worker administration. QEMU can suit repeatable development workflows, while physical hardware is necessary to cover behavior specific to the actual board. LAVA documentation supports physical and virtual devices but does not establish a universal preference.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Deployment and boot support depend on the device type and LAVA instance configuration. Start from the closest known-working standard job for the same device type and deployment style; support for a method on one board does not establish support on another. LAVA gold-standard jobs
Decide whether a run passed: inspect the cases, not just the job state
A job marked Finished and Complete shows that the pipeline completed; it does not establish that every test passed. Review the run in this order:
- Did the pipeline complete? Check the overall job state and logs for errors during validation, deployment, or boot.
- Did the device reach the test action? Confirm the expected image booted and the target-side test definition actually ran. A failed prompt or boot sequence may resemble a test failure if you look only at missing test output.
- Were the expected cases recorded? Confirm each intended case appears with a result. Missing cases may mean the script stopped early or the test action did not run.
- What failed? Separate package-test failures from deployment, boot, or infrastructure problems. Use the LAVA log and the retained per-suite ptest output to locate the failure.
- Are logs and artifacts available? Keep the runner output and LAVA logs so a failed suite can be investigated rather than inferred from the aggregate state.
Keep commands and templates tied to the release
The Yocto commands above come from the development manual, while AGL’s LAVA documentation currently resolves to its Unagi documentation tree and LAVA’s cited pages are labeled 2026.01. The topic does not identify an AGL release, board, image configuration, or LAVA instance, so no single job YAML or deployment command can be treated as universal. Match the Yocto manual and AGL templates to the release you build, and verify device type, boot method, image format, and deployment support with the LAVA instance you use.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
