GitHub user Leemoonsoo opened a pull request:
https://github.com/apache/zeppelin/pull/2081
[ZEPPELIN-2155] [HOTFIX] Flaky test: NotebookTest
### What is this PR for?
This PR fixes test failure described in ZEPPELIN-2155.
All the PR test fails with this problem at the moment.
Problem came from https://github.com/apache/zeppelin/pull/2049, which fixes
wrong authentication configuration for the test. And previously test were
written for wrong configuration.
This PR fixes wrong test and remove some assert statement that may occur
flaky test but don't really verify anything.
### What type of PR is it?
Hot Fix
### Todos
* [x] - fix problem
### What is the Jira issue?
### How should this be tested?
CI green
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Leemoonsoo/zeppelin ZEPPELIN-2155
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2081.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2081
----
commit 52266a28a2a6b1e8362f0ac24dcc6e8b2d8d7c92
Author: Lee moon soo <[email protected]>
Date: 2017-02-28T08:22:13Z
Remove unnecessary assert
commit 0ff3ff77d9b8bc8c2c10a26f937e460899e96e5a
Author: Lee moon soo <[email protected]>
Date: 2017-02-28T10:17:36Z
Turn off Authentication on DirAccessTest because it is not necessary
commit 21d91ef6bc582f13e205819be8c9cb735a86b8b4
Author: Lee moon soo <[email protected]>
Date: 2017-02-28T12:11:15Z
Handle multiple Set-Cookie headers
commit 0360108870b7e3e88429f4f6eab3829ccc23fa9b
Author: Lee moon soo <[email protected]>
Date: 2017-02-28T12:13:12Z
Correct test implementation with Authentication Enable
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
