Correctly handle different javascript realms/documents #596

Sign in to view logs

Re-run triggered July 19, 2024 16:31

luin

#4330

edave64:feature/multi-realm

Status Success

Total duration 2m 10s

Artifacts –

pull-request.yml

on: pull_request

test / E2E Tests

test / Fuzz Tests

Matrix: test / Unit Tests

Annotations

4 warnings

test / Unit Tests (chromium)

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

test / Unit Tests (firefox)

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

test / Unit Tests (webkit)

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

test / E2E Tests

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, coactions/setup-xvfb@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/