Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • WSL Setup (Linux for Windows) (windows only)
  • Docker environment (Docker desktop started in windows)
  • Docker image of latest CPS-NCMP  (mvn clean install)
  • Docker image of latest DMI-Plugin  (mvn clean install)

Run CSIT

Navigate to cps/csit directory.


Warning

It is recommended to either:

  1. clone CPS into a folder on WSL and run scripts from there. The reason for this is that when using /mnt in WSL to navigate to your local folder (e.g. windows) the file formatting causes issues and the scripts don't run.
  2. Copy CPS folder to WSL. If you choose this you will need to run the following command to change the file formatting.  
Code Block
languagebash
find . -type f -print0 | xargs -0 dos2unix




Run the following script

Code Block
languagebash
sudo bash run-project-csit.sh

Note - The first time this runs it will download all the libraries defined in the CSTI CSIT scripts. This may take awhile be patient (smile)

...

Code Block
languagebash
python3 -m robot.run -N ${TESTPLAN} -v WORKSPACE:/tmp ${ROBOT_VARIABLES} ${TESTOPTIONS} ${SUITES}

Run scripts again


python setup.py egg_info did not run successfully

Problem

Code Block
Collecting robotframework-selenium2library
  Using cached robotframework-selenium2library-1.8.0.tar.gz (118 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error
  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [11 lines of output]
      /usr/lib/python3/dist-packages/requests/__init__.py:89: RequestsDependencyWarning: urllib3 (1.26.12) or chardet (3.0.4) doesn't match a supported version!
        warnings.warn("urllib3 ({}) or chardet ({}) doesn't match a supported "
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-629q8t42/robotframework-selenium2library_b2892f832c9f4471a4b59409ca658b27/setup.py", line 7, in <module>
          from ez_setup import use_setuptools
        File "/tmp/pip-install-629q8t42/robotframework-selenium2library_b2892f832c9f4471a4b59409ca658b27/src/ez_setup.py", line 106
          except pkg_resources.VersionConflict, e:
                                              ^
      SyntaxError: invalid syntax
      [end of output]
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed


Solution

Update the version in the pylibs.txt file which we use to keep track of the libraries required to run the CSITs.

Path : cps/csit/pylibs.txt

Code Block
[OLD]  robotframework-selenium2library         
[NEW]  robotframework-selenium2library==3.0.0   

Unable to find include-raw-integration-install-robotframework-py3.sh

Code Block
Cloning into 'ci-management'...
remote: Counting objects: 1, done
remote: Total 33485 (delta 0), reused 33485 (delta 0)
Receiving objects: 100% (33485/33485), 5.32 MiB | 8.69 MiB/s, done.
Resolving deltas: 100% (24180/24180), done.
++ source /tmp/ci-management/jjb/integration/include-raw-integration-install-robotframework-py3.sh
+++ set -eu pipefail
+++ . /root/lf-env.sh
/tmp/ci-management/jjb/integration/include-raw-integration-install-robotframework-py3.sh: line 16: /root/lf-env.sh: No such file or directory
++++ on_exit
++++ rc=1
++++ [[ -n /mnt/c/Users/LeeAnjellaMacabuhay/Documents/userStories/1393/cps/csit ]]
++++ [[ -n /tmp/tmp.ooyImAc0MW-robot-workdir ]]
++++ rsync -av /tmp/tmp.ooyImAc0MW-robot-workdir/ /mnt/c/Users/LeeAnjellaMacabuhay/Documents/userStories/1393/cps/csit/archives/plans/cps
sending incremental file list
./

Solution 

Path: csit/prepare-csit.sh replace the OLD script with the new one.

Code Block
[OLD] source /tmp/ci-management/jjb/integration/include-raw-integration-install-robotframework-py3.sh
[NEW] source ${WORKSPACE}/install-robotframework.sh

System time out of Sync

If there is further issues downloading libraries due to the system date being out of sync with windows issue the following command and run the scripts again.

...