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

Tracking Stability of v4.x-staging #4937

Closed
MylesBorins opened this issue Jan 28, 2016 · 2 comments
Closed

Tracking Stability of v4.x-staging #4937

MylesBorins opened this issue Jan 28, 2016 · 2 comments
Labels
meta Issues and PRs related to the general management of the project.

Comments

@MylesBorins
Copy link
Contributor

There are over 60 new commits on v4.x-staging.

Running CI + citgm and tracking problems in here.

CI: https://ci.nodejs.org/job/node-test-commit/1966/

citgm: https://ci.nodejs.org/job/thealphanerd-smoker/50/
@mscdex mscdex added meta Issues and PRs related to the general management of the project. v4.x labels Jan 28, 2016
@Trott
Copy link
Member

Trott commented Jan 28, 2016

Seems probable that the one failure (so far) on Raspberry Pi (test-dgram-send-empty-buffer.js) could be improved with a common.platformTimeout(). I'll get a PR in for that.

@Trott Trott mentioned this issue Jan 29, 2016
Closed
Trott added a commit to Trott/io.js that referenced this issue Jan 29, 2016
@Trott
test: add common.platformTimeout() to dgram test
18f930c 
Use common.platformTimeout() to mitigate potential for CI to timeout
on slower devices.

Ref: nodejs#4937
@MylesBorins
Copy link
Contributor Author

The only citgm failure is expected (eslint on ppc).

Closing

Trott added a commit to Trott/io.js that referenced this issue Jan 31, 2016
@Trott
test: add common.platformTimeout() to dgram test
d319561 
Use common.platformTimeout() to mitigate potential for CI to timeout
on slower devices.

Ref: nodejs#4937
PR-URL: nodejs#4938
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
rvagg pushed a commit that referenced this issue Feb 8, 2016
@Trott @rvagg
test: add common.platformTimeout() to dgram test
443d046 
Use common.platformTimeout() to mitigate potential for CI to timeout
on slower devices.

Ref: #4937
PR-URL: #4938
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
MylesBorins pushed a commit that referenced this issue Feb 17, 2016
@Trott
test: add common.platformTimeout() to dgram test
df9844e 
Use common.platformTimeout() to mitigate potential for CI to timeout
on slower devices.

Ref: #4937
PR-URL: #4938
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
MylesBorins pushed a commit that referenced this issue Feb 18, 2016
@Trott
test: add common.platformTimeout() to dgram test
226dfef 
Use common.platformTimeout() to mitigate potential for CI to timeout
on slower devices.

Ref: #4937
PR-URL: #4938
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
MylesBorins pushed a commit that referenced this issue Mar 2, 2016
@Trott
test: add common.platformTimeout() to dgram test
edc2df9 
Use common.platformTimeout() to mitigate potential for CI to timeout
on slower devices.

Ref: #4937
PR-URL: #4938
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
scovetta pushed a commit to scovetta/node that referenced this issue Apr 2, 2016
@Trott
test: add common.platformTimeout() to dgram test
45ac61b 
Use common.platformTimeout() to mitigate potential for CI to timeout
on slower devices.

Ref: nodejs#4937
PR-URL: nodejs#4938
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
meta Issues and PRs related to the general management of the project.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mscdex @MylesBorins @Trott