Skip to content
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

Add cats-effect to the community build #9784

Merged
merged 1 commit into from
Sep 17, 2020
Merged

Add cats-effect to the community build #9784

merged 1 commit into from
Sep 17, 2020

Conversation

vasilmkd
Copy link
Contributor

Cats Effect 2 added under "cats-effect-2".
Cats Effect 3 added under "cats-effect-3".

cc @djspiewak

Copy link
Member

@dottybot dottybot left a comment

Choose a reason for hiding this comment

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

Hello, and thank you for opening this PR! 🎉

All contributors have signed the CLA, thank you! ❤️

Have an awesome day! ☀️

@vasilmkd
Copy link
Contributor Author

The cats effect build failed with the following exception:

sbt.librarymanagement.ResolveException: Error downloading ch.epfl.lamp:dotty-library_sjs1_0.28:0.28.0-bin-SNAPSHOT

@smarter
Copy link
Member

smarter commented Sep 13, 2020

I think (publishLocal in `dotty-library-bootstrappedJS`).value needs to be added to prepareCommunityBuild in Build.scala: https://github.com/lampepfl/dotty/blob/c104e9b1b7c028f114f8f3c0331198a9587391b5/project/Build.scala#L1253

@vasilmkd
Copy link
Contributor Author

That did the trick. Thank you @smarter.

@anatoliykmetyuk
Copy link
Contributor

Thanks for contributing this @vasilmkd! All of the Dotty community projects live in forks under dotty-staging organization – so that we have the capability to fix them fast if they break. I've created such a fork for cats-effects: https://github.com/dotty-staging/cats-effect – could you point the submodule to this fork instead?

@vasilmkd
Copy link
Contributor Author

@anatoliykmetyuk On it right now.

@anatoliykmetyuk anatoliykmetyuk merged commit 5435e68 into scala:master Sep 17, 2020
@vasilmkd vasilmkd deleted the cats-effect branch September 17, 2020 13:18
@anatoliykmetyuk
Copy link
Contributor

anatoliykmetyuk commented Sep 18, 2020

Looks like this project fails the CI once in a while:

https://github.com/lampepfl/dotty/runs/1131886366
https://github.com/lampepfl/dotty/runs/1128837504

@vasilmkd @djspiewak do you have an idea why this is happening?

@vasilmkd
Copy link
Contributor Author

vasilmkd commented Sep 18, 2020

The tests that fail are really hard to properly write and we know them to be slightly non-deterministic and therefore flaky. May I ask what environment these tests run in?

@anatoliykmetyuk
Copy link
Contributor

The CI definition of the community build step is here: https://github.com/lampepfl/dotty/blob/04659bec64d98cc483c9288f91b04a5b274989bb/.github/workflows/ci.yaml#L99
And the Docker container used is defined as follows: https://github.com/lampepfl/dotty-ci/blob/master/dotty-docker/Dockerfile

@anatoliykmetyuk
Copy link
Contributor

Is it possible to disable these tests in the dotty-staging fork so that the entire CI doesn't fail non-deterministically?

@vasilmkd
Copy link
Contributor Author

I will push a commit to do that in a bit, is that ok?

@vasilmkd
Copy link
Contributor Author

I opened a PR here.
dotty-staging/cats-effect#1

@vasilmkd
Copy link
Contributor Author

@anatoliykmetyuk @smarter What does the process for keeping the dotty-staging/cats-effect fork up to date with upstream? For example, we have a fix for the flaky tests pushed to typelevel/cats-effect and we'd like to incorporate them into the community build. How do we do that? Is it maybe possible to restore the git histories to be identical, since they have diverged with the commit that disabled the flaky tests. Thank you.

cc @djspiewak

@smarter
Copy link
Member

smarter commented Sep 19, 2020

Is it maybe possible to restore the git histories to be identical, since they have diverged with the commit that disabled the flaky tests.

Yes, but we have to keep the old history in a branch in the fork, so that each dotty commit still points to reachable commits in the submodules.

@vasilmkd
Copy link
Contributor Author

vasilmkd commented Sep 19, 2020

This might be a stupid question, I just want to be sure I understood correctly. If I want to restore the series/2.x (the main branch) to its current state as it is in typelevel/cats-effect, I should first branch off the current series/2.x branch in dotty-staging/cats-effect in order to save the history and force push the main branch?

@smarter
Copy link
Member

smarter commented Sep 19, 2020

Yes, and push the saved branch too :) I suggest putitng the date in the name of the branch.

@vasilmkd
Copy link
Contributor Author

@smarter Does series/2.x-20.09.2020 work?

@smarter
Copy link
Member

smarter commented Sep 19, 2020

There's only one true date format: https://xkcd.com/1179/ :)

@vasilmkd
Copy link
Contributor Author

vasilmkd commented Sep 19, 2020

Agreed. 😆

@vasilmkd
Copy link
Contributor Author

vasilmkd commented Sep 19, 2020

https://github.com/dotty-staging/cats-effect/tree/series/2.x-2020-09-20

I will go ahead and force push series/2.x.

@vasilmkd
Copy link
Contributor Author

Thank you @smarter for the quick replies and the help.

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.

5 participants