This repository has been archived by the owner on May 4, 2018. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Unreliable, it's timing / system load sensitive.
- Loading branch information
1 parent
ce28e13
commit 28766dc
Showing
3 changed files
with
0 additions
and
92 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
28766dc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bnoordhuis Thanks. All current tests in libuv have just been passed in my environment. I was going to make a patch to uv_timer instead for this test. How are you going to do with test-callback-order.c? It's been disabled. I wonder whether libuv is to be fixed or not.
28766dc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The test has been reworked in the next-tick branch (8143d76). It's TBD if we're going to define callback order with that level of detail.
28766dc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. I understand test-next-tick-ordering2.js of Node is left to be failed for some time.