> test_expect_failure (as well as other helper functions in the test
> harness library, such as test_expect_success, test_must_fail,
> test_might_fail, etc.) are explained in t/README. By its definition,
> it technically satisfies "list of known issues" as you asked for.
> However, most softwar
Hi Mark,
On Thu, Jul 11, 2019 at 12:02 PM Mark T. Ortell
wrote:
>
> Elijah,
>
> Thanks for the response. I am not clear whether the test_expect_failure means
> that the test is trying to do something that should fail and so it is a valid
> test case or if it is a test case that is failing, but
t with criss
cross times on revisions' '
t/t9801-git-p4-branch.sh:test_expect_failure 'git p4 clone file subset branch' '
t/t9804-git-p4-label.sh:test_expect_failure 'two labels on the same changelist'
'
t/t9809-git-p4-client-view.sh:test_expect_failure '
On 2019-07-11 at 15:28:27, Mark T. Ortell wrote:
> Hello,
>
> I am doing a software tool assessment for functional safety and I am
> reviewing the use of Git as the SCM. One thing that I need to do is review
> the list of "known issues" with the Git release being used. I have gone
> through the
On Thu, Jul 11, 2019 at 8:50 AM Mark T. Ortell wrote:
>
> Hello,
>
> I am doing a software tool assessment for functional safety and I am
> reviewing the use of Git as the SCM. One thing that I need to do is review
> the list of "known issues" with the Git release being used. I have gone
> thro
Hello,
I am doing a software tool assessment for functional safety and I am reviewing
the use of Git as the SCM. One thing that I need to do is review the list of
"known issues" with the Git release being used. I have gone through the release
notes and found that it only contains the fixes and
6 matches
Mail list logo
