<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/tests/sys/common, branch release/13.4.0</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=release%2F13.4.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=release%2F13.4.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2024-06-11T06:05:13Z</updated>
<entry>
<title>vnet tests: check for if_bridge.ko</title>
<updated>2024-06-11T06:05:13Z</updated>
<author>
<name>Kristof Provost</name>
<email>kp@FreeBSD.org</email>
</author>
<published>2024-06-04T18:02:18Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=154dd1eaa643ffff4df525dca2e747490df61df3'/>
<id>urn:sha1:154dd1eaa643ffff4df525dca2e747490df61df3</id>
<content type='text'>
A number of tests create a bridge, but did not check if if_bridge.ko is loaded.

We usually get away with that, because `ifconfig bridge create` autoloads the
module, but if we run the tests in a jail (e.g. because of kyua's upcoming
execenv.jail.params feature) we can't load the module and these tests can fail.

Check if the module is loaded, skip the test if it is not.

Reviewed by:	markj
MFC after:	1 week
Event:		Kitchener-Waterloo Hackathon 202406
Differential Revision:	https://reviews.freebsd.org/D45487

(cherry picked from commit 480ad4055314efbfff7eedbb34272031d836ba89)
</content>
</entry>
<entry>
<title>Remove $FreeBSD$: one-line sh pattern</title>
<updated>2023-08-23T17:43:30Z</updated>
<author>
<name>Warner Losh</name>
<email>imp@FreeBSD.org</email>
</author>
<published>2023-08-22T01:32:01Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=023fc80ee38a117fa65b2ccb2abf8bdc7dbd6fd9'/>
<id>urn:sha1:023fc80ee38a117fa65b2ccb2abf8bdc7dbd6fd9</id>
<content type='text'>
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/

Similar commit in main:
(cherry picked from commit d0b2dbfa0ecf)
</content>
</entry>
<entry>
<title>pf tests: properly destroy renamed interfaces</title>
<updated>2023-01-23T02:26:25Z</updated>
<author>
<name>Kajetan Staszkiewicz</name>
<email>vegeta@tuxpowered.net</email>
</author>
<published>2023-01-16T06:19:41Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=fbdde1029e9202cf44ed3ce3e38a4d11e418eda5'/>
<id>urn:sha1:fbdde1029e9202cf44ed3ce3e38a4d11e418eda5</id>
<content type='text'>
The pfsync:pbr tests leaves  lot of interfaces when they finish, making
other tests slower due to long time of loading scapy from pft_ping.py
when more interfaces are present. When both sides of epair are assigned
to jails, they are both removed from created_interfaces.lst and thus
won't be removed during cleanup from this file. An interface assigned to
jail is stored in created_jails.lst but if it is renamed, it won't be
cleaned up either. Furthermore this test uses identical names for
multiple interfaces across multiple jails which after destroying those
jails adds to overall confusion.

To address this issue a new function is provided for renaming interfaces
in jails and storing their new names in created_jails.lst for deletion
during cleanup.

MFC after:	1 week
Sponsored by:	InnoGames GmbH
Differential Revision:	https://reviews.freebsd.org/D38024

(cherry picked from commit ddcdb534b7669f186184baf164e7647d544f7bd6)
</content>
</entry>
<entry>
<title>pf tests: test ALTQ CBQ on top of if_vlan</title>
<updated>2021-09-01T13:27:01Z</updated>
<author>
<name>Kristof Provost</name>
<email>kp@FreeBSD.org</email>
</author>
<published>2021-08-23T14:58:50Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=f610aafaed3c9d95073b156302280d43329c83fd'/>
<id>urn:sha1:f610aafaed3c9d95073b156302280d43329c83fd</id>
<content type='text'>
The main purpose of this test is to verify that we can use ALTQ on top
of if_vlan, but while we're here we also exercise the CBQ code. There's
already a basis test for HFSC, so it makes sense to test another
algorithm while we test if_vlan.

Reviewed by:	donner
MFC after:	1 week
Sponsored by:	Rubicon Communications, LLC ("Netgate")
Differential Revision:	https://reviews.freebsd.org/D31649

