Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Oct 14, 2016

What is this PR for?

While running jUnit tests in zeppelin-server & zeppelin-zengine projects, several note are created during the process and those notes are never purged after the execution of the tests.

What type of PR is it?

Bug Fix

Todos

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-1542

How should this be tested?

Prerequisites:

  1. Get the list of note that already exist in server.

Now build zeppelin project by running maven commands(mvn clean package)(mvn clean package -pl 'zeppelin-interpreter,zeppelin-zengine,zeppelin-server').

  1. Now no extra note should get created after running the maven command

Screenshots (if appropriate)

Questions:

  • Does the licenses files need update? No
  • Is there breaking changes for older versions? No
  • Does this needs documentation? No

@ghost ghost closed this Oct 17, 2016
@ghost
Copy link
Author

ghost commented Oct 17, 2016

Reopening the PR to trigger CI build

@ghost ghost reopened this Oct 17, 2016
@jongyoul
Copy link
Member

Looks interesting!

@Leemoonsoo
Copy link
Member

LGTM!

@khalidhuseynov
Copy link
Member

doesn't tearDown() remove whole directory?

@jongyoul
Copy link
Member

@khalidhuseynov If we already have own our notes, removing whole directory also removes our own. :-)

@khalidhuseynov
Copy link
Member

Yeah make sense, LGTM!

@kavinkumarks
Copy link
Contributor

LGTM 👍

Thanks,
Kavin
MailTo: [email protected]

@Leemoonsoo
Copy link
Member

Merge to master if there're no more discussions.

@asfgit asfgit closed this in 1214463 Oct 19, 2016
darionyaphet pushed a commit to darionyaphet/zeppelin that referenced this pull request Oct 27, 2016
…-server, zeppelin-zengine

### What is this PR for?
While running jUnit tests in zeppelin-server & zeppelin-zengine projects, several note are created during the process and those notes are never purged after the execution of the tests.

### What type of PR is it?
Bug Fix

### Todos

### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1542

### How should this be tested?
Prerequisites:
1. Get the list of note that already exist in server.

Now build zeppelin project by running maven commands(mvn clean package)(mvn clean package -pl 'zeppelin-interpreter,zeppelin-zengine,zeppelin-server').
1. Now no extra note should get created after running the maven command

### Screenshots (if appropriate)

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No

Author: rajarajan-g <[email protected]>

Closes apache#1524 from rajarajan-g/ZEPPELIN-1542 and squashes the following commits:

d97cb4a [rajarajan-g] code changes for ZEPPELIN-1542
pedrozatta pushed a commit to pedrozatta/zeppelin that referenced this pull request Oct 27, 2016
…-server, zeppelin-zengine

### What is this PR for?
While running jUnit tests in zeppelin-server & zeppelin-zengine projects, several note are created during the process and those notes are never purged after the execution of the tests.

### What type of PR is it?
Bug Fix

### Todos

### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1542

### How should this be tested?
Prerequisites:
1. Get the list of note that already exist in server.

Now build zeppelin project by running maven commands(mvn clean package)(mvn clean package -pl 'zeppelin-interpreter,zeppelin-zengine,zeppelin-server').
1. Now no extra note should get created after running the maven command

### Screenshots (if appropriate)

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No

Author: rajarajan-g <[email protected]>

Closes apache#1524 from rajarajan-g/ZEPPELIN-1542 and squashes the following commits:

d97cb4a [rajarajan-g] code changes for ZEPPELIN-1542
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants