How to Install and Uninstall python3-subunit2sql Package on Ubuntu 20.10 (Groovy Gorilla)

Last updated: December 23,2024

1. Install "python3-subunit2sql" package

This guide let you learn how to install python3-subunit2sql on Ubuntu 20.10 (Groovy Gorilla)

$ sudo apt update $ sudo apt install python3-subunit2sql

2. Uninstall "python3-subunit2sql" package

In this section, we are going to explain the necessary steps to uninstall python3-subunit2sql on Ubuntu 20.10 (Groovy Gorilla):

$ sudo apt remove python3-subunit2sql $ sudo apt autoclean && sudo apt autoremove

3. Information about the python3-subunit2sql package on Ubuntu 20.10 (Groovy Gorilla)

Package: python3-subunit2sql
Architecture: all
Version: 1.10.0-4
Priority: optional
Section: universe/python
Source: python-subunit2sql
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian OpenStack
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 418
Depends: alembic, python3-alembic, python3-dateutil, python3-oslo.config, python3-oslo.db, python3-pbr, python3-six (>= 1.9.0), python3-sqlalchemy, python3-stevedore, subunit, python3-subunit, python3:any
Suggests: python-subunit2sql-doc
Filename: pool/universe/p/python-subunit2sql/python3-subunit2sql_1.10.0-4_all.deb
Size: 55336
MD5sum: 486ef80940e233cb89e2d7b7b9def8b7
SHA1: 2ddb50d629a7273388128940670fd6991fc9d0ed
SHA256: a3cc09ad919b6aaca2b8e5a275e2e0aab43dcc6deab419eec6cc4fdb7ae9356e
SHA512: 2ad576b8c6cb581ac82c4adbb39243f4bc63f29dc50b48c127ec18dca5890ccb5289e48160195150c32456e4fc8a46b7ccd78ad6569b2e331c41af0a7b81560f
Homepage: https://github.com/openstack-infra/subunit2sql
Description-en: subunit file/stream to DB - Python 3.x
subunit2SQL is a tool for storing test results data in a SQL database. Like
it's name implies it was originally designed around converting subunit streams
to data in a SQL database and the packaged utilities assume a subunit stream
as the input format. However, the data model used for the DB does not preclude
using any test result format. Additionally the analysis tooling built on top
of a database is data format agnostic. However if you choose to use a
different result format as an input for the database additional tooling using
the DB API would need to be created to parse a different test result output
format. It's also worth pointing out that subunit has several language library
bindings available. So as a user you could create a small filter to convert a
different format to subunit. Creating a filter should be fairly easy and then
you don't have to worry about writing a tool like :ref:`subunit2sql` to use a
different format.
.
For multiple distributed test runs that are generating subunit output it is
useful to store the results in a unified repository. This is the motivation for
the testrepository project which does a good job for centralizing the results
from multiple test runs.
.
However, imagine something like the OpenStack CI system where the same basic
test suite is normally run several hundreds of times a day. To provide useful
introspection on the data from those runs and to build trends over time the
test results need to be stored in a format that allows for easy querying.
Using a SQL database makes a lot of sense for doing this, which was the
original motivation for the project.
.
At a high level subunit2SQL uses alembic migrations to setup a DB schema that
can then be used by the subunit2sql tool to parse subunit streams and populate
the DB. Then there are tools for interacting with the stored data in the
subunit2sql-graph command as well as the sql2subunit command to create a
subunit stream from data in the database. Additionally, subunit2sql provides a
Python DB API that can be used to query information from the stored data to
build other tooling.
.
This package contains the Python 3.x module.
Description-md5: e1c9f0ee342bfc5055e67fe92d1dc922