Bug 1447208 - Need a NetBSD machine to debug regression failure
Summary: Need a NetBSD machine to debug regression failure
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: build
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nigel Babu
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-02 06:31 UTC by Sanoj Unnikrishnan
Modified: 2017-05-05 10:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-05 10:18:01 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)
public key id_rsa.pub (420 bytes, text/plain)
2017-05-02 06:31 UTC, Sanoj Unnikrishnan 		no flags Details
View All

Description Sanoj Unnikrishnan 2017-05-02 06:31:38 UTC 
Created attachment 1275570 [details]
public key id_rsa.pub

I would like to debug the regression failure in https://review.gluster.org/#/c/16938/. Need a setup for the same

PFA, my public key
Comment 1 Nigel Babu 2017-05-02 08:30:05 UTC 
You should be able to SSH in as jenkins.gluster.org. Let me know if you run into any troubles. The NetBSD machines are a little special. The tools are almost like Linux, but not quite. For starters, after you ssh in, you might want to do switch to bash rather than sh. Just type `bash`. I'd also recommend taking a look at the scripts in /opt/qa, especially build.sh and regression.sh. It's different from our usual regression scripts.

Most recently Hari has worked on NetBSD and I suspect Nithya knows the developer environment better than I do.
Comment 2 Sanoj Unnikrishnan 2017-05-05 10:15:22 UTC 
Thanks for the setup. wiki page was helpful
Note You need to log in before you can comment on or make changes to this bug.