Can anyone help me with this issue. In one of the PR runs, it says the Run Library e2e test failed. However when I follow the Oppia E2E guide and run the command
python -m scripts.run_e2e_tests --suite="library" I did not see the error message.
Does anyone know how can I test locally? I can't replicate the error I am seeing.
python -m scripts.start
Checking if pip is installed on the local machine Collecting six==1.16.0 Using cached six-1.16.0-py2.py3-none-any.whl (11 kB) Installing collected packages: six Successfully installed six-1.16.0 Redis-cli is already installed. ElasticSearch is already installed. Copying Google Cloud SDK modules to third_party/python_libs... Traceback (most recent call last): File "/home/juno/.pyenv/versions/3.7.10/lib/python3.7/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/home/juno/.pyenv/versions/3.7.10/lib/python3.7/runpy.py", line 85, in _run_code exec(code, run_globals) File "/home/juno/Desktop/cs/oss/oppia/scripts/start.py", line 31, in <module> install_third_party_libs.main() File "/home/juno/Desktop/cs/oss/oppia/scripts/install_third_party_libs.py", line 271, in main os.path.join(correct_google_path, 'appengine')) File "/home/juno/.pyenv/versions/3.7.10/lib/python3.7/shutil.py", line 318, in copytree names = os.listdir(src) FileNotFoundError: [Errno 2] No such file or directory: '/home/juno/Desktop/cs/oss/oppia_tools/google-cloud-sdk-335.0.0/google-cloud-sdk/platform/google_appengine/google/appengine'
python -m scripts.start
xvfb-run -a --server-args="-screen 0, 1285x1000x24" python -m scripts.run_e2e_tests --skip-build --skip-install --suite="learnerDashboard" --prod_envand running starting the server using
python -m scripts.start.
allExplorationCardsand it is not empty. However, when I used
console.log()to observe the behavior, it seems that the for loop never gets called and the code inside the for loop never gets executed.
I'm contributing to Oppia during the Hacktoberfest. so excited to start.
I am assigned a task which is removing an unneeded variable called RANGE in python_utils.py file and replace it with its corresponding equivalent in Python 3
I finished my changes and it was time to run the tests to make sure everything is working fine, so I started with the back-end tests. The back-end tests stopped at this part