Merge lp:~mir-team/mir/workaround-for-valgrind-opcode into lp:mir
Status: | Merged |
---|---|
Approved by: | Daniel van Vugt |
Approved revision: | no longer in the source branch. |
Merged at revision: | 2979 |
Proposed branch: | lp:~mir-team/mir/workaround-for-valgrind-opcode |
Merge into: | lp:mir |
Diff against target: |
12 lines (+1/-1) 1 file modified
tests/mir_test_framework/testing_server_options.cpp (+1/-1) |
To merge this branch: | bzr merge lp:~mir-team/mir/workaround-for-valgrind-opcode |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
PS Jenkins bot (community) | continuous-integration | Approve | |
Daniel van Vugt | Approve | ||
Chris Halse Rogers | Approve | ||
Alberto Aguirre (community) | Approve | ||
Review via email: mp+272997@code.launchpad.net |
Commit message
Explicitly use "/dev/urandom" vs the default __x86_rdrand() which seems to cause opcode issues.
This is a WORKAROUND until this is fixed:
https:/
Description of the change
This work around is for errors that only happen on amd64:
http://
Invalid op code from valgrinds latest release.
Error started happening here:
http://
Failed > Console Output #1225 Sep 30, 2015 3:21:48 PM
Success > Console Output #1224 Sep 30, 2015 2:07:47 PM
New valgrind release:
-- Matthias Klose <email address hidden> Wed, 30 Sep 2015
Still dont know what exactly is causing the issue with valgrind.
ci-testing passed:
http://
Sounds plausible...
valgrind may have updated it's cpuid info?