[
https://issues.apache.org/jira/browse/TRAFODION-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847593#comment-15847593
]
ASF GitHub Bot commented on TRAFODION-2457:
-------------------------------------------
Github user DaveBirdsall commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/940#discussion_r98781522
--- Diff: core/sql/regress/compGeneral/TEST042 ---
@@ -229,6 +229,10 @@ values (600,52,43,4.12345678,6.0932);
--
insert into p9tab (c5) values (0E0);
+-- caching behavior changes with or without authorization initialized,
+-- make sure authorization is initialized when we run this test
+initialize authorization;
--- End diff --
So, do we get an error if authorization is already initialized? Is the
error filtered out of the diffs?
> regress/compGeneral/TEST042 shows non-deterministic results
> -----------------------------------------------------------
>
> Key: TRAFODION-2457
> URL: https://issues.apache.org/jira/browse/TRAFODION-2457
> Project: Apache Trafodion
> Issue Type: Bug
> Reporter: Anoop Sharma
> Assignee: Hans Zeller
>
> compGeneral/TEST042 runs tests for query caching feature and
> validates it by looking at the number of cache hits and other parameters.
> These values change based on where this test is being run,
> what the environment is and other changes.
> It fails off and on and folks have been updating expected files
> or known diff files to handle it.
> Because of the non-deterministic behavior, the test as it is currently
> written is unreliable and developers/jenkins failures are ignored.
> The test suite need to be modified and written so it doesn't make
> the cache hit/miss values as part of expected output. Or some other
> way to tolerate a range or the difference in output.
> For this checkin, this test has been disabled. A proper way to write
> this test will be discussed and once that is done, it will be reenabled.
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
