Comments (4)
What tests will be a part of what levels?
from rev.
That's for the solver of this issue to decide
from rev.
from rev.
You can look at the time each test takes by running it today. From there, you can do a Huffman-like compression, by sorting the times, and taking all of the fastest tests which take 1/3 of the total time. That would be the "Low" category. Then among the remaining tests, take the fastest which add up to 1/3 of the total time. They and the Low tests would be in the Med category. Finally, the remaining tests and Med would be in the High category. That's one way to do it in thirds.
But another way would be to put all of the fastest tests in the Low category up to where there is a huge climb in the timing of the tests. Sort the tests by runtime, and plot the runtimes. At the first large jump, put everything below that jump in the Low category. Then do the same with the remaining tests, finding a large jump and putting all tests under that jump in the Med category. Put any remaining tests in the High category.
Numbers like 1, 2, 3 can be used instead of category names, so that in CMake you can add a tag like testlevel=1
to each test with a number on it, and then only run a test if its number is less than or equal to the testing level.
from rev.
Related Issues (20)
- simple constructor crash HOT 4
- Argument passing / atoi conversion sensitivity to compiler output HOT 9
- missing thread execution for RV32I HOT 1
- Make spikeCheck modular based on the startSymbol passed in the rev config
- Statistics not being correctly accumulated or reported HOT 2
- fcvt.w.s does not support rounding modes HOT 8
- [FEATURE REQUEST] ifence HOT 1
- [FEATURE REQUEST] Support cache flush instructions HOT 1
- A problem with FPU register dependency tracking HOT 12
- Out of Memory error when using rev_mmap (with the memH memory backend) HOT 2
- c.addi16sp instruction is incorrectly printed as c.lui by Rev Tracer HOT 1
- Tracer is printing compressed register move instructions as c.jr instructions HOT 3
- [FEATURE REQUEST] Documentation HOT 3
- rev_read operation slowdown after large number of lines read HOT 2
- Stack buffer initialization corrupts memory. HOT 22
- lwsp instruction execution generating bad address outside of stack HOT 3
- dump_stack() system call returning only zeros
- [FEATURE REQUEST] CSR Tracing
- [FEATURE REQUEST] Support signal and trap handling
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.
from rev.