Skip to content
📖 Release (stage)

release/1.2.0 #1

Sign in to view logs

release/1.2.0

release/1.2.0 #1

Triggered via push December 17, 2024 17:34
@vlad-dargelvlad-dargel
pushed 37cc980
release/1.2.0
Status Failure
Total duration 27m 0s
Artifacts 5

release-stage.yml

on: push
Release stage tests  /  ...  /  Frontend tests
4m 22s
Release stage tests / frontend-tests / Frontend tests
Release stage tests  /  Approve E2E tests
2s
Release stage tests / Approve E2E tests
Release stage tests  /  ...  /  Build linux
1m 28s
Release stage tests / build-linux / Build linux
Matrix: tests / e2e-linux-test / E2E tests
Release stage tests  /  ...  /  merge-artifacts
0s
Release stage tests / e2e-linux-test / merge-artifacts
builds  /  ...  /  Build linux
builds / build-linux / Build linux
builds  /  ...  /  Build macos
builds / build-macos / Build macos
builds  /  ...  /  Build windows
builds / build-windows / Build windows
Matrix: e2e-linux-tests / E2E tests
Waiting for pending jobs
e2e-linux-tests  /  merge-artifacts
e2e-linux-tests / merge-artifacts
Fit to window
Zoom out
Zoom in

Annotations

