On Wed, 20 Sep 2023 03:56:28 GMT, Leonid Mesnik wrote:
> Test start failing because of unexpected VM logging.
> The fix is to search expected string ignoring any unknown output from forked
> process.
> Tested with tier1 and by running test with various options used in CI.
Thumbs up. Please
On Wed, 20 Sep 2023 03:56:28 GMT, Leonid Mesnik wrote:
> Test start failing because of unexpected VM logging.
> The fix is to search expected string ignoring any unknown output from forked
> process.
> Tested with tier1 and by running test with various options used in CI.
Marked as reviewed by
On Wed, 20 Sep 2023 05:32:07 GMT, David Holmes wrote:
>> Test start failing because of unexpected VM logging.
>> The fix is to search expected string ignoring any unknown output from forked
>> process.
>> Tested with tier1 and by running test with various options used in CI.
>
>
On Wed, 20 Sep 2023 03:56:28 GMT, Leonid Mesnik wrote:
> Test start failing because of unexpected VM logging.
> The fix is to search expected string ignoring any unknown output from forked
> process.
> Tested with tier1 and by running test with various options used in CI.
Okay - seems
On Wed, 20 Sep 2023 05:23:12 GMT, Leonid Mesnik wrote:
> OutputAnalyzer 'firstmatch' method analyze result. It analyze string from
> 'String OutputBuffer getStdout()' and can't be used to communicate with
> process.
Ah I see.
> Something like this was my first fix. Use
On Wed, 20 Sep 2023 03:56:28 GMT, Leonid Mesnik wrote:
> Test start failing because of unexpected VM logging.
> The fix is to search expected string ignoring any unknown output from forked
> process.
> Tested with tier1 and by running test with various options used in CI.
OutputAnalyzer
On Wed, 20 Sep 2023 03:56:28 GMT, Leonid Mesnik wrote:
> Test start failing because of unexpected VM logging.
> The fix is to search expected string ignoring any unknown output from forked
> process.
> Tested with tier1 and by running test with various options used in CI.
Something like this
On Wed, 20 Sep 2023 03:56:28 GMT, Leonid Mesnik wrote:
> Test start failing because of unexpected VM logging.
> The fix is to search expected string ignoring any unknown output from forked
> process.
> Tested with tier1 and by running test with various options used in CI.
Or even use the
On Wed, 20 Sep 2023 03:56:28 GMT, Leonid Mesnik wrote:
> Test start failing because of unexpected VM logging.
> The fix is to search expected string ignoring any unknown output from forked
> process.
> Tested with tier1 and by running test with various options used in CI.
Can't you just change
Test start failing because of unexpected VM logging.
The fix is to search expected string ignoring any unknown output from forked
process.
Tested with tier1 and by running test with various options used in CI.
-
Commit messages:
- 8316562:
10 matches
Mail list logo
