Skip to content

fix: add fields for browser monitors via config !! (#1000) #1003

fix: add fields for browser monitors via config !! (#1000)

fix: add fields for browser monitors via config !! (#1000) #1003

Triggered via push February 14, 2025 16:56
Status Success
Total duration 11m 36s
Artifacts 1

e2e.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
8.5.2 e2e test synthetics - browser - inline ► 8.5.2 e2e test synthetics - browser - inline create an browser monitor ► create an browser monitor: __tests__/e2e/junit_8.5.2-SNAPSHOT.xml#L0
Failed test found in: __tests__/e2e/junit_8.5.2-SNAPSHOT.xml __tests__/e2e/junit_8.5.2-SNAPSHOT.xml __tests__/e2e/junit_8.5.2-SNAPSHOT.xml Error: TimeoutError: page.waitForSelector: Timeout 10000ms exceeded. Call log: - waiting for locator('[data-test-subj="packagePolicyNameInput"]') to be visible
test
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.
test
Additionally, the attachment-level `fallback` argument is missing in the request payload for a chat.postMessage call - To avoid this warning, it is recommended to always provide a top-level `text` argument when posting a message. Alternatively, you can provide an attachment-level `fallback` argument, though this is now considered a legacy field (see https://api.slack.com/reference/messaging/attachments#legacy_fields for more details).
test
Restore cache failed: Dependencies file is not found in /home/runner/work/synthetics/synthetics. Supported file pattern: go.sum

Artifacts

Produced during runtime
Name Size
test-results
1.11 KB