27 errors and 7 warnings
Edit Databases ► Verify that user can edit Standalone DB ► Edit Databases Verify that user can edit Standalone DB: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: AssertionError: CA certificate is incorrect: the given combination of arguments (null and string) is invalid for this assertion. You can use an array, a map, an object, a set, a string, or a weakset instead of a string
Formatters ► Verify that user can see highlighted key details in JSON format ► Formatters Verify that user can see highlighted key details in JSON format: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
Formatters ► Verify that user can see highlighted key details in PHP serialized format ► Formatters Verify that user can see highlighted key details in PHP serialized format: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
Formatters ► Verify that user can see highlighted key details in Msgpack format ► Formatters Verify that user can see highlighted key details in Msgpack format: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
Formatters ► Verify that user can see highlighted key details in Protobuf format ► Formatters Verify that user can see highlighted key details in Protobuf format: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
Formatters ► Verify that user can see highlighted key details in Java serialized format ► Formatters Verify that user can see highlighted key details in Java serialized format: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
Formatters ► Verify that user can see highlighted key details in Pickle format ► Formatters Verify that user can see highlighted key details in Pickle format: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
Formatters ► Verify that user can see highlighted key details in Vector 32-bit format ► Formatters Verify that user can see highlighted key details in Vector 32-bit format: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
Formatters ► Verify that user can see highlighted key details in Vector 64-bit format ► Formatters Verify that user can see highlighted key details in Vector 64-bit format: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
Formatters ► Verify that user can edit the values in the key regardless if they are valid in JSON format or not ► Formatters Verify that user can edit the values in the key regardless if they are valid in JSON format or not: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
Formatters ► Verify that user can edit the values in the key regardless if they are valid in Msgpack format or not ► Formatters Verify that user can edit the values in the key regardless if they are valid in Msgpack format or not: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
Release stage tests / e2e-linux-test / E2E tests (1)
Process completed with exit code 1.
Actions with Key List ► Verify that key deleted properly from the list ► Actions with Key List Verify that key deleted properly from the list: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: TimeoutError: Waiting for element to be located By(xpath, //vscode-button[starts-with(@data-testid, 'remove-key-kerovafasb')])
Format switcher functionality ► "before each" hook for "Formatters saved selection" ► Format switcher functionality "before each" hook for "Formatters saved selection": tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
List Key verification ► "before each" hook for "Verify that user can search List element by index" ► List Key verification "before each" hook for "Verify that user can search List element by index": tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: TimeoutError: Waiting for element to be located By(xpath, //*[@data-testid="key-awruvofehe"])
List Key verification for db with version <6.2 ► Verify that user can remove only one element for List for Redis v. <6.2 ► List Key verification for db with version <6.2 Verify that user can remove only one element for List for Redis v. <6.2: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: TimeoutError: Waiting for element to be located By(xpath, //vscode-button[@data-testid='add-key-button'])
Release stage tests / e2e-linux-test / E2E tests (0)
Process completed with exit code 1.
Edit Key values verification ► Verify that user can edit String value ► Edit Key values verification Verify that user can edit String value: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: StaleElementReferenceError: stale element reference: stale element not found in the current frame
Hash Key fields verification ► Verify that tab is closed if Hash was deleted from keys list ► Hash Key fields verification Verify that tab is closed if Hash was deleted from keys list: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: TimeoutError: Waiting for element to be located By(xpath, //vscode-button[starts-with(@data-testid, 'remove-key-hepuglehub')])
Large key details verification ► Verify that user can download String key value as txt file when it has > 5000 characters ► Large key details verification Verify that user can download String key value as txt file when it has > 5000 characters: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: AssertionError: Edit key value button not disabled: expected true to deeply equal false
Set TTL for Key ► Verify that user can specify TTL for Key ► Set TTL for Key Verify that user can specify TTL for Key: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: TimeoutError: Waiting for element to be located By(xpath, .//div[starts-with(@data-testid, 'database-')][.//*[text()='test_standalone-v7-C(^*9xaf0X']]/../..//button[@data-testid = 'refresh-keys-refresh-btn'])
Set TTL for Key ► Verify that user can set ttl for Hash fields ► Set TTL for Key Verify that user can set ttl for Hash fields: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: TimeoutError: Waiting for element to be located By(xpath, //div[@data-testid="hash-ttl_content-value-Field1WithTtl"])
Tree view verifications for big database ► Verify that user can see the total number of keys, the number of keys scanned, the “Scan more” control displayed at the top of Tree view ► Tree view verifications for big database Verify that user can see the ...: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: AssertionError: incorrect count is displayed: expected false to deeply equal true
Release stage tests / e2e-linux-test / E2E tests (2)
Process completed with exit code 1.
Add database ► Verify that user can add SSH tunnel with Password for Standalone database ► Add database Verify that user can add SSH tunnel with Password for Standalone database: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: ElementClickInterceptedError: element click intercepted: Element <iframe name="51d8efd8-5178-40f7-8007-885e4b02f3e4" class="webview ready" sandbox="allow-scripts allow-same-origin allow-forms allow-pointer-lock allow-downloads" allow="cross-origin-isolated; autoplay; clipboard-read; clipboard-write" src="vscode-webview://1b2f8dk2jiq4apu32rkj1kecf4heq2a26f98upgift25riapo6v9/index.html?id=51d8efd8-5178-40f7-8007-885e4b02f3e4&amp;origin=f4f8f9ff-38ed-4c8e-9298-7ccec116d6cb&amp;swVersion=4&amp;extensionId=Redis.redis-for-vscode&amp;platform=electron&amp;vscode-resource-base-authority=vscode-resource.vscode-cdn.net&amp;parentOrigin=vscode-file%3A%2F%2Fvscode-app" style="border: none; width: 100%; height: 100%; pointer-events: auto;" cd_frame_id_="fb9dc9ce163a7eee5e4c55130367b978"></iframe> is not clickable at point (900, 702). Other element would receive the click: <div class="notification-list-item-message" custom-hover="true">...</div>
Filtering per key name ► Verify that user can filter keys per data type ► Filtering per key name Verify that user can filter keys per data type: tests/e2e/mochawesome-report/junit-report.xml#L0
Failed test found in: tests/e2e/mochawesome-report/junit-report.xml Error: AssertionError: The creation of new list key request failed: expected 400 to deeply equal 201
Release stage tests / e2e-linux-test / E2E tests (3)
Process completed with exit code 1.
Release stage tests / Approve E2E tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Release stage tests / build-linux / Build linux
This extension consists of 1269 files, out of which 571 are JavaScript files. For performance reasons, you should bundle your extension: https://aka.ms/vscode-bundle-extension. You should also exclude unnecessary files by adding them to your .vscodeignore: https://aka.ms/vscode-vscodeignore.
Release stage tests / frontend-tests / Frontend tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Release stage tests / e2e-linux-test / E2E tests (1)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Release stage tests / e2e-linux-test / E2E tests (0)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Release stage tests / e2e-linux-test / E2E tests (2)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Release stage tests / e2e-linux-test / E2E tests (3)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Artifacts

Produced during runtime
Name Size
linux-build Expired
10.3 MB
mocha-report-linux-node-0 Expired
376 KB
mocha-report-linux-node-1 Expired
384 KB
mocha-report-linux-node-2 Expired
384 KB
mocha-report-linux-node-3 Expired
385 KB