search for: test_cases

The vsock_diag.ko module already has a test suite but the core AF_VSOCK functionality has no tests. This patch series adds several test cases that exercise AF_VSOCK SOCK_STREAM socket semantics (send/recv, connect/accept, half-closed connections, simultaneous connections). The v1 of this series was originally sent by Stefan. v3: - Patch 6: * check the byte received in the recv_byte() * use

I''m a newb here and probably shouldn''t be using Rails3 yet to start with, but for some reason I was feeling adventurous. I''m also learning to use rspec along the way and things ''were'' working out with my ''rake spec'' until I tried to follow some examples for test Authlogic with rspec. I ''think'' what started the

The vsock_diag.ko module already has a test suite but the core AF_VSOCK functionality has no tests. This patch series adds several test cases that exercise AF_VSOCK SOCK_STREAM socket semantics (send/recv, connect/accept, half-closed connections, simultaneous connections). Stefan: Do you think we should have a single application or is better to split it in single tests (e.g.

On my current project I needed to create a stub that responded correctly to the id message. Here''s the change I put into my copy of head. Index: lib/mocha/mock_methods.rb =================================================================== --- lib/mocha/mock_methods.rb (revision 1114) +++ lib/mocha/mock_methods.rb (working copy) @@ -68,6 +68,7 @@ method_names =

I am trying to check the size of an array in a newly created object, and am getting an "undefined method" error. I have written a minimal test case. Can someone spot the issue here? I''m sure I''m missing something simple.... I realize that I''m not saving the object to the database, I''ve got a requirement to create and manipulate it in memory before

I upgraded a working app from rails 2.1 to 2.3.2. Now when I run rake test:units I get this error: /usr/lib/ruby/gems/1.8/gems/ activesupport-2.3.2/lib/active_support/test_case.rb:17: superclass mismatch for class TestCase (TypeError) I generated a new test app and all tests run OK. For the upgrade I ran rake:update and renamed the class in test_helper to ActiveSupport::TestCase. Also renamed

Adam, Please find the attached test case (run with ToT opt -O3). As you can see, `y_body` successfully is vectorized, though %33 and %46 are deemed MayAlias despite their exclusive use in loads ands stores marked with `llvm.mem.parallel_loop_access`. Many Thanks, Josh On Thu, Mar 19, 2015 at 12:55 PM, Adam Nemet <anemet at apple.com> wrote: > > > On Mar 19, 2015, at 9:43 AM,

See also the 32bit build failures on Debian: https://buildd.debian.org/status/package.php?p=dovecot There are some compiler warnings on 32bit architectures in test-mech.c test-mech.c: In function ?test_mechs?: test-mech.c:326:61: warning: format ?%lu? expects argument of type ?long unsigned int?, but argument 4 has type ?unsigned int? [-Wformat=] 326 | const char *testname =

On 8/13/20 10:56 AM, Aki Tuomi wrote: > >> On 13/08/2020 11:31 Michael Str?der <michael at stroeder.com> wrote: >> I'm trying to update openSUSE package on OBS [1] which builds for >> various OS versions and hardware platforms. To me it seems that a test >> fails on 32bit platforms: >> >> Info: invalid token 3: structure length disagrees with data

...IT_FAILURE); >+ } >+ >+ if (shutdown(fd, SHUT_RD)) { >+ perror("shutdown"); >+ exit(EXIT_FAILURE); >+ } >+ >+ control_writeln("SHUTRDDONE"); >+ control_expectln("CLIENTDONE"); >+ >+ close(fd); >+} >+ > static struct test_case test_cases[] = { > { > .name = "SOCK_STREAM connection reset", >@@ -1250,6 +1378,16 @@ static struct test_case test_cases[] = { > .run_client = test_seqpacket_msg_peek_client, > .run_server = test_seqpacket_msg_peek_server, > }, >+ { >+ .name = "SOCK_STREAM SHUT...

...t failing. >+ exit(EXIT_FAILURE); >+ } Moving the pointer correctly, I would also check that there is HELLOWORLD in the buffer. Thanks for adding tests in this suite! Stefano >+ >+ control_writeln("REPLY1"); >+ >+ close(fd); >+} >+ > static struct test_case test_cases[] = { > { > .name = "SOCK_STREAM connection reset", >@@ -1038,6 +1114,11 @@ static struct test_case test_cases[] = { > .run_client = test_seqpacket_inv_buf_client, > .run_server = test_seqpacket_inv_buf_server, > }, >+ { >+ .name = "SOCK_STREAM virtio...

I''m using rails 2.0.1 now. Here is the step for generate the error 1. Create rails project name demo "rails demo" 2. I create model name "Tester" using command "ruby script/generate model Tester name:string description:text" 3. create database (after change username and password) "rake db:create:all" 4. migrate database, both development and

Hi, I have doubt in executing raw.write tests using lxc-execute. When I execute it without lxc-execute it works fine i.e it performs raw.write testing. command :: root at nishant:/home/nishant/Desktop/samba-4.0.0alpha15# bin/smbtorture //localhost/ubuntu -Ubase%base_system raw.write This command works fine. We can see the o/p of this also,

Test case attached. It is not a test case that works within the llvm test-suite yet, but it does demonstrate the problem. I would like some advice on how to modify this test_case so that it can be added to the automated llvm test cases. On 15 September 2013 23:02, David Majnemer <david.majnemer at gmail.com> wrote: > The attached patch includes no test-case and isn't consistent

The attached patch includes no test-case and isn't consistent with the rest of the file: - constants should be on the right hand side of comparisons - the braces around your single line 'if' aren't needed. On Sun, Sep 15, 2013 at 2:39 PM, James Courtier-Dutton < james.dutton at gmail.com> wrote: > I attach a patch that fixes this bug. Applies to llvm 3.4svn > >

Guys, I''ve created a plugin, i wanna put my automated test there. However, I got bad file descriptor error when i run the test like normal unit test file: "ruby plugins/acts_as_fox/test/acts_as_fox_test.rb" How to test a plugin? Also, is it right to say that I should only put my unit tests (but not functional test for example) for the plugin in the plugin test folder?

On 13/08/20 9:16 pm, Michael Str?der wrote: > On 8/13/20 10:56 AM, Aki Tuomi wrote: >> >>> On 13/08/2020 11:31 Michael Str?der <michael at stroeder.com> wrote: >>> I'm trying to update openSUSE package on OBS [1] which builds for >>> various OS versions and hardware platforms. To me it seems that a test >>> fails on 32bit platforms: > >

On 18/08/20 2:15 pm, Peter wrote: > I'm getting the same issue on a CentOS 6 i386 build: > > test-mech.c:371: Assert(#1) failed: strcmp(test_case->username,username) > ??????? "testuser" != NULL > test-mech.c:380: Assert(#1) failed: request->failed == FALSE > auth mech APOP 2/84 .................................................. : > FAILED > >

Below every page in the browser i get: "Loaded suite dispatch.cgi Started Finished in 0.000225 seconds. 0 tests, 0 assertions, 0 failures, 0 errors" I''m not sure if i changed something or someone else did it, but now i don''t know how to get rid of it. It has something to do with testing, right? How to switch it off? -- Posted via http://www.ruby-forum.com/.

Lucene''s standard analyzer splits words separater with underscores. Ferret doesn''t do this. For example, if I create an index with only document ''test_case'' and search for ''case'' it doesn''t find anything. Lucene on the other hand finds it. The same story goes for words separated by colons. Which analyzer should I use to emulate