Pretest Build Reports - Log tarball details

← back to report list

For more information, see

The pretest-auto-build-check script keeps detailed logs of the build process, archives them and uploads them to this server. Each tarball contains the following files:

File Details Example
./logs/status The determined status of this build Possible values: ok, configure failed, make failed, make-check failed
./logs/input.txt Information about the build
./logs/environment.txt Information about the build machine envrionment
./logs/versions.txt Information about the build machine kernel and programs
autoconf-version: autoconf (GNU Autoconf) 2.69
automake-version: automake (GNU automake) 1.11.6
autopoint-version: /usr/bin/autopoint (GNU gettext-tools) 0.18.1
autoreconf-version: autoreconf (GNU Autoconf) 2.69
make-version: GNU Make 3.81
makeinfo-version: makeinfo (GNU texinfo) 4.13
git-version: git version
wget-version: GNU Wget 1.13.4 built on kfreebsd-gnu.
rsync-version: rsync  version 3.0.9  protocol version 30
cc-version: gcc (Debian 4.7.2-5) 4.7.2
cc-version: cc (Debian 4.7.2-5) 4.7.2
uname-s: GNU/kFreeBSD
uname-r: 9.0-2-amd64
uname-m: x86_64
uname-p: amd64
uname-i: QEMU Virtual CPU version 2.0.0
uname-o: GNU/kFreeBSD
uname-v: #0 Wed Feb 25 13:42:52 UTC 2015
lsb_release-i: Debian
lsb_release-d: Debian GNU/kFreeBSD 7.8 (wheezy)
lsb_release-r: 7.8
lsb_release-c: wheezy
./logs/configure.log output of ./configure (stdout+stderr)
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
./logs/configure.ok Empty file, only exists if ./configure succeeded (returned exit code 0)
./logs/config.log Generated by ./configure
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by GNU Hello configure 2.8, which was
generated by GNU Autoconf 2.68.  Invocation command line was

  $ ./configure

## --------- ##
## Platform. ##
## --------- ##
./logs/config.status Generated by ./configure
#! /bin/bash
# Generated by configure.
# Run this file to recreate the current configuration.
# Compiler output produced by configure, useful for debugging
# configure, is in config.log if it exists.

./logs/config.h Generated by ./configure
/* config.h.  Generated from by configure.  */
/*  Generated from by autoheader.  */

/* Define to 1 if translation of program messages to the user's native
   language is requested. */
   #define ENABLE_NLS 1
./logs/make.log output of make (stdout+stderr)
make  all-recursive
make[1]: Entering directory `/tmp/hello-2.8.8fCee9/hello-2.8'
Making all in contrib
make[2]: Entering directory `/tmp/hello-2.8.8fCee9/hello-2.8/contrib'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/tmp/hello-2.8.8fCee9/hello-2.8/contrib'
Making all in lib
make[2]: Entering directory `/tmp/hello-2.8.8fCee9/hello-2.8/lib'
./logs/make.ok Empty file, only exists if make succeeded (returned exit code 0)
./logs/make-check.log output of make check (stdout+stderr)
Making check in tests
make[1]: Entering directory `/tmp/hello-2.8.8fCee9/hello-2.8/tests'
make  check-TESTS
make[2]: Entering directory `/tmp/hello-2.8.8fCee9/hello-2.8/tests'
PASS: greeting-1
./greeting-2: Skipping test: not a full moon night
SKIP: greeting-2
PASS: hello-1
PASS: last-1
PASS: traditional-1
./logs/make-check.ok Empty file, only exists if make check succeeded (returned exit code 0)
./logs/test-suite.0.log The test suite logs generated by make check. (NOTE: multiple files are possible)
GNU coreutils 8.24: ./tests/test-suite.log

# TOTAL: 579
# PASS:  432
# SKIP:  147
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0
./logs/tail-error.log last 50 lines from the relevant log file (of the failed step) Example: if make check failed, these will be the last 50 lines from make-check.log
./logs/tests-suite-summary.log The test counts and failed tests from test-suite.log files