Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update TestNG to 6.14.2 version to fix false positive test result #1398

Merged
merged 1 commit into from
Mar 16, 2018

Conversation

terryzuoty
Copy link
Contributor

@terryzuoty terryzuoty commented Mar 8, 2018

  • TestNG before 6.14 treats configuration failure as pass
  • this has been fixed since TestNG 6.14
  • update TestNG version to 6.14.2 to fix this bug in product build
  • separate JLM test targets to avoid OOM failure
  • re-enable tests which are fixed and passing
  • update exlucde file which failed on TestNG 6.14.2
  • exclude reattachAfterExit from win since it is not supported on win

fixed:#1367
fixed:#1112
Issue:#1454

Signed-off-by: Tianyu Zuo tianyu@ca.ibm.com

@llxia
Copy link
Contributor

llxia commented Mar 9, 2018

Please also update TestNG jar version in readme. Thanks.
Please skip ci in your next commit msg, as this change cannot be verified by SDK compilation.

@terryzuoty terryzuoty force-pushed the cbuild branch 6 times, most recently from 0efec8a to 793e706 Compare March 12, 2018 18:30
@terryzuoty terryzuoty changed the title WIP: update TestNG to 6.14.2 version to fix false positive test result update TestNG to 6.14.2 version to fix false positive test result Mar 13, 2018
@terryzuoty terryzuoty force-pushed the cbuild branch 2 times, most recently from 04f4e5a to 37702d2 Compare March 13, 2018 18:11
@terryzuoty
Copy link
Contributor Author

Hi @llxia @smlambert , this PR is ready for review

@llxia
Copy link
Contributor

llxia commented Mar 13, 2018

Could we add description for why we have to separate JLM_Tests_interface, remove gpu exclude, and exclude on win? Thanks.

@terryzuoty
Copy link
Contributor Author

they were in the commit message, updated the description of this PR.

@terryzuoty terryzuoty force-pushed the cbuild branch 3 times, most recently from 54f4d0d to 27206e3 Compare March 13, 2018 18:55
@terryzuoty terryzuoty force-pushed the cbuild branch 5 times, most recently from 37b9b7b to 64f8842 Compare March 15, 2018 19:33
* TestNG before 6.14 treats configuration failure as pass,
  this has been fixed since TestNG 6.14, update TestNG
  version to 6.14.2 to fix this bug in product build
* separate JLM test targets to avoid OOM failure
* re-enable tests which are fixed and passing
* update exclude file which failed on TestNG 6.14.2
* exclude reattachAfterExit from win since it is not supported on win
* disable testSoftMxRemote tests since it failed at setup stage

[ci skip]

fixed:eclipse-openj9#1367
fixed:eclipse-openj9#1112
Issue:eclipse-openj9#1454

Signed-off-by: Tianyu Zuo <tianyu@ca.ibm.com>
@smlambert
Copy link
Contributor

Jenkins test sanity all

@llxia
Copy link
Contributor

llxia commented Mar 16, 2018

This PR changed sha1 to match new testng jar in getDependencies.pl. PR builds failed because they are using staged old testng.jar from Jenkins https://ci.eclipse.org/openj9/job/test.getDependency/

https://ci.eclipse.org/openj9/job/test.getDependency/ should be rerun after the change is delivered to make sure future PR builds is using up-to-date jar.

@smlambert
Copy link
Contributor

smlambert commented Mar 16, 2018

Thanks @llxia - I forgot that this is how the getDependency currently is called at OpenJ9 (could likely rethink this approach, and consider same approach as for freemarker.jar - try to fetch it, and only if fails, fall back to pre-fetched version).

Will merge this change (which has been verified in internal personal builds) and launch a getdependency job.

@smlambert smlambert merged commit 8499c69 into eclipse-openj9:master Mar 16, 2018
@terryzuoty
Copy link
Contributor Author

Thanks for launching the getdependency job Shelley

@smlambert
Copy link
Contributor

This was a big PR to pull together (given all the internal dependencies also), thanks for sticking with it @TianyuZuo !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade TestNG to latest release (v6.14) Test failure not reported
3 participants