Add failing ORC thread-safety regressions and run all suites with nimble test
This commit is contained in:
1 parent
15af03e5c5
commit
c1c8a3c072
8 files changed
+342
-2
No files matched your search
@@ -459,6 +459,15 @@ As much as possible, avoid complex operations that might themselves fail.
|
||||
Don't do heavy operations like database writes, complex network operations, or
|
||||
file system operations that might fail and cause cascading errors.
|
||||
|
||||
## Testing
|
||||
|
||||
Run `nimble test` for all unit, regression, and ThreadSanitizer ownership tests.
|
||||
It runs every suite even when an earlier suite fails. For focused debugging,
|
||||
use `nimble testUnit`, `nimble testRegression`, or `nimble testThreadSafety`.
|
||||
The regression tests currently expose known defects and are expected to fail
|
||||
until those defects are fixed. See [tests/README.md](tests/README.md) for commands,
|
||||
requirements, and coverage limitations.
|
||||
|
||||
[log4j]: https://logging.apache.org/log4j/2.x/
|
||||
[logback]: https://logback.qos.ch/
|
||||
[effective logging level]: https://logback.qos.ch/manual/architecture.html#effectiveLevel
|
||||
|
||||
Reference in new issue
Block a user