search for: test_type

Can someone point me to a reference or tutorial that shows how to map foreign key relationships in the model? For example given: Users id name email Posts id user_id title How do I associate user_id with users.id in the Post and User models? has_many and belongs_to don''t seem to do it. -- Posted via http://www.ruby-forum.com/.

...database. When I select something in the combobox and press ''update'' it goes through fine, except it places the default value for the field of the combobox. Any suggestions? Here''s the model: class TestResult < ActiveRecord::Base has_one :status_index has_one :test_type has_one :product_area validates_presence_of :statusindex_id, :testtype_id, :productarea_id, :name end This generates the combobox (inside a view partial): <%= select("test_type", "id", TestType.find_all.collect {|tt| [tt.name, tt.id] }, { :include_blank => false})...

So both Liu and I made huge messes of find_lock_delalloc_range trying to fix stuff, me first by fixing extent size, then him by fixing something I broke and then me again telling him to fix it a different way. So this is obviously a candidate for some testing. This patch adds a pseudo fs so we can allocate fake inodes for tests that need an inode or pages. Then it addes a bunch of tests to make

...defaults to 1. pointless if template & target are files # template  : source directory or file with permissions to clone # target    : destination directory or file for cloning perms to # # version 1.0 USAGE="Usage: $0 [-r] [-p numcores] template target" # determine parameter type test_type() {     TYPE_TEST=$1     if   [ -d "${TYPE_TEST}" ]     then return 1; # directory     elif [ -f "${TYPE_TEST}" ]     then return 2; # file     else         echo "${TYPE_TEST} is not found!"; echo $USAGE; exit 1;     fi } # check for options CORES=1 RECURSE=0...

On Sat, 2018-03-24 at 20:38 -0400, Ken McDonald via samba wrote: > > > By default, step 4 takes forever to run on large datasets because it > > uses named entities. My ultimate plan was to use the numeric > > user/group id's in that step instead of named ones so the Winbind cost > > is not incurred. Seems for the whole process, the calls to Winbind to > >

...g)); p = guestfs_get_sockdir (g); printf ("guestfs_get_sockdir: %s\n", p ? : "(null)"); diff --git a/tests/selinux/run-test.pl b/tests/selinux/run-test.pl index f0f241f..7e4620f 100755 --- a/tests/selinux/run-test.pl +++ b/tests/selinux/run-test.pl @@ -105,8 +105,6 @@ if ($test_type eq "selinux" && $test_via eq "fuse") { # Create a filesystem that could support xattrs and SELinux labels. my $g = Sys::Guestfs->new (); -#$g->set_selinux (1) if $test_type eq "selinux"; - $g->add_drive_scratch (256*1024*1024); $g->launch ();...

...g)); p = guestfs_get_sockdir (g); printf ("guestfs_get_sockdir: %s\n", p ? : "(null)"); diff --git a/tests/selinux/run-test.pl b/tests/selinux/run-test.pl index f0f241f..7e4620f 100755 --- a/tests/selinux/run-test.pl +++ b/tests/selinux/run-test.pl @@ -105,8 +105,6 @@ if ($test_type eq "selinux" && $test_via eq "fuse") { # Create a filesystem that could support xattrs and SELinux labels. my $g = Sys::Guestfs->new (); -#$g->set_selinux (1) if $test_type eq "selinux"; - $g->add_drive_scratch (256*1024*1024); $g->launch ();...

We can use the setfiles(8) command to relabel the guest filesystem, even though we don't have a policy loaded nor SELinux enabled in the appliance kernel. This also deprecates or removes the old and broken SELinux support. This patch isn't quite complete - I would like to add some tests to the new API. I'm posting here to garner early feedback. Rich.

v1 -> v2: - Add simple test of the setfiles API. - Use SELinux_relabel module in virt-v2v (instead of touch /.autorelabel). - Small fixes. Rich.

...int flags, const char *dev_name, void *data) { - return mount_pseudo(fs_type, "btrfs_test:", NULL, NULL, BTRFS_TEST_MAGIC); + return mount_pseudo(fs_type, "btrfs_test:", &btrfs_test_super_ops, + NULL, BTRFS_TEST_MAGIC); } static struct file_system_type test_type = { diff --git a/fs/btrfs/tests/btrfs-tests.h b/fs/btrfs/tests/btrfs-tests.h index e935fe5..b353bc8 100644 --- a/fs/btrfs/tests/btrfs-tests.h +++ b/fs/btrfs/tests/btrfs-tests.h @@ -26,6 +26,7 @@ int btrfs_test_free_space_cache(void); int btrfs_test_extent_buffer_operations(void); int btrfs_test_...

This converts more of the tests (basically everything under tests/) to use the test harness, revealing some problems which have subsequently been fixed. Rich.

Since v4: - More tests have been converted. - Testing local guests fixed. - Drop no-exec-stack test.

For v6: This is mainly just a rebase, but I have also added tests in the ocaml/ language bindings directory, and for all the OCaml-written virt tools. Rich.

v7: The only changes since v6 are those suggested by Pino in the review of v5.

I should probably start by saying this patch series isn't ready for review yet. This patch series adds a test harness to libguestfs. It allows us to run the tests outside the ordinary 'make check' path in the build tree. In particular, you can use this to run tests when libguestfs has been installed. 'make check' and the other 'make check-*' rules still work. The

This is a more complete patch to add the test harness. The only parts missing now are the language bindings (except OCaml). The language bindings need a bit more thought. At the moment most language binding tests are done through some sort of shell script like perl/run-perl-tests which either runs each test itself or uses some language-specific machinary to run each test. The problem with that

Since v2: - Add perl tests. - Reworked and fixed the tests for virt-builder. - Some further minor bug fixes.

Since v3: - A large number of fixes, especially for running the tests on installed libguestfs. - Fixed EXTRA_DIST rules throughout. - Extra patch 17/17 which is a tidy-up of the generated XML listing guests. Rich.