linux_ns_path contest integration test

[cody-herbst]

Description

part of #361

Implemented the linux_ns_path integration test

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement
• Test updates
• CI/CD related changes
• Other (please describe):

Testing

• Added new unit tests
• Added new integration tests
• Ran existing test suite
• Tested manually (please provide steps)

Related Issues

Fixes #

Additional Context

[Copilot]

Pull Request Overview

This PR implements integration tests for linux namespace path functionality as part of issue #361. The tests verify that containers can correctly inherit namespaces by comparing inodes between unshared processes and container processes.

• Adds comprehensive integration tests for various Linux namespace types (PID, UTS, IPC, Mount, Network)
• Implements a namespace path testing framework with proper cleanup mechanisms
• Integrates the new test module into the existing test suite structure

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File	Description
tests/contest/contest/src/tests/mod.rs	Adds module declaration for the new linux_ns_path test module
tests/contest/contest/src/tests/linux_ns_path/ns_path_test.rs	Implements the core namespace path testing logic with cleanup utilities and test cases
tests/contest/contest/src/tests/linux_ns_path/mod.rs	Module file exposing the test functionality
tests/contest/contest/src/main.rs	Integrates the new test group into the main test runner

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[cody-herbst]

Apologies for all the fix commits. I just notice the "just lint" command

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The parameter should be a slice &[NamespacePath] instead of a reference to a Vec. This is more idiomatic Rust and allows the function to accept both Vec and array references.

Suggested change

	fn create_spec(namespace_path: &Vec<NamespacePath>) -> Spec {
	fn create_spec(namespace_path: &[NamespacePath]) -> Spec {

[Copilot]

The format!() call is unnecessary here. Use anyhow!() directly with format string arguments: anyhow!('could not spawn unshare: {}', e).

Suggested change

	return TestResult::Failed(anyhow!(format!("could not spawn unshare: {}", e)));
	return TestResult::Failed(anyhow!("could not spawn unshare: {}", e));

[Copilot]

The format!() call is unnecessary here. Use anyhow!() directly with format string arguments: anyhow!('could not wait for path {}', namespace_path.path.display()).

Suggested change

	return TestResult::Failed(anyhow!(format!(
	"could not wait for path {}",
	&namespace_path.path.display()
	)));
	return TestResult::Failed(anyhow!(
	"could not wait for path {}",
	&namespace_path.path.display()
	));

[Copilot]

The format!() call is unnecessary here. Use anyhow!() directly with format string arguments: anyhow!('could not get inode of {}: {}', unshared_namespace_path.path.display(), e).

[Copilot]

The format!() call is unnecessary here. Use anyhow!() directly with format string arguments: anyhow!('could not get inode of {}: {}', container_ns_path.display(), e).

Suggested change

	return TestResult::Failed(anyhow!(format!(
	"could not get inode of {}: {}",
	container_ns_path.display(),
	e
	)));
	return TestResult::Failed(anyhow!(
	"could not get inode of {}: {}",
	container_ns_path.display(),
	e
	));