-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Make CI known flakes and errors #12413
Labels
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
And
And other test cases in that same suite. |
|
|
|
|
And
|
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This ticket is meant to track down flakes and errors that happen in Make CI (currently enabled in
main
and pull requests.OTP-27 bugs
inetrc
Kernel parameter doesn't accept atoms anymore on 27 (resolution ongoing in OTP-27 inetrc behavior change leads to obscure crashes erlang/otp#8899)java_SUITE
ofrabbitmq_mqtt
, and Erlang/OTP 27.1.1 (specifically) - (resolution in SSL version matching OTP 27.1.1 erlang/otp#8908 fixed in 27.1.2)Flakes
Failed to create SSL certificates
- multiple test suites, one example in commentrabbit > amqp_system > access_failure
- details in commentrabbit > metrics_SUITE > connection_metric_count_test
- details in commentrabbit > per_node_limit_SUITE > channel_consumers_limit
- details in commentrabbitmq_amqp_client > management_SUITE > cluster_size_3 > queue_topology
- details in commentrabbitmq_amqp_client > management_SUITE > cluster_size_3 > classic_queue_stopped
- details in commentrabbitmq_cli
sometimes fails with1383 tests, 5 failures
- the failures are all tests that set the disk free limit. It is not yet known whether they are proper errors, normal flakes or caused by differences in GH runnersrabbitmq_federation > exchange_SUITE > rolling_upgrade > child_id_format
- timetrap timeoutrabbitmq_federation > queue_SUITE > classic_queue > without_disambiguate > cluster_size_1 > dynamic_plugin_stop_start
- details in commentrabbitmq_management > clustering_SUITE > non_parallel_tests > queue_on_other_node
- details in commentrabbitmq_management > clustering_prop_SUITE > non_parallel_tests > prop_connection_channel_counts_test
- details in commentrabbitmq_mqtt > parallel-ct-set-1 > mqtt_shared_SUITE > cluster_size_3 > v4 rabbit_mqtt_qos0_queue_kill_node
- test failure (details in comment) leads to subsequent tests being unable to continue and to the job timing out after 30 minutesThe text was updated successfully, but these errors were encountered: