Disable and remove projects in downstream

[meteorcloudy]

Those projects are broken due to incompatible changes in Bazel and
didn't get fixed for a long time.

• Android Testing: Android testing is broken with Bazel 4.2.1 android/testing-samples#417
• Tulsi: Bazel CI: Tulsi failing with both Bazel 4.2 and Bazel@HEAD tulsi#286
• rules_dotnet: Bazel CI: rules_dotnet failing in downstream pipeline with Bazel@HEAD bazel-contrib/rules_dotnet#268
• rules_haskell: Bazel CI: rules_haskell failing with Bazel 4.2 tweag/rules_haskell#1650
• rules_k8s: rules_k8s broken with Bazel@HEAD CI rules_k8s#668
• rules_d: removed because the project isn't maintained.

[aherrmann]

Those projects are broken due to incompatible changes in Bazel and
didn't get fixed for a long time.

rules_haskell was only informed about this failure yesterday: tweag/rules_haskell#1650
That's a very short deadline to get a fix in place.
Is there some way to set up automatic notification for when this pipeline fails?

[meteorcloudy]

Our CI sheriff is responsible for filing issues against downstream projects, automatic notification can be very noise, because sometimes it's a Bazel bug or infra issue.

For rules_haskell, indeed I probably should give it more time, got confused with the other long standing failing projects. Sorry about that. But you can still check Bazel@HEAD + rules_haskell result at https://buildkite.com/bazel/bazel-at-head-plus-disabled/builds/1133, we can re-enable it in the actual downstream pipeline once it's green. ;)

[meteorcloudy]

@aherrmann
Wait a minute, rules_haskell isn't only failing in downstream pipeline, it's already failing with Bazel 4.2.1 since https://buildkite.com/bazel/rules-haskell-haskell/builds?branch=master&page=7.

Maybe you should put a build status badge in the README file? Something like

here you go: tweag/rules_haskell#1652

[aherrmann]

Wait a minute, rules_haskell isn't only failing in downstream pipeline, it's already failing with Bazel 4.2.1 since https://buildkite.com/bazel/rules-haskell-haskell/builds?branch=master&page=7.

Oh, I missed that. Looks like perhaps something changed about the image.

    libgmp.so: cannot open shared object file: No such file or directory

Maybe you should put a build status badge in the README file? Something like

here you go: tweag/rules_haskell#1652

Thanks, it's better than nothing. I'd still prefer actual notifications, though. 🙂 Just makes a timely response more likely.

[philwo]

@aherrmann I sent you a PR here that hopefully fixes the issue: tweag/rules_haskell#1655