You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/07/15 15:31:00 UTC
[jira] [Work logged] (KNOX-2635) GatewayAppFuncTest is flaky
[ https://issues.apache.org/jira/browse/KNOX-2635?focusedWorklogId=623111&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-623111 ]
ASF GitHub Bot logged work on KNOX-2635:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Jul/21 15:30
Start Date: 15/Jul/21 15:30
Worklog Time Spent: 10m
Work Description: zeroflag opened a new pull request #470:
URL: https://github.com/apache/knox/pull/470
## What changes were proposed in this pull request?
Typical failure look like:
```
[ERROR] GatewayAppFuncTest.testMultiApps:338 1 expectation failed.
Expected status code <200> but was <404>.
```
It happens in test which are running right after testDeploymentCleanup or testDefaultTopology. These tests restart the gateway service during the test run.
The subsequent test overwrite the topology file which are used by all tests but file access date granularity is 1 second (msec part is always 000, this is likley FS specific) therefore the topology is never redeployed.
Adding clean up logic in between these restarts seem to solve the issue.
## How was this patch tested?
```bash
mvn test -Dtest=GatewayAppFuncTest
while [ $? -eq 0 ]; do
mvn test -Dtest=GatewayAppFuncTest
done
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@knox.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 623111)
Remaining Estimate: 0h
Time Spent: 10m
> GatewayAppFuncTest is flaky
> ---------------------------
>
> Key: KNOX-2635
> URL: https://issues.apache.org/jira/browse/KNOX-2635
> Project: Apache Knox
> Issue Type: Task
> Components: Tests
> Reporter: Attila Magyar
> Assignee: Attila Magyar
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Typical failure look like:
> {code:java}
> [ERROR] GatewayAppFuncTest.testMultiApps:338 1 expectation failed.
> Expected status code <200> but was <404>. {code}
> It happen in test which are running right after testDeploymentCleanup or
> testDefaultTopology. These tests restart the gateway service during the test run.
> The subsequent test overwrite the topology file which are used by all tests but file access date granularity is 1 second (msec part is always 000, this is likley FS specific) therefore the topology is never redeployed.
>
> Adding
> FileUtils.cleanDirectory(new File(config.getGatewayTopologyDir())); in between restarts seems to solve the issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)