Arquillian and Open Liberty

Build and Fat Problems.

The build farm that IBM uses uses a lot of virtual machines and, with a large team, we occassionally hammer it to the extent that some of the default Arquillian controlled FAT tests can, rarely, timeout.

This is particularly the case with tests that test various Deployment Exceptions by waiting for the default timeout and then scanning the messages.log.

The URL: https://github.com/OpenLiberty/open-liberty/labels/arquillian

holds the current set of Arquillian related issues and the board: https://github.com/OpenLiberty/open-liberty/issues#boards?labels=team%3Amicroprofileuk&repos=103694377

holds the current activity and priority order of what is being worked. Each issue is discussed in the individual issue.

Removal of the internal IBM version i.e. #1462 delivery/effectiveness/use is currently blocked by 1463, 2506 and providing an external solution to #2485 and #2456. All 5 of these need to be fixed for us to be able to remove the use of the internal IBM Arquillian.

• 1462 - Wrapped exceptions upstream - PR done but not merged by commiter
• 1463 - Latest version of Arquillian Core Does not pass all FT/Config TCK
• 2506 - Upsteam Arquillian Container 'Hangs' - Andrew has fix (change is in Simplicity MvnUtils)
• 2485 - I left this in review for a while after having increased the undeploy timeout to 5 and have seen no new problems since. Two ations are required to make the external Arquillian as robust: 1 - Each IBM arquillian.xml needs to set the undeploy timeout and not rely on the default. 2 - IN https://github.ibm.com/gordon-hutchison/arquillian-container-was/pull/6/files I made the undeploy more robust - this work needs to be fed in upstream. I raised 2717 and 2718 to cover these respectively.
• 2456 - If deploy of TCK test with @ShouldThrow( DefinitionException ) takes > 20 seconds - test will fail