Switch to GitLab CI

Created on 8 January 2024, about 1 year ago
Updated 26 February 2024, 11 months ago

Need to eventually switch this project to use GitLab CI instead of DrupalCI.

πŸ“Œ Task
Status

Active

Version

10.2

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States eojthebrave Minneapolis, MN

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @eojthebrave
  • πŸ‡ΊπŸ‡ΈUnited States eojthebrave Minneapolis, MN
  • πŸ‡ΊπŸ‡ΈUnited States eojthebrave Minneapolis, MN

    Merging this initial pass at tests in so we can run them. This configuration should restrict the tests to just being run manually instead of running on every MR since we only use them to create screenshots and not really to test the module itself.

  • Merge request !3Draft: Resolve #3413260 "Ci fix" β†’ (Open) created by eojthebrave
  • πŸ‡ΊπŸ‡ΈUnited States eojthebrave Minneapolis, MN

    I've got the tests running in GitLab CI now and with the exception of some deprecation notices they are passing. However the job fails because GitLab CI doesn't provide as much space for saving testing artifacts as this job uses. See errors from a recent run:

    Unsilenced deprecation notices (9)
    Remaining self deprecation notices (7)
    Remaining direct deprecation notices (3)
    Remaining indirect deprecation notices (1)
    Other deprecation notices (1)
    Fail      run-tests. Unknown              0 Unknown                            
        FATAL
        Drupal\Tests\user_guide_tests\FunctionalJavascript\UserGuideDemoTestCa:
        test runner returned a non-zero error code (2).
    ---- Drupal\Tests\user_guide_tests\FunctionalJavascript\DrupalScreenshotTest ----
    Status    Group      Filename          Line Function                            
    --------------------------------------------------------------------------------
    Pass      Other      DrupalScreenshotT   27 Drupal\Tests\user_guide_tests\Funct
        
    $ cp /var/log/apache2/test.apache.access.log $CI_PROJECT_DIR/apache.access.log.txt
    $ cp /var/log/apache2/test.apache.error.log $CI_PROJECT_DIR/apache.error.log.txt
    $ exit $EXIT_CODE
    Uploading artifacts for failed job
    00:15
    Uploading artifacts...
    WARNING: junit.xml: no matching files. Ensure that the artifact path is relative to the working directory (/builds/project/user_guide_tests) 
    /builds/project/user_guide_tests/web/sites/default/files/simpletest: found 25 matching artifact files and directories 
    /builds/project/user_guide_tests/web/sites/simpletest/browser_output: found 5167 matching artifact files and directories 
    apache.access.log.txt: found 1 matching artifact files and directories 
    apache.error.log.txt: found 1 matching artifact files and directories 
    ERROR: Uploading artifacts as "archive" to coordinator... 413 Request Entity Too Large  id=909322 responseStatus=413 Request Entity Too Large status=413 token=glcbt-64
    FATAL: too large                                   
    Cleaning up project directory and file based variables
    00:01
    ERROR: Job failed: command terminated with exit code 1
    mand terminated with exit code 1
    

    This is probably because the test suite saves DB snapshots of all the chapters so that it's easier to debug and only run certain sections of the tests. I think there are two possible solutions:

    - Increase the GitLab max allowed size of artifacts for this project
    - Disable saving of backups by default, and instead make that an option for when the tests are run locally

Production build 0.71.5 2024