You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@fjtirado I understand. The problem is they set the entire team that is working on the repository back. Especially now that this is under Apache and we are trying to build a bigger community. Failing builds mean a broken project and not getting changes in due to random issues pushes people away.
For this reason if the test is important, we need to find a way to do it better. I don't know if trying to find the solution as a team helps.
The reason for just commenting them out ( this test was just one of many ) is that without that, there is no interest in fixing them. Also each failure they cause, causes trouble for the project. Decreasing the bandwidth to run builds and increasing the healthiness of the project. If they need to be fixed, they can be fixed once the area they affect has changes done on them.
Description
This ticket will list flaky tests. The tests will be disabled or ignored from the build.
org.acme.travel.tests.multimessaging.springboot.MultiMessagingIT.testProcess
org.acme.travel.tests.messaging.springboot.MessagingIT.testProcess
Implementation ideas
To get a test
back it needs to be fixed. Removing a test is also an option.
The text was updated successfully, but these errors were encountered: