ArduPilot/ardupilot

Add visualisation for data in build_binaries_history.sqlite

Open

#14,439 opened on May 24, 2020

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C++ (9,336 stars) (15,603 forks)batch import
good first issue

Description

Feature request

This file is generated as part of an autotest run. It contains information about which boards built and which boards did not for a particular tested git sha.

It would be nice to be able to visualise this data on the autotest results page.

Previously when I've done this I've created a table, the left-most column being the most recent tested master commit, the columns sorted by git history. This allows you to narrow down to a narrow range of commits where a board's build was broken.

However, a quicker patch giving a lot of value would be to extract the data in autotest.py's build_binaries.py and do a results.add() for the failing boards. Only the failures for the master commit (as opposed to the stable/beta tags) would be reported as the story is too difficult to tell otherwise. Rejigging autotest to run on the different tags (as opposed to running build_binaries on the different tags) is not in scope here :-)

Contributor guide

Tech stack
pythonsqlite
Domain
backendtesting
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
PythonSQLiteAutotest framework
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Start by examining the existing autotest.py and build binaries.py files in the repository. Understand the schema of build binaries history.sqlite. Consider implementing the simpler approach: modify build binaries.py to extract failing boards and call results.add() for each. Then verify on the autotest results page. The issue also mentions a more comprehensive table visualization, but the simpler patch is recommended for newcomers.