Using Maloo

Using Maloo

Introduction

Maloo is Whamcloud's shared database of Lustre testing results, provided to make it easy for those testing Lustre to collaborate and track progress. Maloo is available for interested parties to upload and view test data.

Getting started

The Maloo server is located at https://testing.whamcloud.com. At present, all access to view and upload results requires a user account. You can register for an account using the "Sign up now" link on the login page. A newly created account is not usable until an administrator validates it – we aim to validate accounts within 24 hours (usually much sooner).

Once your account has been validated, when you log in you will see a list of the latest test results.

Viewing test results

The main page view (sessions from the menu at the top of the page) shows all test sessions which have been run, in reverse chronological order. This page shows the list of test runs uploaded, which can be filtered using the criteria available at the top of the page.

Each test session contains a number of test sets that represent the results for a single patch. Each test set in a session may have a number of sub tests, these are the individual test items that get marked pass/fail and their results are aggregated up to the session level. There will often be multiple test sessions for a single patch build, each one running a different test group. The purpose of splitting a single patch into multiple test groups is to be able to run these tests in parallel and obtain pass/fail results for all sooner.

Searching Maloo

On the top of each Maloo page the [results->search] menu item allows searching the test results by a variety of parameters. Commonly, one wants to search for specific test results (e.g. sanity) that have FAILed in the past week to see if a test failure is unique to the patch being tested, or if it is being hit intermittently for other patches as well. In addition to searching for the full test results, it is also possible to select the [Sub test] option at the top of the page to search for a specific subtest result (e.g. sanity test_102). Other search parameters include the test group, host distro, host architecture, backing filesystem type (ldiskfs or zfs), and others. 

Uploading test results

Please note that Maloo only accepts properly formatted result uploads.

The format of test results is the YAML markup generated by the Lustre test framework. The output of the tests consists of a number of YAML files and log files. Maloo receives these results in a gzipped tar file of the tests results for each test session. The files must be in the root of the tar file.

Autotest

The vast majority of test uploads are initiated by the Whamcloud Autotest application which continually kicks off test runs as patches land in the Lustre code repository, the application then monitors when the test completes and uploads the results automatically to Maloo.

Manual upload

Select [results->upload] from the menu at the top of the page to access the manual upload page, there are three ways to manually upload results:

Web Upload

If you have a set of results that need to be uploaded, simply choose the file and select upload from the page, the results will be available a few seconds after the upload completes.

command-line

For command-line uploads you will need to download the .maloorc configuration file which is available from the [results->upload] page.

Using auster

The auster script in the lustre source tree can automatically upload results when a test run completes. In order to do this, the .maloorc file is required. This file provides the address of the server, and a unique token associating uploaded results with your user account.

 maloo_upload.sh

You can download the maloo_upload.sh shell script and configuration file from the [results->upload] page which can be used to perform uploads from the command line.