-
```
go test -tags invariants --exec 'stress -p 4' -timeout 0 -v ./wal -run TestConcurrentWritersWithManyRecords
=== RUN TestConcurrentWritersWithManyRecords
failover_writer_test.go:602: s…
-
Test replication/box_set_replication_stress.test.lua is flaky:
OS: always macOS
arch: always x86_64
Tarantool version:
Tarantool 2.6.0-36-g29ec62891
Target: Darwin-x86_64-RelWithDebInfo
…
-
It is time for a redesign of the stress testing framework. Specifically,
1. **Restrict input range**. Using Cauchy for random coordinates is excessive, as it can easily result in values outside 100…
tpapp updated
11 months ago
-
**Description:**
Currently, the production backend runs in 512MB. There is some uncertainty that this might be insufficient for 100+ concurrent users submitting large files.
**Acceptance Criter…
-
## RFC: Implement Resilient Error Handling for API Overload Conditions
### Background
Currently, the sampling loop is vulnerable to API overload conditions (error 529), which can result in frequent f…
-
I decided to stress-test Vello by modifying the with_winit example. Instead of just one tiger, I changed it to draw hundreds of animated tigers.
My branch with the modified test can be found here: …
-
Right now, the randomized tests only run automatically a few times on every pebble CI run. We should add a new nightly build which stresses each of the pebble randomized tests. We can probably stress …
-
I have issue understanding the output of stress testing. I believe my sublime text stress tester is misbehaving.
`stress.cpp`
![image](https://user-images.githubusercontent.com/92126782/167201745-…
-
The upcoming `Gc` test in #469 has surfaced a macOS segfault while running `STM Gc stress test parallel`.
This first happened on 5.3.0+trunk:
https://github.com/ocaml-multicore/multicoretests/acti…
-
If I stress test my application it crashes and the application restarts. In JavaFX it runs just fine.
Allowing more memory does not make any difference. A tail -f on nohup.out shows the logging be…