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

Post a Comment

Popular posts from this blog

How to find the server is whether standby (slave) or primary(master) in Postgresql replication ?

-
Method 1 You can check the mode of the server using "pg_controldata". [pgsql@test~]$ pg_controldata /usr/local/pgsql/data84/ Database cluster state: in archive recovery --> This is Standby Database Database cluster state: in production --> This is Production Database [Master] Method 2 You can use pg_is_in_recovery() which returns True if recovery is still in progress(so the server is running in standby mode or slave) postgres=# select pg_is_in_recovery(); pg_is_in_recovery ------------------- t (1 row) If Return    false   so the server is running in primary mode or master postgres=# select pg_is_in_recovery(); pg_is_in_recovery ------------------- f (1 row)
Read more

How to Get Table Size, Database Size, Indexes Size, schema Size, Tablespace Size, column Size in PostgreSQL Database

-
In this post, I am sharing few important function for finding the size of database, table and index in PostgreSQL. Finding object size in postgresql database is very important and common. Is it very useful to know the exact size occupied by the object at the tablespace. The object size in the following scripts is in GB. The scripts have been formatted to work very easily with PUTTY SQL Editor. 1. Checking table size excluding table dependency: SELECT pg_size_pretty(pg_relation_size('mhrordhu_shk.mut_kharedi_audit')); pg_size_pretty ---------------- 238 MB (1 row) 2. Checking table size including table dependency: SELECT pg_size_pretty(pg_total_relation_size('mhrordhu_shk.mut_kharedi_audit')); pg_size_pretty ---------------- 268 MB (1 row) 3. Finding individual postgresql database size SELECT pg_size_pretty(pg_database_size('db_name')); 4. Finding individual table size for postgresql database -including dependency index: SELECT pg_size_pretty(pg_total_rel
Read more

How to Return a Result Set from a PostgreSQL Stored Procedure

-
Image
Both stored procedures and user-defined functions are created with CREATE FUNCTION statement in PostgreSQL. To return one or more result sets (cursors in terms of PostgreSQL), you have to use  refcursor  return type. Quick Example : -- Procedure that returns a single result set (cursor) CREATE OR REPLACE FUNCTION show_cities ( ) RETURNS refcursor AS $$ DECLARE ref refcursor; -- Declare a cursor variable BEGIN OPEN ref FOR SELECT city , state FROM cities; -- Open a cursor RETURN ref; -- Return the cursor to the caller END ; $$ LANGUAGE plpgsql; Overview : Return Multiple Result Sets Cursor Lifetime Until the  end  of transaction Auto-commit Must be  off Transaction must be active so the caller can see a result set Important Note : The cursor remains open until the end of transaction, and since PostgreSQL works
Read more

7 Steps to configure BDR replication in postgresql

-
Image
 The  BDR  (Bi-Directional Replication) project adds multi-master replication to PostgreSQL 9.4.  Postgres-BDR has a lower impact on the masters(s) than trigger-based replication solutions. There is no write-amplification, as it does not require triggers to write to queue tables in order to replicate writes.   Here We are using  postgres version 9.4.12 and bdr version 1.0.2. for configuring  multi master replication . Simply Following 7 steps you can configure the multi master replication in postgresql. To download the bdr in below link. .   https://github.com/2ndQuadrant/bdr/archive/bdr-pg/REL9_4_12-1.tar.gz $ tar -xzvf REL9_4_12-1.tar.gz $ wget https://github.com/2ndQuadrant/bdr/archive/bdr-plugin/1.0.2.tar.gz $ tar -xzvf 1.0.2.tar.gz 1. To install BDR. $ cd ~/bdr-bdr-pg-REL9_4_12-1 $ ./configure --prefix=/usr/lib/postgresql/9.4 --enable-debug --with-openssl $ make -j4 -s install-world $ cd ~/bdr-bdr-plugin-1.0.2 $ PATH=/usr/lib/postgresql/9.4/bin:"$PATH" ./c
Read more

PostgreSQL Pgbadger Installation On Linux

-
Image
PgBadger is a tool that analyzes PostgreSQL log files and generates reports on execution of SQL and server operation. Statistical reports analyzed from a number of perspectives can be useful not only for grasping the usual database operation but also as a hint for performance improvement. The report output by pgBadger has the following features. Graph output in HTML format Many statistical objects Daily, Weekly unit creation possible 1.Graph output in HTML format Many of the analysis results can be displayed in graph form by outputting the report in HTML format (output in text format or JSON format is also possible). By analyzing the log information graphed, it is much more prospective for people to see than the raw log data. So, if you do not need to handle it with another tool separately, we recommend report output in HTML format. 2.Many statistical objects A lot of data useful for database performance analysis is output in the report as shown below. Qu
Read more