Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
test: improve performance of stringbytes test
String concatenation in the assert messages has drastic impact on test runtime. Removal of these messages is unlikely to affect debugging if any breaking changes are made. Previous time to run: $ time ./iojs test/parallel/test-stringbytes-external.js real 0m2.321s user 0m2.256s sys 0m0.092s With fix: $ time ./iojs test/parallel/test-stringbytes-external.js real 0m0.518s user 0m0.508s sys 0m0.008s PR-URL: #2544 Reviewed-By: trevnorris - Trevor Norris <trev.norris@gmail.com> Reviewed-By: thefourtheye - Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
- Loading branch information
37ee43e
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.
@orangemocha if you're going to totally screw with someone's commit make sure you fill in the fields correctly. This commit is for PR #2410.
37ee43e
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.
@trevnorris sorry, I was trying to help, not sure what happened. Did you get my emails?
It looks like both commits were on that branch: https://github.com/nodejs/node/compare/reland-landed-commitss
37ee43e
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.
Hmmm ok, I see, it looks like you meant to land both commits with one job, but they had different PR-URL. That's currently not possible, because the merge job always strips any existing PR-URL and Reviewed-By, then tries to stick the one in the form. I'll make a change to support this scenario. Sorry about the confusion.
37ee43e
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.
@orangemocha My comment was overly reactive. My apologies. After getting these two commits re-landed was surprised/frustrated to see that the
PR-URL
field had been altered. Though now I understand much better how the CI works.37ee43e
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.
@trevnorris no worries. It's good feedback: nodejs/build#179. Please chip in with any suggestions in there. Until it's fixed, please let me know if you need any help working around this limitation.