Merge lp:~mir-team/mir/workaround-for-valgrind-opcode into lp:mir
| Status: | Merged |
|---|---|
| Approved by: | Daniel van Vugt on 2015-10-01 |
| Approved revision: | 2979 |
| 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 | continuous-integration | Approve on 2015-10-01 | |
| Daniel van Vugt | Approve on 2015-10-01 | ||
| Chris Halse Rogers | Approve on 2015-10-01 | ||
| Alberto Aguirre | 2015-09-30 | Approve on 2015-09-30 | |
|
Review via email:
|
|||
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://
| Alberto Aguirre (albaguirre) wrote : | # |
FIY, the opcode is "rdrand %eax"
| Alberto Aguirre (albaguirre) wrote : | # |
s/FIY/FYI
| Brandon Schaefer (brandontschaefer) wrote : | # |
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2979
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
FAILURE: http://
SUCCESS: http://
deb: http://
FAILURE: http://
SUCCESS: http://
deb: http://
FAILURE: http://
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:2979
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| Daniel van Vugt (vanvugt) wrote : | # |
Another one. I guess we should be thankful these are rare. And normally it's just valgrind on armhf...
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:2979
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://

Sounds plausible...
valgrind may have updated it's cpuid info?