Comments (2)
Yes, making xfstests run it's tests on the CrashMonkey wrapper device is the proper approach. You will likely need to check how large a disk xfstests wants to use. CrashMonkey thus far has been using pure RAM disks, so the file system size has been limited by system memory size.
I believe "run in bkgd" refers to running CrashMonkey in the background and then starting an xfstest with the CrashMonkey device wrapper.
"Checking N crash states" should just require you to change the -s
parameter in CrashMonkey that denotes how many crash states to generate and test. You may also want to change the random seed in RandomPermuter.cpp
to something actually random. Right now it is set to a fixed value to help with reproducibility.
from crashmonkey.
Our understanding of the issue at hand is that you want to be able to log operations for tests run by xfstest through crashmonkey. We are thinking of doing this by setting the crashmonkey wrapper device (hwm) to be the device that xfstest runs tests on.
We would like to request several clarifications. Is the above interpretation correct? As for "run in bkgd," does this mean to run xfstests in the background?
Also, we are confused about the last task: "check N crash states." Does this mean crashing the tests run by xfstest, and letting crashmonkey validate the state of the device afterward? Should we adjust how xfstests runs the requested test?
from crashmonkey.
Related Issues (20)
- CrashMonkey test faililng due to assertion error in RandomPermuter HOT 1
- insmod ERROR: “disk_wrapper.ko: Cannot allocate memory” HOT 3
- Make multiple instances of CrashMonkey run in a single machine HOT 1
- Have CrashMonkey behave more like a fuzzer HOT 1
- Write an adaptor for Crashmonkey for dm-flakey HOT 2
- ACE fails on fsync HOT 3
- ACE fails on "nested" mode HOT 1
- report two Ace bugs HOT 15
- Build error happening HOT 2
- Failed test cases - "Unable to remove wrapper device" HOT 1
- Port CrashMonkey to Linux 5.6.6
- Update documentation and scripts to reflect changes in xfsMonkey.py for btrfs
- Build error "No such file or directory" on CentOS7 HOT 1
- xfstest adapter produces incorrect output files because of erroring commands
- Memory access violation HOT 1
- False positive tests
- The xfstest does not support _supported_os
- ZFS/OpenZFS support ?
- future bugs to investigate when CrashMonkey is more complete HOT 1
- Clean up logs
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 crashmonkey.