On 19/12/2023 00:55, John Hubbard wrote:
> On 12/18/23 16:51, John Hubbard wrote:
>> On 12/18/23 03:32, Ryan Roberts wrote:
>> ...
I should also point out that some of the subtests already attempt a TAP
output. So now we end up with TAP-within-TAP output for those programs.
>>>
>>> It's a
On 12/18/23 16:51, John Hubbard wrote:
On 12/18/23 03:32, Ryan Roberts wrote:
...
I should also point out that some of the subtests already attempt a TAP
output. So now we end up with TAP-within-TAP output for those programs.
It's actually TAP-in-TAP-in-TAP if you're running from run_kselftest
On 12/18/23 03:32, Ryan Roberts wrote:
...
I should also point out that some of the subtests already attempt a TAP
output. So now we end up with TAP-within-TAP output for those programs.
It's actually TAP-in-TAP-in-TAP if you're running from run_kselftest.sh :)
For example:
# --
On 16/12/2023 02:40, John Hubbard wrote:
> On 12/15/23 18:25, John Hubbard wrote:
>> On 12/15/23 06:28, Ryan Roberts wrote:
>> ...
>>> I've kept all the existing "pretty" output and results summary as is, it
>>> just
>>> gets a hash in front of it when TAP is enabled.
>>>
>>> so this:
>>>
>>>
On 12/15/23 18:25, John Hubbard wrote:
On 12/15/23 06:28, Ryan Roberts wrote:
...
I've kept all the existing "pretty" output and results summary as is, it just
gets a hash in front of it when TAP is enabled.
so this:
---
running ./hugepage-mmap
---
Retur
On 12/15/23 06:28, Ryan Roberts wrote:
...
I've kept all the existing "pretty" output and results summary as is, it just
gets a hash in front of it when TAP is enabled.
so this:
---
running ./hugepage-mmap
---
Returned address is 0x89e0
First hex
On Fri, Dec 15, 2023 at 02:28:32PM +, Ryan Roberts wrote:
> On 15/12/2023 14:08, Mark Brown wrote:
> # ---
> # running ./hugepage-mmap
> # ---
> # Returned address is 0x89e0
> # First hex is 0
> # First hex is 3020100
> # [PASS]
> ok 1 hugepage-m
On 15/12/2023 14:08, Mark Brown wrote:
> On Fri, Dec 15, 2023 at 01:58:45PM +, Ryan Roberts wrote:
>> On 15/12/2023 13:54, Mark Brown wrote:
>
>>> What I did for ftrace which had a similar situation was make a wrapper
>>> script which invokes the test runner, make the test runner a
>>> TEST_PR
On Fri, Dec 15, 2023 at 01:58:45PM +, Ryan Roberts wrote:
> On 15/12/2023 13:54, Mark Brown wrote:
> > What I did for ftrace which had a similar situation was make a wrapper
> > script which invokes the test runner, make the test runner a
> > TEST_PROGS_EXTENDED so it's not run by the kselftes
On 15/12/2023 13:54, Mark Brown wrote:
> On Thu, Dec 14, 2023 at 04:24:34PM +, Ryan Roberts wrote:
>> When running tests on a CI system (e.g. LAVA) it is useful to output
>> test results in TAP format so that the CI can parse the fine-grained
>> results to show regressions. Many of the mm selft
On Thu, Dec 14, 2023 at 04:24:34PM +, Ryan Roberts wrote:
> When running tests on a CI system (e.g. LAVA) it is useful to output
> test results in TAP format so that the CI can parse the fine-grained
> results to show regressions. Many of the mm selftest binaries already
> output using the TAP
When running tests on a CI system (e.g. LAVA) it is useful to output
test results in TAP format so that the CI can parse the fine-grained
results to show regressions. Many of the mm selftest binaries already
output using the TAP format. And the kselftests runner
(run_kselftest.sh) also uses the for
12 matches
Mail list logo
