You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #5318 , we introduced the ability to run testinfra over tor on production-like setups. During release testing on hardware, we manually run the spectre/meltdown tests (https://github.com/speed47/spectre-meltdown-checker/) to ensure the running kernel contains mitigations against these vulnerabilities.
In order to reduce QA burden, we should automatically run these tests as part of the testinfra suite. Furthermore, it will allow us to code around false positives due to grsecurity hardening described in #5040 (comment) the
User Stories
As a QA / release engineer, I would like to minimize the time required to test, and automate as many testing steps as possible.
The text was updated successfully, but these errors were encountered:
Description
In #5318 , we introduced the ability to run testinfra over tor on production-like setups. During release testing on hardware, we manually run the spectre/meltdown tests (https://github.com/speed47/spectre-meltdown-checker/) to ensure the running kernel contains mitigations against these vulnerabilities.
In order to reduce QA burden, we should automatically run these tests as part of the testinfra suite. Furthermore, it will allow us to code around false positives due to grsecurity hardening described in #5040 (comment) the
User Stories
As a QA / release engineer, I would like to minimize the time required to test, and automate as many testing steps as possible.
The text was updated successfully, but these errors were encountered: