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
There are tests that exist for issues (bugs) that are known but for which there does not yet exist a solution (fix, mitigation, patch).
How do we accommodate those tests into the repo while allowing the testsuite to pass?
Potential solutions:
I originally wanted to have them in their intended target location ("tests") but simply omit the test name from "tests/Makefile" so it gets skipped over, a bit like we do for different vintages of kernels or distros.
Having them in a separate branch and merging them when a fix is upstream leaves them out of the way, but makes things inconvenient for developers switching back and forth and adding more branches than necessary, one per test.
They could go in a directory similar to "tests-manual" called "tests-pending" and when ready its sub-directory gets "git mv" into "tests" and update "tests/Makefile".
Don't merge the test at all until the fix is upstream.
I'd prefer the first, third, then second, fourth, in that order.
The text was updated successfully, but these errors were encountered:
pcmoore
changed the title
Accomodate tests for known issues for which fix does not yet exist
Q: accomodate tests for known issues for which fix does not yet exist
May 8, 2017
There are tests that exist for issues (bugs) that are known but for which there does not yet exist a solution (fix, mitigation, patch).
How do we accommodate those tests into the repo while allowing the testsuite to pass?
Potential solutions:
I originally wanted to have them in their intended target location ("tests") but simply omit the test name from "tests/Makefile" so it gets skipped over, a bit like we do for different vintages of kernels or distros.
Having them in a separate branch and merging them when a fix is upstream leaves them out of the way, but makes things inconvenient for developers switching back and forth and adding more branches than necessary, one per test.
They could go in a directory similar to "tests-manual" called "tests-pending" and when ready its sub-directory gets "git mv" into "tests" and update "tests/Makefile".
Don't merge the test at all until the fix is upstream.
I'd prefer the first, third, then second, fourth, in that order.
The text was updated successfully, but these errors were encountered: