feb41819ec
It appears that the double write caused by using to() inside a separate execution environment (experimental.chain) causes flux e2e tests to behave unpredictably, when coupled with the 1.x storage engine. Removing the second write by using two passes, one to write to the db, then another to run the test, eliminates the flakiness. Verified by running e2e tests in parallel times 8 for 12 hours without any flakiness observed. Before the fix, the flakiness would take approx 30 minutes on avgerage to exhibit. This commit also removes universe/to_time from the skipped tests because it was added when this flakiness was discovered. |
||
|---|---|---|
| .. | ||
| experimental | ||
| influxdata/influxdb | ||
| testing | ||
| packages.go | ||