(cherry picked from commit e62175df4ec2c8fe2aa2e372f683ddb933768e62)
</content>
</entry>
<entry>
<title>tests: Only log critical errors from scapy</title>
<updated>2021-05-18T10:00:38Z</updated>
<author>
<name>Kristof Provost</name>
<email>kp@FreeBSD.org</email>
</author>
<published>2021-05-12T17:13:40Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=2b8399210bb00c868b4cce86d86fc68a5a0a9121'/>
<id>urn:sha1:2b8399210bb00c868b4cce86d86fc68a5a0a9121</id>
<content type='text'>
Since 2.4.5 scapy started issuing warnings about a few different
configurations during our tests. These are harmless, but they generate
stderr output, which upsets atf_check.

Configure scapy to only log critical errors (and thus not warnings) to
fix these tests.

MFC after:	1 week
Sponsored by:	Rubicon Communications, LLC ("Netgate")

(cherry picked from commit a26e895f3d803cc1f4ee1c2b33c61330998808b9)
</content>
</entry>
<entry>
<title>Add tests verifying IPv4/IPv6 output for TCP/UDP/raw paths.</title>
<updated>2020-03-23T12:21:32Z</updated>
<author>
<name>Alexander V. Chernikov</name>
<email>melifaro@FreeBSD.org</email>
</author>
<published>2020-03-23T12:21:32Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=b4a4a3b82f7a0b3c684ab6470117c47b17a25981'/>
<id>urn:sha1:b4a4a3b82f7a0b3c684ab6470117c47b17a25981</id>
<content type='text'>
Reviewed by:	kp
MFC after:	2 weeks
Differential Revision:	https://reviews.freebsd.org/D24138
</content>
</entry>
<entry>
<title>Add basic IPv4/IPv6 forwarding tests.</title>
<updated>2020-03-10T19:52:19Z</updated>
<author>
<name>Alexander V. Chernikov</name>
<email>melifaro@FreeBSD.org</email>
</author>
<published>2020-03-10T19:52:19Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=d7cdd89777b83f82416f4bb0c84249db63d90686'/>
<id>urn:sha1:d7cdd89777b83f82416f4bb0c84249db63d90686</id>
<content type='text'>
MFC after:	2 weeks
Differential Revision:	https://reviews.freebsd.org/D24002
</content>
</entry>
<entry>
<title>bridge: Basic test case</title>
<updated>2020-02-16T13:16:40Z</updated>
<author>
<name>Kristof Provost</name>
<email>kp@FreeBSD.org</email>
</author>
<published>2020-02-16T13:16:40Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=095aabf7dc814ae96d83bc5327a4b1f2e23be419'/>
<id>urn:sha1:095aabf7dc814ae96d83bc5327a4b1f2e23be419</id>
<content type='text'>
Very basic bridge test: Set up two jails and test that they can pass IPv4
traffic over the bridge.

Reviewed by:	melifaro, philip
Sponsored by:	The FreeBSD Foundation
Differential Revision:	https://reviews.freebsd.org/D23697
</content>
</entry>
<entry>
<title>Add basic IPDIVERT tests.</title>
<updated>2020-02-14T09:36:35Z</updated>
<author>
<name>Alexander V. Chernikov</name>
<email>melifaro@FreeBSD.org</email>
</author>
<published>2020-02-14T09:36:35Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=2207447bf4c3fa03e9dbde829712e0f31e447ba2'/>
<id>urn:sha1:2207447bf4c3fa03e9dbde829712e0f31e447ba2</id>
<content type='text'>
Reviewed by:	lwhsu,kp
Differential Revision:	https://reviews.freebsd.org/D23316
</content>
</entry>
<entry>
<title>pkgbase: Put the sys/common test into the tests package</title>
<updated>2019-09-05T14:14:07Z</updated>
<author>
<name>Emmanuel Vadot</name>
<email>manu@FreeBSD.org</email>
</author>
<published>2019-09-05T14:14:07Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=ea8a4d593bd7fe462131a6d53192b50ddb7eddc3'/>
<id>urn:sha1:ea8a4d593bd7fe462131a6d53192b50ddb7eddc3</id>
<content type='text'>
Every other test is there so do the same for those.

Reviewed by:	bapt, gjb
Differential Revision:	https://reviews.freebsd.org/D21504
</content>
</entry>
</feed>
