search for: tc_410_close_event

It seems the default behaviour of rake is to run tests sequentially, and not in parallel (there are separate gems to achieve that behaviour). Hence just invoke "rake test" to run all the available tests at once. This reverts commit 8f30c3c3f8c063f7c5ff8c6154d881e07a820251. --- ruby/run-ruby-tests | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git

In data martedì 7 giugno 2016 22:35:33, Richard W.M. Jones ha scritto: > 'tc_410_close_event.rb' was not being run. You could prove this by > simply inserting "exit 1" into that test. > > The reason is unclear, but by renaming every class and method in the > tests to be unique, this ensures the tests are run. > --- ruby/t/tc_410_close_event.rb: def test_eve...

Make more use of assert_equal/refute_equal instead of manually checking values and raising errors. --- ruby/t/tc_100_launch.rb | 4 +--- ruby/t/tc_410_close_event.rb | 8 ++------ ruby/t/tc_420_log_messages.rb | 4 +--- ruby/t/tc_810_rhbz664558c6.rb | 4 +--- 4 files changed, 5 insertions(+), 15 deletions(-) diff --git a/ruby/t/tc_100_launch.rb b/ruby/t/tc_100_launch.rb index 9c31aa5..b79b984 100644 --- a/ruby/t/tc_100_launch.rb +++ b/ruby/t/tc_100_launch....

--- generator/ruby.ml | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/generator/ruby.ml b/generator/ruby.ml index 97ccfdc..0f71ccc 100644 --- a/generator/ruby.ml +++ b/generator/ruby.ml @@ -404,15 +404,17 @@ event_callback_wrapper_wrapper (VALUE argvv) return Qnil; } +/* Callbacks aren't supposed to throw exceptions. We just print the + * exception on

'tc_410_close_event.rb' was not being run. You could prove this by simply inserting "exit 1" into that test. The reason is unclear, but by renaming every class and method in the tests to be unique, this ensures the tests are run. --- ruby/t/tc_010_load.rb | 4 ++-- ruby/t/tc_020_create.rb...

...0_create_flags.rb | 29 +++++++++++ ruby/t/tc_040_create_multiple.rb | 32 +++++++++++++ ruby/t/tc_050_handle_properties.rb | 36 ++++++++++++++ ruby/t/tc_060_explicit_close.rb | 29 +++++++++++ ruby/t/tc_070_optargs.rb | 2 +- ruby/t/tc_100_launch.rb | 2 +- ruby/t/tc_410_close_event.rb | 2 +- ruby/t/tc_420_log_messages.rb | 2 +- ruby/t/tc_800_rhbz507346.rb | 2 +- ruby/t/tc_810_rhbz664558c6.rb | 2 +- ruby/t/tc_820_rhbz1046509.rb | 42 ++++++++++++++++ 14 files changed, 254 insertions(+), 28 deletions(-) create mode 100644 ruby/t/tc_030_crea...

On Fri, Jun 10, 2016 at 03:10:32PM +0200, Pino Toscano wrote: > In data martedì 7 giugno 2016 22:35:33, Richard W.M. Jones ha scritto: > > 'tc_410_close_event.rb' was not being run. You could prove this by > > simply inserting "exit 1" into that test. > > > > The reason is unclear, but by renaming every class and method in the > > tests to be unique, this ensures the tests are run. > > --- > > ruby/t/t...

If the connection is not local, paths of disks will refer to the remote host, which were mistakenly handled as local paths (in the best case failing to open a non-existing disk, and in the worst case opening a different disk!). In case the disks are remote resources like ssh or ceph, nothing guarantees that the hostname can be reached from the local machine, or even that it is actually the same on

Hopefully this time ...