These errors are not your fault. The appveyor one is known but we haven't
reproduced it locally yet, the Travis one is intermittent but also not your
fault.

Sam

On Wed, May 23, 2018, 5:41 PM William J. Bowman <w...@williamjbowman.com>
wrote:

> I submitted a pull request, and both Travis and AppVeyor are failing for
> no apparent reason.
> For one, the PR is only changed documentation and shouldn't affect any
> tests.
>   https://github.com/racket/racket/pull/2076
>
> The first time, it looked like Travis just timed out... shortly after all
> tests passed.
> I forced it to rerun, and most of the Travis builds passed... but one
> failed with a mysterious error:
>   "Users/travis/.travis/job_stages: line 166: shell_session_update:
> command not found"
>
> AppVeyor shows all tests pass, but errors with
>   "Command exited with code -1073740940".
>
> I notice many other PRs show CI failing.
> Is this my fault and I just can't debug, or is something going on with the
> CI?
>
> --
> William J. Bowman
> Northeastern University
> College of Computer and Information Science
>
> --
> You received this message because you are subscribed to the Google Groups
> "Racket Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to racket-dev+unsubscr...@googlegroups.com.
> To post to this group, send email to racket-dev@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/racket-dev/20180523214111.GA1052%40williamjbowman.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-dev+unsubscr...@googlegroups.com.
To post to this group, send email to racket-dev@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-dev/CAK%3DHD%2BaMPzN4SUt0t1rGrAQqRneaEW6SLRdkKD-FRZfWOXn6ZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to