Actually, this is an accidental pass, the reason is that the CONFIG_DEVMEM option did not come into being until the 3.19 kernel. I've adjusted the tests for that in https://git.launchpad.net/qa-regression- testing/commit/?id=f405927a76483d29f3a6bde092ebc29d7de6d945 .
Given that CONFIG_STRICT_DEVMEM is not set for arm64 on trusty, looking at the specific test exception, it was not accepting the correct failure value from the test (we run the test even when expecting failure, because we want to know if/when it gets fixed). I've added the correct failure value in the expected set of values for arm64 on trusty and older in https://git.launchpad.net/qa-regression- testing/commit/?id=ab5ba157aa0ba979e8e97612fe56678fbaabcdc5 . I'm closing this bug based on the above commits; please re-open if I made a thinko somewhere in my logic and the test is still failing. Thanks! ** Changed in: qa-regression-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747852 Title: test_072_strict_devmem in ubuntu_qrt_kernel_security should be skipped on Trusty ARM64 To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1747852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
