You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Docker test and location folder inside the docker image for the Java Piscine DistinctSubstringlength subject is misspelled.
When running test - docker cannot find tester and returns:
"cp: can't stat '/app/tests/DistinctSubstringLength_test/*.java': No such file or directory"
Users
Anyone running/passing Java Piscine
Severity
(⚠️ critical).
Type
(⚙️ functionality)
To Reproduce
Steps to reproduce the behavior:
Run the test.
Workarounds
Test and it's folder inside docker container is named wrong e.g. "DistinctSubstringLenght_test"
Need to change them to required "DistinctSubstringLength_test"
Expected behavior
Run and execute the test for the subject.
Attachments
Desktop (please complete the following information):
Ubuntu 24.04.1 LTS
Smartphone (please complete the following information):
NA
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Docker test and location folder inside the docker image for the Java Piscine DistinctSubstringlength subject is misspelled.
When running test - docker cannot find tester and returns:
"cp: can't stat '/app/tests/DistinctSubstringLength_test/*.java': No such file or directory"
Users
Anyone running/passing Java Piscine
Severity⚠️ critical).
(
Type
(⚙️ functionality)
To Reproduce
Steps to reproduce the behavior:
Run the test.
Workarounds
Test and it's folder inside docker container is named wrong e.g. "DistinctSubstringLenght_test"
Need to change them to required "DistinctSubstringLength_test"
Expected behavior
Run and execute the test for the subject.
Attachments
Desktop (please complete the following information):
Ubuntu 24.04.1 LTS
Smartphone (please complete the following information):
NA
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: