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.

Sign up for GitHub

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

Jump to bottom

[ci] × src » message » ready() contact ready for ToNickName #445

Closed
huan opened this issue Apr 28, 2017 · 1 comment
Closed

[ci] × src » message » ready() contact ready for ToNickName #445

huan opened this issue Apr 28, 2017 · 1 comment
Labels
bug

Comments

@huan
Copy link
Member

huan commented Apr 28, 2017 •
edited
Loading

Appveyor CI on Windows always fails on message unit test at:

  × src » message » ready() contact ready for ToNickName

src » message » ready()
  C:\projects\wechaty\dist\src\message.spec.js:10
                                                           
  Difference:
  "To Nick Name@Test"
  contact ready for ToNickName

Since 2 days ago.

At the same time, all code run under Linux/Mac/Docker without any problem.(?)

CI Log:

  1. https://ci.appveyor.com/project/Chatie/wechaty/build/877#L99
@huan huan added the bug label Apr 28, 2017
@huan huan changed the title [ci log] × src » message » ready() contact ready for ToNickName [test] × src » message » ready() contact ready for ToNickName May 6, 2017
@huan huan changed the title [test] × src » message » ready() contact ready for ToNickName [ci] × src » message » ready() contact ready for ToNickName May 12, 2017
huan added a commit that referenced this issue May 12, 2017
@huan
log(message): try to find out why win32 can not get to() (#445)
ca6dcd1
huan added a commit that referenced this issue May 12, 2017
@huan
log(message): try to find out why win32 can not get to() (#445)
3e2e8e2
huan added a commit that referenced this issue May 12, 2017
@huan
log(message): try to find out why win32 can not get to() (#445)
495db7b
huan added a commit that referenced this issue May 12, 2017
@huan
log(message): try to find out why win32 can not get to() (#445)
1206d53
huan added a commit that referenced this issue May 12, 2017
@huan
log(message): try to find out why win32 can not get to() (#445)
54a85e5
huan added a commit that referenced this issue May 12, 2017
@huan
log(message): try to find out why win32 can not get to() (#445)
b6d8b06
huan added a commit that referenced this issue May 12, 2017
@huan
log(message): try to find out why win32 can not get to() (#445)
2d9725f
@huan huan closed this as completed in 441f64a May 12, 2017
@huan
Copy link
Member Author

huan commented May 12, 2017

2d9725f fixed this.

test.serial()

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@huan