Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Ignore warnings from the engine/platform when running regression tests

Description

The output for a test with a warning message is:
<Warning><Code>5102</Code><Source>eclagent</Source><Message>SUCCESS clause failed (execution will continue): 5102: </Message></Warning>
<Dataset name='Result 1'>
 <Row><Result_1>6</Result_1></Row>
</Dataset>
 
Ideally, there should be an option in the regression tests to ignore warning messages such as these. The engine-specific "Source" tag means that a key file will not suit all engines.
 
A workaround would be to create a different key file for each engine, but this is not preferable.

Conclusion

None

Activity

Show:

Nathan Halliday July 13, 2020 at 3:03 PM

 I have spoken with and we have decided that this Jira is not needed. We will look at suppressing the warning by modifying the engine - to use onwarning.

 

Nathan Halliday July 13, 2020 at 2:10 PM

Thanks,

For my project, it is sufficient to use the second case - where each test that needs to ignore a warning has the tag specified. I think that the global case is not needed.

Therefore it should be a "test case related feature".

 

Attila Vamos July 13, 2020 at 1:53 PM

Do we need this as a global (for all executed test cases) or test case related feature?

In the first case it would be a new Regression Test Engine command line parameter like '–ignorePlatformWarning'. So, all warning line in the result of the test cases would be ignored (but some keyfile should be update).

In second case it would be a new tag like //ignoreEngineWarning into the ECL file and in this case the warning(s) would be ignored for that test only.

Or we need both.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Compatibility

Point

Fix versions

Pull Request URL

https://github.com/hpcc-systems/HPCC-Platform/pull/13968

Roadmap

Not applicable

Created July 13, 2020 at 1:23 PM
Updated July 16, 2020 at 10:56 AM
Resolved July 16, 2020 at 10:56 AM