Yes I use two such tools like that, on A HO with Tyler yesterday we
concluded that all the external tools did pass the regex, but LAVA did not,
that is the case presented here.
In addition I think Tyler implied that such a regex tester is not the
complete LAVA story, and that other validation of the result could be
combined in a LAVA specific tool.
Mike
On 25 March 2014 06:00, Milosz Wasilewski <email address hidden>wrote:
> Mike,
> Did you try this tool: http://regexpal.com/
> It doesn't meet all your requirements, but should do the some of the job.
>
> --
> You received this bug notification because you are a member of Linaro
> Validation Team, which is subscribed to LAVA Project.
> https://bugs.launchpad.net/bugs/1296880
>
> Title:
> LAVA result regex can't be validated prior to a run
>
> Status in LAVA Project:
> New
>
> Bug description:
> When developing a test, python regex tools can provide some validation
> of the results string parsing outside of LAVA.
>
> However the results are not always the same or complete, and this is a
> problem with tests that take hours to run.
>
> A tool - ideally web based and thus always current, that could
> validate a results string pasted into a window similar to how JSON
> scripts can be run would be very valuable. It should return the same
> results that LAVA would be expecting such as test_case_id, results
> etc.
>
> e.g.
> If I were to paste in the regex
> ^(?P<test_case_id>[\s\S]+)\s+Result:(?P<result>(pass|fail))
> and
> a results string such as
> test atomic inc/dec of signed word_1_2 Result:pass
>
> I would expect to see
>
> LAVA results = OK
> test_case_id = "test atomic inc/dec of signed word_1_2"
> result = "pass"
>
> Or some helpful diagnosis if the result would not have produced any
> test result had this been a real run.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/lava-project/+bug/1296880/+subscriptions
>
Yes I use two such tools like that, on A HO with Tyler yesterday we
concluded that all the external tools did pass the regex, but LAVA did not,
that is the case presented here.
In addition I think Tyler implied that such a regex tester is not the
complete LAVA story, and that other validation of the result could be
combined in a LAVA specific tool.
Mike
On 25 March 2014 06:00, Milosz Wasilewski <email address hidden>wrote:
> Mike, regexpal. com/ /bugs.launchpad .net/bugs/ 1296880 case_id> [\s\S]+ )\s+Result: (?P<result> (pass|fail) ) /bugs.launchpad .net/lava- project/ +bug/1296880/ +subscriptions
> Did you try this tool: http://
> It doesn't meet all your requirements, but should do the some of the job.
>
> --
> You received this bug notification because you are a member of Linaro
> Validation Team, which is subscribed to LAVA Project.
> https:/
>
> Title:
> LAVA result regex can't be validated prior to a run
>
> Status in LAVA Project:
> New
>
> Bug description:
> When developing a test, python regex tools can provide some validation
> of the results string parsing outside of LAVA.
>
> However the results are not always the same or complete, and this is a
> problem with tests that take hours to run.
>
> A tool - ideally web based and thus always current, that could
> validate a results string pasted into a window similar to how JSON
> scripts can be run would be very valuable. It should return the same
> results that LAVA would be expecting such as test_case_id, results
> etc.
>
> e.g.
> If I were to paste in the regex
> ^(?P<test_
> and
> a results string such as
> test atomic inc/dec of signed word_1_2 Result:pass
>
> I would expect to see
>
> LAVA results = OK
> test_case_id = "test atomic inc/dec of signed word_1_2"
> result = "pass"
>
> Or some helpful diagnosis if the result would not have produced any
> test result had this been a real run.
>
> To manage notifications about this bug go to:
> https:/
>