You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When multiple inline_c tests in a rust file use the same names of environment variables, flakiness is observed during parallel execution of tests.
For example, if all tests in a rust file need an input directory and an output directory, and environment variables INLINE_C_RS_INPUT_PATH and INLINE_C_RS_OUTPUT_PATH are used to pass these values to assert_c macro, cases fail randomly upon running cargo test. To get around this, one needs to use unique environment variable names in each test.
This should be documented.
The text was updated successfully, but these errors were encountered:
Added documentation for the flakiness that may arise when multiple inline c tests use the same environment variables. Please refer issue issue [Hywan#22](Hywan#22) for more details.
When multiple inline_c tests in a rust file use the same names of environment variables, flakiness is observed during parallel execution of tests.
For example, if all tests in a rust file need an input directory and an output directory, and environment variables
INLINE_C_RS_INPUT_PATH
andINLINE_C_RS_OUTPUT_PATH
are used to pass these values toassert_c
macro, cases fail randomly upon runningcargo test
. To get around this, one needs to use unique environment variable names in each test.This should be documented.
The text was updated successfully, but these errors were encountered: