det-stresstests's People
det-stresstests's Issues
O_TMPFILE does not work under Docker container.
Currently the sample program open_tmpfile.c does not work inside a Docker container. Just running ./open_tmpfile.c
fails with Operation Not Supported. Everything works fine outside the container, with/without dettrace.
Adding new tests that will fail on dettrace or systrace
One example is the latest commit a6b29ab I commented out the mq test says it fails on DeTtrace.
On one hand, it's great adding new tests like mq
since we keep a "log" of tests which we don't pass yet. On the other hand, since DetTrace relies on this repo, it makes DetTrace development harder, since we see a failure when testing our latest changes in DetTrace. How should we go about solving this?
Ideas:
- Have DetTrace/systrace target a specific commit on det-stresstest. This way, even new tests will now break the existing testing functionality. Git submodules do this by default, so it's a natural workflow. The problem is what happens like now, when Kelly wants to add more thread tests, if Baojun has added new tests and the repository points several commits ahead, Kelly cannot easily add her tests, and we're back to the original problem.
- Have
master
contain only tests that are supported by dettrace/systrace, new tests likemq
are each on their own branch, which will be merged once dettrace/systrace support that test. This is awkward since dettrace and systrace are artificially gating each others tests though... - Learning from "(2", instead we have master which contains all the tests, DeTtrace and systrace both have a separate branch in this repo, branch
dettrace
andsystrace
, The test submodule in the DetTrace repo points to the det-stresstest branchdettrace
. This way, we can add all tests to master, and simply merge the passing ones over to our branch.
rdrand: Silent failure of illegal instruction (squashed exception)
On older machines this just tries to execute the rdrand, disregarding cpuid:
$ ./rdrand.bin
Illegal instruction (core dumped)
So how could this test work for us, since we depend on cpuid interception? (Furthermore, how could rr handle this as written? I doesn't seem to on the machines I've tried.)
Shouldn't this test be changed to check cpuid and print a different message if it reports absence of HW randomness?
Change tests away comparison based.
Currently, we compared every test against the previous saved "expected output". This means, if our implementation changes, we end up with false positives and have to go back and manually edit or regenerate the created output files. Instead, a better scheme would involve running the test twice (or even N times) and verifying the results always match the previous outputs.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.