Make WordPress Core

Changeset 59635


Ignore:
Timestamp:
01/16/2025 08:19:28 PM (6 months ago)
Author:
desrosj
Message:

Build/Test Tools: Add input for disabling AppArmor.

Old branches requiring outdated versions of Chromium to run JavaScript tests have recently started failing as a result of the ubuntu-latest container being updated to point to ubuntu-24.

This introduces a new input to the reusable JavaScript testing workflow to allow a fix to be used without having to update Chromium or tests in these branches.

Props swissspidy.
See #62808.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/.github/workflows/reusable-javascript-tests.yml

    r59354 r59635  
    66on:
    77  workflow_call:
     8    inputs:
     9      disable-apparmor:
     10        description: 'Whether to disable AppArmor.'
     11        required: false
     12        type: 'boolean'
     13        default: false
    814
    915jobs:
     
    4551        run: npm ci
    4652
     53      # Older branches using outdated versions of Puppeteer fail on newer versions of the `ubuntu-24` image.
     54      # This disables AppArmor in order to work around those failures.
     55      #
     56      # See https://issues.chromium.org/issues/373753919
     57      # and https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md
     58      - name: Disable AppArmor
     59        if: ${{ inputs.disable-apparmor }}
     60        run: echo 0 | sudo tee /proc/sys/kernel/apparmor_restrict_unprivileged_userns
     61
    4762      - name: Run QUnit tests
    4863        run: npm run grunt qunit:compiled
Note: See TracChangeset for help on using the changeset viewer.