Skip to content
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

suspend/memory_after_suspend_auto fails with total amount of memory differing before/after the test #1703

Open
1 task done
pieqq opened this issue Jan 30, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@pieqq
Copy link
Collaborator

pieqq commented Jan 30, 2025

Bug Description

Recent run exhibiting this problem:

https://certification.canonical.com/hardware/201711-25989/submission/409962/

This device is an NVIDIA DGX-Station running 20.04,with 251 GB of RAM.

CPU: Intel(R) Xeon(R) CPU E5-2698 v4 @ 2.20GHz
GPUs: NVIDIA - 10de:1db2 (x4)

The test fails with the following output:

2c2
< total: 270165549056
---
> total: 270165532672

Meaning there is a difference of 16384 Kbytes between the two runs.

We had an internal discussion, and it looks like the issue is related to some graphics tests being executed before the two memory gathering info, resulting in some RAM being used or released for the GPUs.

Cert-blocker Test Case

  • cert-blocker

To Reproduce

Run the SRU test plan on that machine.

Expected Result

suspend/memory_after_suspend_auto job passes

Actual Result

suspend/memory_after_suspend_auto fails with output described above.

Environment

20.04, with the latest version of Checkbox (4.3.0dev44ubuntu20.04.1)

Relevant log output

Additional context

No response

@pieqq pieqq added the bug Something isn't working label Jan 30, 2025
Copy link

Thank you for reporting your feedback to us!

The internal ticket has been created: https://warthogs.atlassian.net/browse/CHECKBOX-1725.

This message was autogenerated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant