[GitHub] flink pull request: [FLINK-3569] fix test cases that expect a diff...

[mxm]

Github user mxm commented on the pull request:

https://github.com/apache/flink/pull/1767#issuecomment-195282751
  
Sure. Thanks for merging!


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] flink pull request: [FLINK-3569] fix test cases that expect a diff...

[mxm]

Github user mxm closed the pull request at:

https://github.com/apache/flink/pull/1767


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] flink pull request: [FLINK-3569] fix test cases that expect a diff...

[StephanEwen]

Github user StephanEwen commented on the pull request:

https://github.com/apache/flink/pull/1767#issuecomment-195003857
  
This has been merged into master (1.1.x) and release-1.0 (1.0.x).

@mxm Can you close this? (was not autoclosed)


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] flink pull request: [FLINK-3569] fix test cases that expect a diff...

[StephanEwen]

Github user StephanEwen commented on the pull request:

https://github.com/apache/flink/pull/1767#issuecomment-192361294
  
Looks good, merging this...


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] flink pull request: [FLINK-3569] fix test cases that expect a diff...

[mxm]

Github user mxm commented on the pull request:

https://github.com/apache/flink/pull/1767#issuecomment-192338586
  
I think it is fixed now. The YARN test run in test scope and are not 
shaded...


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] flink pull request: [FLINK-3569] fix test cases that expect a diff...

[mxm]

GitHub user mxm opened a pull request:

https://github.com/apache/flink/pull/1767

[FLINK-3569] fix test cases that expect a different working directory

All the IT cases executed after shading now have the target directory as 
working directory.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mxm/flink FLINK-3569

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/flink/pull/1767.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 #1767


commit 7a229ab987b36cf341e0d78b6b92aab79a62ea8f
Author: Maximilian Michels 
Date:   2016-03-03T11:52:32Z

[maven] explicitly disable shading of flink-dist

- shading was previously disabled through setting the force-shading
  dependency to provided

commit 07ad4044ef1d746a4e8b54721436aedf894d42a3
Author: Maximilian Michels 
Date:   2016-03-03T15:31:49Z

[FLINK-3569] fix test cases that expect a different working directory

- all the it cases executed after shading now have the target directory
  as working directory




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---