Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Re-consider the docker directory re-mapping #462

Open
cecille opened this issue Oct 3, 2024 · 3 comments
Open

[Feature] Re-consider the docker directory re-mapping #462

cecille opened this issue Oct 3, 2024 · 3 comments

Comments

@cecille
Copy link

cecille commented Oct 3, 2024

Feature description

I'm not sure if this is a feature or a bug, but when the TH starts the docker, it re-maps a bunch of directories. Folks that have experience running these tests mostly know where these files are located in the SDK, but the remapping changes that. It also means you can't just run a find in the TH AND you can't just open a docker because that already involves knowing how the remapping was done. It just makes it really hard to find stuff.

Use Cases

  • use find command in TH, files are located there.

Test Cases

No response

Additional Information

No response

@rquidute
Copy link
Contributor

rquidute commented Dec 4, 2024

Hi @cecille, currently the TH->SDK Image mappings are the following:
SDK Image (Docker) -> TH (Raspi)

  • /root/python_testing -> /home/ubuntu/certification-tool/backend/test_collections/matter/sdk_tests/sdk_checkout/python_testing
  • /paa-root-certs -> /var/paa-root-certs
  • /credentials/development -> /var/credentials/development

What would be your suggestion?

@rquidute
Copy link
Contributor

rquidute commented Dec 4, 2024

@cecille Adding the mapping provided in the note above in User Guide works for you?

@cecille
Copy link
Author

cecille commented Dec 9, 2024

They should definitely be added to the user guide, but it still ends up being a bit weird because the arguments to some of the scripts are then different between the CI and the test harness.

how did stuff end up so scattered around anyway such that it needs to be re-mapped?

I'd suggest checking with the ATLs to see how they feel about this and what would work for them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants