-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Sproradic (but frequent) JS build failures #1242
Comments
ceedubs
added a commit
to ceedubs/cats
that referenced
this issue
Jul 30, 2016
This is a shot in the dark attempting to fix typelevel#1242. The idea is that we can mark certain tests as slow and not run them when running JS tests. Currently I've done this for all of the stack-safety tests that I can find. I don't really like this solution, but currently almost every PR is resulting in a failed build, which is really problematic. One thing that we could do is get rid of the `Platform.isJs` branch of the `slowTest` implementation locally just before a release to make sure that these tests all pass on JS. I think we only really run into these issues on Travis CI.
ceedubs
added a commit
to ceedubs/cats
that referenced
this issue
Jul 31, 2016
This is a shot in the dark attempting to fix typelevel#1242. The idea is that we can mark certain tests as slow and not run them when running JS tests. Currently I've done this for all of the stack-safety tests that I can find. I don't really like this solution, but currently almost every PR is resulting in a failed build, which is really problematic. One thing that we could do is get rid of the `Platform.isJs` branch of the `slowTest` implementation locally just before a release to make sure that these tests all pass on JS. I think we only really run into these issues on Travis CI.
kailuowang
added a commit
that referenced
this issue
Aug 3, 2016
Split build tasks on travis fixes #1242
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recently we started seeing the following sporadic build failures (during JS phase). Do any folks with scala.js experience know what might be going on here?
I think that the first time that I noticed it was after #1231, but I'm not sure. I'm pretty sure that I did see this happen at least once before the recent switch from scala.js 0.6.8 to 0.6.11.
Below is an excerpt from the logs. You can also look at this Travis build starting on line 9132.
The text was updated successfully, but these errors were encountered: