Skip to content
Snippets Groups Projects

ci(dedal): implement coverage calculation for the library

As part of this implementation, the test jobs in the CI/CD pipeline have been split into two:

  • Unit tests – These complete in a few minutes (1-2 minutes), providing quick feedback to the developer.

  • Integration tests – These take significantly longer (20-30 minutes), ensuring a thorough validation of the system.

Parent artefact: https://tvb-projects.atlassian.net/browse/VT-87

Edited by Jithu Murugan

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Author Developer

    @adrianciu For your information, I will revert the last two commits, which were added solely to pinpoint the commands causing the pipeline to hang!

  • Jithu Murugan added 1 commit

    added 1 commit

    • e0262adc - - Commented the failing tests to verify the coverage calculation

    Compare with previous version

  • Jithu Murugan added 3 commits

    added 3 commits

    • 6e2f574f - Revert "- Commented the failing tests to verify the coverage calculation"
    • 4491132f - Revert "- Added a 10 minute timeout for testing if any specific command hangs...
    • 997d22b0 - Revert "- Added a 10 minute timeout for testing if any specific command hangs...

    Compare with previous version

  • 1 1 stages:
    2 2 - test
    3 3 - build
    4 - coverage_report
    4 5
    5 6 variables:
    6 7 BUILD_ENV_DOCKER_IMAGE: docker-registry.ebrains.eu/esd/tmp:latest
    7 8
    9 default:
    10 before_script:
    11 - chmod +x dedal/utils/bootstrap.sh
    12 - ./dedal/utils/bootstrap.sh
    13 - pip install -e .[test]
    • Comment on lines +11 to +13

      Hmm, I would have expected that we are "self-hosting" (i.e. use spack for managing the dependencies (except for the very basic base image things like wget/curl/patch/diff/make/base compiler))?

      (Also below in the unit_tests stage.)

      Edited by Eric Müller
    • Author Developer

      @emuller This is not Spack bootstrapping; rather, it is the installation of pre-requisites required for the Spack. Since we are testing Spack-related functionalities as part of unit and integration tests, all necessary dependencies are installed beforehand.

      You can review the actual script here: Bootstrap Script.

      Does this address your concern?

      Edited by Jithu Murugan
    • Author Developer

      @emuller Could you resolve this comment if the response adequately addresses your concern?

    • Please register or sign in to reply
  • Jithu Murugan added 1 commit

    added 1 commit

    • 84d30a75 - - Added .dedal.log also as a job artefact

    Compare with previous version

  • Jithu Murugan added 19 commits

    added 19 commits

    • 84d30a75...e11cb8d4 - 18 commits from branch VT-70-function-Migrate-Spack-env-setup-into-ESD-repo-with-buildcache
    • 911e73ff - Merge branch...

    Compare with previous version

  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Please register or sign in to reply