Comments (3)
The resource waste of --repeat
without stopping would only be high if the flaky tests use significantly more resources than the passing ones (especially since the passing ones would always have to repeat N times). Hopefully this isn't the case for your test suite in general.
Would the semantics for --gtest_break_on_failure
be sufficient for your intended use case (stop running gtest-parallel
when any test fails)? I'm a bit hesitant to add flags that don't have a corresponding --gtest
ones. I can see --gtest_break_on_failure
being useful locally as you can start looking into the first detected failure without having to ctrl+c to abort execution.
from gtest-parallel.
Context: running a handful of tests a lot of time. If one of the test if flaky at 3%, first failure will appear on average at 33th try. With 1000 iterations, that's 967 more than needed!
--gtest_break_on_failure
is not an ideal fit, since we still want to detect all tests failing at least once.
I agree this is not specific to gtest-parallel. Opened google/googletest#2645
from gtest-parallel.
Thanks, do let me know what the outcome of that is as I'm more inclined to consider upstream flags. I was more thinking if you run 100 tests 100 times and only one of them is flaky, that 33th time only lowers the total number of iterations from 10000 to 9967, at which point the savings are less than 1%.
from gtest-parallel.
Related Issues (19)
- Add a mechanism for avoiding removing non-gtest-parallel data in output_dir HOT 2
- Add tests to make sure that tests run in proper order (failed or unseen tests first, longest running tests first) HOT 1
- Multiple parallel invocations of gtest-parallel can fail(!) HOT 3
- python gtest_parallel.py --help doesn't do anything HOT 1
- Log file names generated by gtest-parallel are too long HOT 8
- Feature request: batching of tests HOT 22
- Missing year and name of copyright owner in LICENSE file. HOT 4
- gtest
- Log files never created for long test names HOT 1
- It hangs on ubuntu HOT 2
- Debug mode much needed as a developer to debug HOT 2
- can i use it in my muti-threads test_cases? HOT 2
- Feature: Consider adding batching
- Running Gtest requires pressing a key to continue
- Add support for running tests in a pty HOT 1
- The reported test duration is wrong when timed out
- the running test cases are not actively killed
- Support per-test case timeout?
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 gtest-parallel.