Arch Testing Team

The Arch Testing Team is a group within the Arch community in charge of making sure that packages submitted to the testing repositories are functional. This includes, making sure that the package installs correctly, that it does not cause breakage with packages of which it depends on, among others.

Arch Testers sign off packages after vouching for their correctness so that they can be moved from the testing repositories into the core, extra or community repositories.

Contributing

You can apply to be an official Arch tester by contacting Florian Pritz via email and requesting a tester account.

If you are given a tester account, you should be able to log in into archweb and see a signoffs tab on it. The signoffs tab will contain a list of packages that are currently in the testing repositories and need at least two signoffs (i.e., a rubber-stamp vouching for the correctness of a package).

You may then test the listed packages locally and signing them off if they are correct by clicking on the signoff button for each package.

Tip: You can simplify the process by signing off packages from the command line with signoff(1) from the arch-signoff package.

Guidelines

In order to test an arch package, keep the following aspects in mind:

  • If you are testing a kernel or a package that relies on kernel modules, you should restart the machine and ensure that it boots correctly.
  • Although testing on virtualization software is not prohibited, it may not be as useful as testing a package in a bare-metal installation. This applies specially to packages that are susceptible to different types of hardware, such as kernel packages.
  • If you are testing a library, you may want to execute a binary that uses such library. Make sure the shared object file is loaded using ldd.
  • Likewise, if there is a package that ships executables, testing their basic functionality is encouraged.
  • If you notice an error when testing a package, add a detailed bug report on the bugtracker:
    • Package name, version and pkgrel
    • Which component of the package was the one to error (e.g., one of the binaries, or a configuration file)
    • Root of the error (e.g., during installation, or usage, etc.)
    • Any relevant error messages/logs
    • Make sure the bug is filed with the category Packages: Testing

Coordination
Note: It is expected that people using the testing repositories frequently check the arch-dev-public mailing list for any announced changes or considerations affecting testing users.

You can coordinate with other testers on the #archlinux-testing IRC channel, and follow updates by packager activity on the arch-commits mailing list (high traffic).

gollark: If your code expects that to work it may sometimes *not*, e.g. if power failure happens, and the user will probably not be there to receive them.
gollark: I don't think remote-waking computers to display notifications makes much sense.
gollark: You would have to have a server of some sort store the notifications so the device can ask for them later.
gollark: Well, you can't, because it's off.
gollark: You could make it track closer to the terrain and possibly use less processing power by making it only check the stuff roughly under its path.
This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.