Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

adt-run

adt-run -V (return code: 20)

adt-run: WARNING: "adt-run" is deprecated, please use "autopkgtest" (see manpage)
usage: adt-run [options] action [action ...] --- virt-server [options]
adt-run: error: You must specify --- <virt-server>...adt-run -HELP (return code: 20)

adt-run: WARNING: "adt-run" is deprecated, please use "autopkgtest" (see manpage)
usage: adt-run [options] action [action ...] --- virt-server [options]

Test installed binary packages using the tests in the source package.

Actions specify the source and binary packages to test, or change
what happens with package arguments:
  --unbuilt-tree DIR or DIR//
                        run tests from unbuilt Debian source tree DIR
  --built-tree DIR or DIR/
                        run tests from built Debian source tree DIR
  --source DSC or some/pkg.dsc
                        build DSC and use its tests and/or generated binary
                        packages
  --git-source GITURL [branchname]
                        check out git URL (optionally a non-default branch),
                        build it if necessary, and run its tests
  --binary DEB or some/pkg.deb
                        use binary package DEB for subsequent tests
  --changes CHANGES or some/pkg.changes
                        run tests from dsc and binary debs from a .changes
                        file
  --apt-source SRCPKG or somesrc
                        download with apt-get source in testbed and use its
                        tests
  --click-source CLICKSRC or some/src
                        click source tree for subsequent --click package
  --click CLICKPKG or some/pkg.click
                        install click package into testbed (path to *.click)
                        or use an already installed click package
                        ("com.example.myapp") and run its tests (from
                        manifest's x-source or preceding --click-source)
  --override-control CONTROL
                        run tests from control file/manifest CONTROL instead
                        in the next package
  --testname TESTNAME   run only given test name in the next package
  -B, --no-built-binaries
                        do not use any binaries from subsequent --source,
                        --git-source, or --unbuilt-tree actions
  --built-binaries      use binaries from subsequent --source, --git-source,
                        or --unbuilt-tree actions

logging options:
  -o OUTPUT_DIR, --output-dir OUTPUT_DIR
                        Write test artifacts (stdout/err, log, debs, etc) to
                        OUTPUT-DIR (must not exist or be empty)
  -l LOGFILE, --log-file LOGFILE
                        Write the log LOGFILE, emptying it beforehand, instead
                        of using OUTPUT-DIR/log
  --summary-file SUMMARY
                        Write a summary report to SUMMARY, emptying it
                        beforehand
  -q, --quiet           Suppress all messages from adt-run itself except for
                        the test results

test bed setup options:
  --setup-commands COMMANDS_OR_PATH
                        Run these commands after opening the testbed (e. g.
                        "apt-get update" or adding apt sources); can be a
                        string with the commands, or a file containing the
                        commands
  --setup-commands-boot COMMANDS_OR_PATH
                        Run these commands after --setup-commands, and also
                        every time the testbed is rebooted
  -U, --apt-upgrade     Run apt update/dist-upgrade before the tests
  --apt-pocket POCKETNAME[=pkgname,src:srcname,...]
                        Enable additional apt source for POCKETNAME. If
                        packages are given, set up apt pinning to use only
                        those packages from POCKETNAME; src:srcname expands to
                        all binaries of srcname
  --copy HOSTFILE:TESTBEDFILE
                        Copy file or dir from host into testbed after opening
  --env VAR=value       Set arbitrary environment variable for builds and test

user/privilege handling options:
  -u USER, --user USER  run tests as USER (needs root on testbed)
  --gain-root GAINROOT  Command to gain root during package build, passed to
                        dpkg-buildpackage -r

debugging options:
  -d, --debug           Show lots of internal adt-run debug messages
  -s, --shell-fail      Run a shell in the testbed after any failed build or
                        test
  --shell               Run a shell in the testbed after every test

timeout options:
  --timeout-test T      set test timeout to T seconds (default: 10000s)
  --timeout-install T   set install timeout to T seconds (default: 3000s)
  --timeout-short T     set short timeout to T seconds (default: 100s)
  --timeout-copy T      set copy timeout to T seconds (default: 300s)
  --timeout-build T     set build timeout to T seconds (default: 100000s)
  --timeout-factor FACTOR
                        multiply all default timeouts by FACTOR

locale options:
  --set-lang LANGVAL    set LANG on testbed to LANGVAL (default: C.UTF-8

other options:
  --no-auto-control     Disable automatic test generation with autodep8
  --build-parallel N    Set "parallel=N" DEB_BUILD_OPTION for building
                        packages (default: number of available processors)
  -h, --help            show this help message and exit

The --- argument separates the adt-run actions and options from the
virt-server which provides the testbed. See e. g. man autopkgtest-schroot for
details.
Path

Comments

Popular posts from this blog

PostgreSQL Pgbadger Installation On Linux

PostgreSQL pgBadger

How to configure Replication Manager (repmgr) ?

Migrating From Oracle to PostgreSQL using ora2pg open source tools

How To Schedule PostgreSQL Jobs using pgAgent on Linux plateform