Skip to content

Conversation

@Mazo
Copy link
Contributor

@Mazo Mazo commented Feb 10, 2021

This should fix some of the flaky tests and speed up some of the water related ones.

There's still a failure with VehicleControlInteractWithWaterTest however, and I have no idea why. It runs perfectly fine when ran on it's own, but in a batch of all tests will fail even with greatly exaggerated timeouts for the expected message. Even running it in a smaller batch seems to work

@Fate-JH If you have any ideas on the above let me know.

class PlayerControlInteractWithWaterTest extends ActorTest {
val player1 =
Player(Avatar(0, "TestCharacter1", PlanetSideEmpire.TR, CharacterGender.Male, 0, CharacterVoice.Mute)) //guid=1
player1.Definition.UnderwaterLifespan(suffocation = 3000, recovery = 3000) // Override the default 60s down / 10s recovery so the tests don't take forever to run
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

player1.Definition.UnderwaterLifespan(...)
As with my far far ealiertests involving a singleton classes is evidenced, changing a single source class for one test changes it for every test. All tests involving a drowning player will endure this 3000ms / 3000ms time limit. Given the reliability of actor tests, depending on the order they are implemented, it's possible that a test whose constituent actors may receive less attention than hoped may be affected by these updates times. In other words, it'll drown faster too.
GlobalDefinitions can be like a singleton to all tests in that respect.

@NickPSF
Copy link
Contributor

NickPSF commented Apr 12, 2021

This one still in flux?

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.

3 participants