search for: log_test

Displaying 9 results from an estimated 9 matches for "log_test".

2009 Feb 02
2
did_not_yield
...d do. Here is what I get in the log: Processing ScannsController#status (for 127.0.0.1 at 2009-02-02 14:24:25) [GET] Session ID: 595e081a5e726f0594f83652c3c2a9d5 Filter chain halted as [#<ActionController::Filters::AroundFilter:0x20470e8 @kind=:filter, @identifier=nil, @options={}, @method=:log_test>] did_not_yield. Completed in 0ms (DB: 12) | [http://127.0.0.1/scanns/status] I think what it says is nothing happened ? class ApplicationController < ActionController::Base ... protected ## attention, below here, all methods are PROTECTED def log_test session[:auth] ? (...
2023 Mar 18
1
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
...ls/testing/selftests/net/forwarding/bridge_locked_port.sh +++ b/tools/testing/selftests/net/forwarding/bridge_locked_port.sh @@ -14,6 +14,7 @@ ALL_TESTS=" NUM_NETIFS=4 CHECK_TC="no" source lib.sh +source tc_common.sh h1_create() { @@ -319,6 +320,41 @@ locked_port_mab_flush() log_test "Locked port MAB FDB flush" } +# Test of dynamic FDB entries. +locked_port_dyn_fdb() +{ + local mac=00:01:02:03:04:05 + local ageing_time + + RET=0 + ageing_time=$(bridge_ageing_time_get br0) + tc qdisc add dev $swp2 clsact + ip link set dev br0 type bridge ageing_time $LOW_AGEING_TIME...
2008 Jun 12
1
how do I mock the Rails Logger with should_receive?
Hey Guys, I''m trying to mock the Rails Logger for the following code: ... rescue TimeoutError => error $logger.error("#{self.name} Timeout for #{path}: #{error}") and return rescue SocketError => error $logger.error("#{self.name} SocketError for #{path}: #{error}") and return rescue StandardError => error
2023 Jan 26
1
[Bridge] [PATCH net-next 09/16] selftests: forwarding: Move IGMP- and MLD-related functions to lib
...: Aux Data Len - )"00:01:"$( : Number of Sources - )"ef:01:01:01:"$( : Multicast Address - 239.1.1.1 - )"c0:00:02:02"$( : Source Address - 192.0.2.2 - ) - - echo $igmpv3 -} - ctrl_igmpv3_is_in_test() { RET=0 @@ -1077,35 +1057,6 @@ ctrl_igmpv3_is_in_test() log_test "IGMPv3 MODE_IS_INCLUE tests" } -mldv2_is_in_get() -{ - local hbh - local icmpv6 - - hbh=$(: - )"3a:"$( : Next Header - ICMPv6 - )"00:"$( : Hdr Ext Len - )"00:00:00:00:00:00:"$( : Options and Padding - ) - - icmpv6=$(: - )"8f:"$( : Ty...
2014 Aug 26
1
Bug#759384: xen: Lack of copyright entry for Vinay Sajip
...copyright lacks information for Vinay Sajip and his permissive license. You can see for which files it should be included: http://codesearch.debian.net/search?prev=0&q=the+name+of+Vinay+Sajip&skip=99, e.g. tools/python/logging/logging-0.4.9.2/* and tools/python/logging/logging-0.4.9.2/test/log_test* -- Dariusz Dwornikowski, Institute of Computing Science, Pozna? University of Technology www.cs.put.poznan.pl/ddwornikowski/ room 2.7.2 BTiCW | tel. +48 61 665 29 41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-s...
2023 May 09
5
[Bridge] [RFC PATCH net-next 0/5] Add layer 2 miss indication and filtering
tl;dr ===== This patchset adds a single bit to the skb to indicate that a packet encountered a layer 2 miss in the bridge and extends flower to match on this metadata. This is required for non-DF (Designated Forwarder) filtering in EVPN multi-homing which prevents decapsulated BUM packets from being forwarded multiple times to the same multi-homed host. Background ========== In a typical EVPN
2023 May 18
5
[Bridge] [PATCH net-next 0/5] Add layer 2 miss indication and filtering
tl;dr ===== This patchset adds a single bit to the skb to indicate that a packet encountered a layer 2 miss in the bridge and extends flower to match on this metadata. This is required for non-DF (Designated Forwarder) filtering in EVPN multi-homing which prevents decapsulated BUM packets from being forwarded multiple times to the same multi-homed host. Background ========== In a typical EVPN
2023 Mar 20
1
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
...dge. Also, I suggest executing 'bridge fdb get' to make sure the entry is no longer present in the bridge FDB. > + > + ip link set dev br0 type bridge ageing_time $ageing_time > + bridge link set dev $swp1 learning off locked off > + tc qdisc del dev $swp2 clsact > + > + log_test "Locked port dyn FDB" > +} > + > trap cleanup EXIT > > setup_prepare > -- > 2.34.1 >
2010 Jun 29
0
Processes hang in /dev/zvol/dsk/poolname
...0 0 0 c7t1d0 ONLINE 0 0 0 logs /dev/zvol/dsk/rpool/puddle_slog ONLINE 0 0 0 zfs list -rt volume puddle NAME USED AVAIL REFER MOUNTPOINT puddle/l2arc 8.25G 538G 7.20G - puddle/log_test 1.25G 537G 1.25G - puddle/temp_cache 4.13G 537G 4.00G - James Dickens http://uadmin.blogspot.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100628/1d27340f/attachment.html>