search for: check_fail

Displaying 19 results from an estimated 19 matches for "check_fail".

2023 Mar 28
2
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
...r 20, 2023 at 10:44, Ido Schimmel <idosch at nvidia.com> wrote: > >> + $MZ $swp1 -c 1 -p 128 -t udp "sp=54321,dp=12345" \ > >> + -a $mac -b `mac_get $h2` -A 192.0.2.1 -B 192.0.2.2 -q > >> + tc_check_packets "dev $swp2 egress" 1 1 > >> + check_fail $? "Dynamic FDB entry did not age out" > > > > Shouldn't this be check_err()? After the FDB entry was aged you want to > > make sure that packets received via $swp1 with SMAC being $mac are no > > longer forwarded by the bridge. > > I was thinking that c...
2023 Mar 26
1
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
On Mon, Mar 20, 2023 at 10:44, Ido Schimmel <idosch at nvidia.com> wrote: >> + $MZ $swp1 -c 1 -p 128 -t udp "sp=54321,dp=12345" \ >> + -a $mac -b `mac_get $h2` -A 192.0.2.1 -B 192.0.2.2 -q >> + tc_check_packets "dev $swp2 egress" 1 1 >> + check_fail $? "Dynamic FDB entry did not age out" > > Shouldn't this be check_err()? After the FDB entry was aged you want to > make sure that packets received via $swp1 with SMAC being $mac are no > longer forwarded by the bridge. I was thinking that check_fail() will pass when tc_...
2023 Mar 28
1
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
...:44, Ido Schimmel <idosch at nvidia.com> wrote: >> >> + $MZ $swp1 -c 1 -p 128 -t udp "sp=54321,dp=12345" \ >> >> + -a $mac -b `mac_get $h2` -A 192.0.2.1 -B 192.0.2.2 -q >> >> + tc_check_packets "dev $swp2 egress" 1 1 >> >> + check_fail $? "Dynamic FDB entry did not age out" >> > >> > Shouldn't this be check_err()? After the FDB entry was aged you want to >> > make sure that packets received via $swp1 with SMAC being $mac are no >> > longer forwarded by the bridge. >> >&g...
2023 Mar 20
1
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
...and how it can arrive at the egress of $swp2. > + > + sleep $((LOW_AGEING_TIME / 100 + 10)) > + > + $MZ $swp1 -c 1 -p 128 -t udp "sp=54321,dp=12345" \ > + -a $mac -b `mac_get $h2` -A 192.0.2.1 -B 192.0.2.2 -q > + tc_check_packets "dev $swp2 egress" 1 1 > + check_fail $? "Dynamic FDB entry did not age out" Shouldn't this be check_err()? After the FDB entry was aged you want to make sure that packets received via $swp1 with SMAC being $mac are no longer forwarded by the bridge. Also, I suggest executing 'bridge fdb get' to make sure the en...
2023 Mar 30
1
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
...:44, Ido Schimmel <idosch at nvidia.com> wrote: >> >> + $MZ $swp1 -c 1 -p 128 -t udp "sp=54321,dp=12345" \ >> >> + -a $mac -b `mac_get $h2` -A 192.0.2.1 -B 192.0.2.2 -q >> >> + tc_check_packets "dev $swp2 egress" 1 1 >> >> + check_fail $? "Dynamic FDB entry did not age out" >> > >> > Shouldn't this be check_err()? After the FDB entry was aged you want to >> > make sure that packets received via $swp1 with SMAC being $mac are no >> > longer forwarded by the bridge. >> >&g...
2023 Mar 18
1
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
...1 1 + check_err $? "Packet not seen on egress after adding dynamic FDB" + + sleep $((LOW_AGEING_TIME / 100 + 10)) + + $MZ $swp1 -c 1 -p 128 -t udp "sp=54321,dp=12345" \ + -a $mac -b `mac_get $h2` -A 192.0.2.1 -B 192.0.2.2 -q + tc_check_packets "dev $swp2 egress" 1 1 + check_fail $? "Dynamic FDB entry did not age out" + + 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
2023 Mar 30
1
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
...t;idosch at nvidia.com> wrote: > >> >> + $MZ $swp1 -c 1 -p 128 -t udp "sp=54321,dp=12345" \ > >> >> + -a $mac -b `mac_get $h2` -A 192.0.2.1 -B 192.0.2.2 -q > >> >> + tc_check_packets "dev $swp2 egress" 1 1 > >> >> + check_fail $? "Dynamic FDB entry did not age out" > >> > > >> > Shouldn't this be check_err()? After the FDB entry was aged you want to > >> > make sure that packets received via $swp1 with SMAC being $mac are no > >> > longer forwarded by the brid...
2007 Nov 12
0
[PATCH]Minor fix for find_search_start
...last); } - cache = btrfs_find_block_group(root, cache, last, data, 0); + if (!full_scan) + cache = btrfs_find_block_group(root, cache, last, data, 0); *cache_ret = cache; cache_miss = 0; goto again; @@ -955,8 +957,8 @@ static int find_free_extent(struct btrfs path = btrfs_alloc_path(); check_failed: - search_start = find_search_start(root, &block_group, - search_start, total_needed, data); + search_start = find_search_start(root, &block_group, search_start, + total_needed, data, full_scan); cached_start = search_start; btrfs_init_path(path);
2020 Mar 26
12
Upgrading LLVM's minimum required CMake version
...in BUILD_RPATH and INSTALL_RPATH CMake 3.17 (released March 20th 2020): * Ninja Multi-Config generator, which among other things would greatly simplify LLVM_OPTIMIZED_TABLEGEN * foreach(ZIP_LISTS) added to iterate multiple lists simultaneously * New message() keywords CHECK_START, CHECK_PASS, and CHECK_FAIL * INSTALL_NAME_DIR supports generator expressions Our build system is incredibly complex, and many of these features can be used to clean it up and make it much more maintainable. I would personally like us to at least bump up to CMake 3.12. I also do think it's worth establishing a policy and...
2020 Mar 26
4
Upgrading LLVM's minimum required CMake version
...gt;> CMake 3.17 (released March 20th 2020): >> * Ninja Multi-Config generator, which among other things would greatly simplify LLVM_OPTIMIZED_TABLEGEN >> * foreach(ZIP_LISTS) added to iterate multiple lists simultaneously >> * New message() keywords CHECK_START, CHECK_PASS, and CHECK_FAIL >> * INSTALL_NAME_DIR supports generator expressions >> >> Our build system is incredibly complex, and many of these features can be used to clean it up and make it much more maintainable. I would personally like us to at least bump up to CMake 3.12. I also do think it's worth...
2020 Apr 02
2
Upgrading LLVM's minimum required CMake version
...in BUILD_RPATH and INSTALL_RPATH CMake 3.17 (released March 20th 2020): * Ninja Multi-Config generator, which among other things would greatly simplify LLVM_OPTIMIZED_TABLEGEN * foreach(ZIP_LISTS) added to iterate multiple lists simultaneously * New message() keywords CHECK_START, CHECK_PASS, and CHECK_FAIL * INSTALL_NAME_DIR supports generator expressions Our build system is incredibly complex, and many of these features can be used to clean it up and make it much more maintainable. I would personally like us to at least bump up to CMake 3.12. I also do think it's worth establishing a policy and...
2020 Apr 02
2
Upgrading LLVM's minimum required CMake version
...in BUILD_RPATH and INSTALL_RPATH CMake 3.17 (released March 20th 2020): * Ninja Multi-Config generator, which among other things would greatly simplify LLVM_OPTIMIZED_TABLEGEN * foreach(ZIP_LISTS) added to iterate multiple lists simultaneously * New message() keywords CHECK_START, CHECK_PASS, and CHECK_FAIL * INSTALL_NAME_DIR supports generator expressions Our build system is incredibly complex, and many of these features can be used to clean it up and make it much more maintainable. I would personally like us to at least bump up to CMake 3.12. I also do think it's worth establishing a policy and...
2020 Mar 26
2
Upgrading LLVM's minimum required CMake version
...in BUILD_RPATH and INSTALL_RPATH CMake 3.17 (released March 20th 2020): * Ninja Multi-Config generator, which among other things would greatly simplify LLVM_OPTIMIZED_TABLEGEN * foreach(ZIP_LISTS) added to iterate multiple lists simultaneously * New message() keywords CHECK_START, CHECK_PASS, and CHECK_FAIL * INSTALL_NAME_DIR supports generator expressions Our build system is incredibly complex, and many of these features can be used to clean it up and make it much more maintainable. I would personally like us to at least bump up to CMake 3.12. I also do think it's worth establishing a policy and...
2020 Apr 08
3
Upgrading LLVM's minimum required CMake version
...gt;> CMake 3.17 (released March 20th 2020): >> * Ninja Multi-Config generator, which among other things would greatly simplify LLVM_OPTIMIZED_TABLEGEN >> * foreach(ZIP_LISTS) added to iterate multiple lists simultaneously >> * New message() keywords CHECK_START, CHECK_PASS, and CHECK_FAIL >> * INSTALL_NAME_DIR supports generator expressions >> >> Our build system is incredibly complex, and many of these features can be used to clean it up and make it much more maintainable. I would personally like us to at least bump up to CMake 3.12. I also do think it's wort...
2020 Apr 04
3
Upgrading LLVM's minimum required CMake version
...h 2020): > * Ninja Multi-Config generator, which among other things would > greatly simplify LLVM_OPTIMIZED_TABLEGEN > * foreach(ZIP_LISTS) added to iterate multiple lists > simultaneously > * New message() keywords CHECK_START, CHECK_PASS, and CHECK_FAIL > * INSTALL_NAME_DIR supports generator expressions > > Our build system is incredibly complex, and many of these > features can be used to clean it up and make it much more > maintainable. I would personally like us to at least bump up > to...
2020 Apr 06
5
Upgrading LLVM's minimum required CMake version
...in BUILD_RPATH and INSTALL_RPATH CMake 3.17 (released March 20th 2020): * Ninja Multi-Config generator, which among other things would greatly simplify LLVM_OPTIMIZED_TABLEGEN * foreach(ZIP_LISTS) added to iterate multiple lists simultaneously * New message() keywords CHECK_START, CHECK_PASS, and CHECK_FAIL * INSTALL_NAME_DIR supports generator expressions Our build system is incredibly complex, and many of these features can be used to clean it up and make it much more maintainable. I would personally like us to at least bump up to CMake 3.12. I also do think it's worth establishing a policy and...
2020 Apr 07
2
Upgrading LLVM's minimum required CMake version
...in BUILD_RPATH and INSTALL_RPATH CMake 3.17 (released March 20th 2020): * Ninja Multi-Config generator, which among other things would greatly simplify LLVM_OPTIMIZED_TABLEGEN * foreach(ZIP_LISTS) added to iterate multiple lists simultaneously * New message() keywords CHECK_START, CHECK_PASS, and CHECK_FAIL * INSTALL_NAME_DIR supports generator expressions Our build system is incredibly complex, and many of these features can be used to clean it up and make it much more maintainable. I would personally like us to at least bump up to CMake 3.12. I also do think it's worth establishing a policy and...
2020 Apr 07
3
Upgrading LLVM's minimum required CMake version
...Make 3.17 (released March 20th 2020): >> * Ninja Multi-Config generator, which among other things would greatly >> simplify LLVM_OPTIMIZED_TABLEGEN >> * foreach(ZIP_LISTS) added to iterate multiple lists simultaneously >> * New message() keywords CHECK_START, CHECK_PASS, and CHECK_FAIL >> * INSTALL_NAME_DIR supports generator expressions >> >> Our build system is incredibly complex, and many of these features can be >> used to clean it up and make it much more maintainable. I would personally >> like us to at least bump up to CMake 3.12. I also do th...
2020 Apr 08
3
Upgrading LLVM's minimum required CMake version
...LL_RPATH > > CMake 3.17 (released March 20th 2020): > * Ninja Multi-Config generator, which among other things would greatly simplify LLVM_OPTIMIZED_TABLEGEN > * foreach(ZIP_LISTS) added to iterate multiple lists simultaneously > * New message() keywords CHECK_START, CHECK_PASS, and CHECK_FAIL > * INSTALL_NAME_DIR supports generator expressions > > Our build system is incredibly complex, and many of these features can be used to clean it up and make it much more maintainable. I would personally like us to at least bump up to CMake 3.12. I also do think it's worth establishi...