-
Notifications
You must be signed in to change notification settings - Fork 166
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.
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
Request access to benchmark CI #3118
Comments
Added key to anonrig@92.51.196.115 (test-nearform_intel-ubuntu1604-x64-2) so you should be able to log in there, although @targos has marked it offline in jenkins for an upgrade so it's availability may not be clear :-) |
This machine is longer running on Ubuntu 16.04. I started upgrading it to 18.04 yesterday (#3122) |
I don't have access anymore. Would someone be able to add me back? @nodejs/build |
What do you need access for? |
@targos Run benchmarks specifically for URL parser, as well as understand the architecture/processor of the benchmark CI machine. |
Can't you use the existing CI job(s) for that?
Hardware is described here: #791 (comment) Note that the machine is currently offline, so that explains why you can't access it. |
Unfortunately, going through the flow of CI jobs while trying to improve a certain part of Node is too time-consuming and having direct access to the resources (where the user does not have the necessary computing power to run the benchmark) will resolve the friction of contributing to performance-critical problems in Node.js |
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
Our benchmark CI runs on Ubuntu 16.04 and my pull request to add
simdutf
had a vague issue. I'd like to get access to the machine to understand the root cause of the issue.Referencing nodejs/node#45803 (comment)
The text was updated successfully, but these errors were encountered: