Today the medium-lsm-multi Jenkins job failed twice. The failure was during connection close. Unfortunately there was a bug in wtperf.c and I don't know the return code. It does not fail most of the time. The time I saw a failure, it was on the 4th iteration of the script. After fixing the bug, it didn't fail (5 iterations). The only change shown in the changelog when this started are the make clean changes, which should not matter here.
This is not a crash or seg fault, but close returning an error value. For now, I'll keep rerunning that job.
- related to
-
WT-1 placeholder WT-1
- Closed
-
WT-2 What does metadata look like?
- Closed
-
WT-3 What file formats are required?
- Closed
-
WT-4 Flexible cursor traversals
- Closed
-
WT-5 How does pget work: is it necessary?
- Closed
-
WT-6 Complex schema example
- Closed
-
WT-7 Do we need the handle->err/errx methods?
- Closed
-
WT-8 Do we need table load, bulk-load and/or dump methods?
- Closed
-
WT-9 Does adding schema need to be transactional?
- Closed
-
WT-10 Basic "getting started" tutorial
- Closed
-
WT-11 placeholder #11
- Closed
-
WT-12 Write more examples
- Closed
-
WT-13 Define supported platforms
- Closed
-
WT-14 Windows build
- Closed
-
WT-15 Automated build/test infrastructure
- Closed
-
WT-16 Test suite
- Closed
-
WT-17 Multithreaded tests
- Closed
-
WT-18 Coverage tests
- Closed
-
WT-19 Memory access / leak tests
- Closed
-
WT-1225 LSM compact hanging
- Closed
-
WT-1227 Close debug
- Closed
-
WT-1230 LSM queue growing too large
- Closed