Skip to content

Conversation

mhdawson
Copy link
Member

@mhdawson mhdawson commented Dec 4, 2017

ARM6 takes longer, more often fails builds than other
platforms. Add instructions for how to recover in this
case.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

doc

@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label Dec 4, 2017
@mhdawson mhdawson requested a review from gibfahn December 4, 2017 15:28
@mscdex mscdex added the build Issues and PRs related to build files or the CI. label Dec 4, 2017
doc/releases.md Outdated
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good to specify the names of those sections in case the numbering gets changed later.

doc/releases.md Outdated
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like it should be part of the step above:

If you didn't wait for ARM builds in the previous step before promoting the release, you should re-run tools/release.sh after the ARM builds have finished. That will move the ARM artifacts into the correct location. You will be prompted to re-sign SHASUMS256.txt.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel it at least should not be after 17. Celebrate (which implies everything is done). As @gibfahn points out, it's already kind of mentioned in 12. Promote and Sign the Release Builds but maybe it's not prominent enough because we have frequently forgotten to promote them (e.g. nodejs/nodejs.org#1382).

Also is there any particular reason to include the 6 and not just say ARM?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is only the ARMv6 builds that are really slow.

@mhdawson
Copy link
Member Author

mhdawson commented Dec 4, 2017

@gibfahn updated to merge into that step.

Copy link
Member

@gibfahn gibfahn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with suggestion.

doc/releases.md Outdated
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe make it:

[`iojs-release-arm6-only`](https://ci-release.nodejs.org/job/iojs+release-arm6-only/)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@gibfahn
Copy link
Member

gibfahn commented Dec 4, 2017

cc/ @nodejs/release

doc/releases.md Outdated
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit - Since the other sentences only use a single whitespace after a sentence, I would suggest to do the same here?

@mhdawson
Copy link
Member Author

mhdawson commented Dec 7, 2017

Will do, its hard to overcome many years at school (in the past) where 2 spaces was the only way :)

@mhdawson
Copy link
Member Author

mhdawson commented Dec 8, 2017

@mhdawson
Copy link
Member Author

mhdawson commented Dec 8, 2017

CI looks good landing.

ARM6 takes longer, more often fails builds than other
platforms.  Add instructions for how to recover in this
case.
@mhdawson
Copy link
Member Author

mhdawson commented Dec 8, 2017

Landed as 4e65f9d

@mhdawson mhdawson closed this Dec 8, 2017
mhdawson added a commit that referenced this pull request Dec 8, 2017
ARM6 takes longer, more often fails builds than other
platforms.  Add instructions for how to recover in this
case.

PR-URL: #17455
Reviewed-By: Gibson Fahnestock <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
MylesBorins pushed a commit that referenced this pull request Dec 12, 2017
ARM6 takes longer, more often fails builds than other
platforms.  Add instructions for how to recover in this
case.

PR-URL: #17455
Reviewed-By: Gibson Fahnestock <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
MylesBorins pushed a commit that referenced this pull request Dec 12, 2017
ARM6 takes longer, more often fails builds than other
platforms.  Add instructions for how to recover in this
case.

PR-URL: #17455
Reviewed-By: Gibson Fahnestock <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
@MylesBorins MylesBorins mentioned this pull request Dec 12, 2017
gibfahn pushed a commit that referenced this pull request Dec 20, 2017
ARM6 takes longer, more often fails builds than other
platforms.  Add instructions for how to recover in this
case.

PR-URL: #17455
Reviewed-By: Gibson Fahnestock <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
@gibfahn gibfahn mentioned this pull request Dec 20, 2017
gibfahn pushed a commit that referenced this pull request Dec 20, 2017
ARM6 takes longer, more often fails builds than other
platforms.  Add instructions for how to recover in this
case.

PR-URL: #17455
Reviewed-By: Gibson Fahnestock <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
@gibfahn gibfahn mentioned this pull request Dec 20, 2017
@mhdawson mhdawson deleted the arm branch September 30, 2019 13:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Issues and PRs related to build files or the CI. doc Issues and PRs related to the documentations.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants