[mcepl]

Sometimes it’s useful to have the tests that use the network marked so they can be skipped easily when we know the network is not available.

This is useful for example on SUSE and openSUSE’s build servers. When building our packages the network is disabled so we can assure reproducible builds (among other benefits). With this mark, it’s easier to skip tests that can not succeed.

[Copilot]

🟡 Changes recommended

The net marker leaves socket-dependent tests and a daemon-launching parameter unmarked, so pytest -m 'not net' still attempts network access on socket-restricted builders.

1 open issue

• Mark all loopback-dependent tests with the net marker · New

What changed in this PR

GitHub Copilot: This PR adds a pytest net marker so builders with networking disabled can exclude marked tests using pytest -m 'not net'.

Changes:

• Registers net as a supported pytest marker.
• Marks three tests that use the remote-repository daemon helper.

File	Description
test/​test_remote.py	Marks two remote-operation tests as network-dependent.
test/​test_base.py	Imports pytest and marks the remote-repository helper test.
pyproject.toml	Registers and describes the net marker.

_{Review effort: Balanced}

[Byron]

Sure, why not.

It's a bit strange that GitPython needs external network access, and I am looking into this.
From what I can tell right now, plenty of annotations are missing, so it's strange this subset works for you. Maybe there is more about it.

Will have to supersede the PR as I can't push into it.

[Byron]

Superseded by #2338 (which includes this commit)