-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DTS E2E tests fail on choosing firmware version #629
Comments
@PLangowski You should add more information to your issues like on what branch/commit it happened. And if there was anything special that might've resulted in those tests failing you should mention it too. It would help with reproducing this error. For example this test failed in
And from what I can see there were no changes to workflow or tests. So failure might've happened due to timing issue (e.g. waiting some arbitrary amount of time instead of waiting for expected output).
|
@PLangowski I try to but I cannot reproduce this issue on: dts 2.1.2 (commit 86fd10102a3b0c0c9adb652dbbd67efbf7ddc5c0) + patch:
|
@EduKav1813, any results from tests you are basing your answer on here? Check out how Michał presented his results. |
@EduKav1813 Let's wait for test results of |
@EduKav1813 https://github.com/Dasharo/meta-dts/actions/runs/12580633445 every test succeeded |
Device
QEMU
RTE version
N/A
OSFV version
develop
Affected component(s) or functionality
No response
Brief summary
The DTS E2E tests fail to choose the firmware version when deploying Dasharo.
How reproducible
No response
How to reproduce
Run any test from the E2E suite that deploys Dasharo.
Expected behavior
PASS
Actual behavior
E2E003.005 MSI PRO Z690-A DDR-4 initial deployment (legacy -> Core... | FAIL |
No match found for 'Does it match your actual specification? (Y|n)' in 30 seconds. Output:
Please, select Dasharo firmware version to install:
c) Community version
d
d) DPP version (coreboot + UEFI)
b) Back to main menu
Enter an option:
Subscription version (cooreboot + EDK2) selected
Link to screenshots or logs
The logs only are available internally, as they contain DPP secrets.
Additional context
No response
Solutions you've tried
No response
The text was updated successfully, but these errors were encountered: