Try putting the :1666 one in Mirror Path. Christian
-- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Mar 30, 2011 at 4:19 PM, Vincent Yee <v...@sendmail.com> wrote: > I get a different error message if I have :1666 on my repository entry > (Got API Error 206 (HTTP code 200) > > > > $ post-review --debug --summary=p4-testing-change > > >>> RBTools 0.3.2 > > >>> Home = /home/build > > >>> svn info > > >>> p4 info > > >>> repository info: Path: repoman.smi.sendmail.com:1666, Base path: None, > Supports changesets: True > > >>> HTTP GETting api/ > > >>> HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/ > > >>> Using the new web API > > >>> Generating diff for changenum default > > >>> p4 opened -c default > > >>> Processing edit of //depot/Iocaine/main/Product/build.xml > > >>> Writing "//depot/Iocaine/main/Product/build.xml#197" to > "/tmp/tmpIdYR5a" > > >>> p4 print -o /tmp/tmpIdYR5a -q > //depot/Iocaine/main/Product/build.xml#197 > > >>> diff -urNp /tmp/tmpIdYR5a > /home/build/build_client/Iocaine/main/Product/build.xml > > >>> Using changenums on Review Board 1.5.2. Falling back to the deprecated > 1.0 API > > ==> Review Board Login Required > > Enter username and password for Review Board at > http://vmreviews.lab-example.com/reviews/ > > >>> Looking for 'vmreviews.qa-lab.sendmail.com /reviews/' cookie in > /home/build/.post-review-cookies.txt > > >>> Loaded valid cookie -- no login required > > >>> Attempting to create review request on perforce.example.com for None > > >>> HTTP POSTing to > http://vmreviews.qa-lab.sendmail.com/reviews/api/json/reviewrequests/new/: > {'repository_path': 'perforce.smi.sendmail.com'} > > >>> Got API Error 206 (HTTP code 200): The repository path specified is not > in the list of known repositories > > >>> Error data: {u'repository_path': u'perforce.example.com', u'stat': > u'fail', u'err': {u'msg': u'The repository path specified is not in the list > of known repositories', u'code': 206}, u'deprecated': {u'in_version': > u'1.5'}} > > > > There was an error creating this review request. > > > > The repository path "repoman.example.com:1666" is not in the > > list of known repositories on the server. > > > > Ask the administrator to add this repository to the Review Board server. > > For information on adding repositories, please read > > http://www.reviewboard.org/docs/manual/dev/admin/management/repositories/ > > > ------------------------------ > > *From:* chip...@gmail.com [mailto:chip...@gmail.com] *On Behalf Of *Christian > Hammond > *Sent:* Wednesday, March 30, 2011 4:08 PM > *To:* Vincent Yee > *Cc:* reviewboard@googlegroups.com > > *Subject:* Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200): > One or more fields had errors > > > > The repository entry you showed doesn't seem to have :1666? Try adding the > port. > > Christian > > -- > Christian Hammond - chip...@chipx86.com > Review Board - http://www.reviewboard.org > VMware, Inc. - http://www.vmware.com > > On Wed, Mar 30, 2011 at 4:00 PM, Vincent Yee <v...@sendmail.com> wrote: > > On my client I have set > > export P4PORT=perforce.example.com:1666 > > > > Ping perforce.example.com works > > PING repoman.example.com (x.y.z.a) 56(84) bytes of data. > > 64 bytes from repoman.example.com (x.y.z.a): icmp_seq=1 ttl=63 time=0.504 > ms > > 64 bytes from repoman.example.com (x.y.z.a): icmp_seq=2 ttl=63 time=0.335 > ms > > > > $ telnet perforce.example.com 1666 > > Trying x.y.z.a... > > Connected to perforce.example.com (x.y.z.a). > > Escape character is '^]'. > > ;;xfiles5server3server217funprotocol^] > > telnet> > ------------------------------ > > *From:* chip...@gmail.com [mailto:chip...@gmail.com] *On Behalf Of *Christian > Hammond > *Sent:* Wednesday, March 30, 2011 3:41 PM > *To:* reviewboard@googlegroups.com > *Cc:* Vincent Yee > *Subject:* Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200): > One or more fields had errors > > > > Sounds like the Review Board server isn't able to contact your Perforce > server for some reason. Might want to try SSHing into that server, > temporarily setting P4PORT in your session, and accessing the server. Or try > pinging it for an initial test. > > Christian > > -- > Christian Hammond - chip...@chipx86.com > Review Board - http://www.reviewboard.org > VMware, Inc. - http://www.vmware.com > > On Wed, Mar 30, 2011 at 3:36 PM, storms <v...@sendmail.com> wrote: > > trying to setup post-review with perforce got the following error. > > I am able to ping and telnet to the perforce server from my > client.... my repository setting is: > Hosting service: Custom > Repository type: Perforce > Path: perforce.example.com > Username: <useranme> > Password: <password> > > $ post-review --debug --summary=p4-testing-change > >>> RBTools 0.3.2 > >>> Home = /home/build > >>> svn info > >>> p4 info > >>> repository info: Path: repoman.example.com:1666, Base path: None, > Supports changesets: True > >>> HTTP GETting api/ > >>> HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/ > >>> Using the new web API > >>> Generating diff for changenum default > >>> p4 opened -c default > >>> Processing edit of //depot/Iocaine/main/Product/build.xml > >>> Writing "//depot/Iocaine/main/Product/build.xml#197" to > "/tmp/tmpzT7Exi" > >>> p4 print -o /tmp/tmpzT7Exi -q > //depot/Iocaine/main/Product/build.xml#197 > >>> diff -urNp /tmp/tmpzT7Exi > /home/build/build_client/Iocaine/main/Product/build.xml > >>> Using changenums on Review Board 1.5.2. Falling back to the deprecated > 1.0 API > ==> Review Board Login Required > Enter username and password for Review Board at > http://vmreviews.lab-example.com/reviews/ > >>> Looking for 'vmreviews.lab-example /reviews/' cookie in > /home/build/.post-review-cookies.txt > >>> Loaded valid cookie -- no login required > >>> Attempting to create review request on perforce.example.com for None > >>> HTTP POSTing to > http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/new/: > {'repository_path': 'perforce.example.com'} > >>> Review request created > >>> Attempting to set field 'summary' to 'p4-testing-change' for review > request '12' > >>> HTTP POSTing to > http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/12/draft/set/: > {'summary': 'p4-testing-change'} > >>> Uploading diff, size: 361 > >>> HTTP POSTing to > http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/12/diff/new/: > {} > >>> Got API Error 105 (HTTP code 200): One or more fields had errors > >>> Error data: {u'fields': {u'path': [u'[P4.connect()] Connect to server > failed; check $P4PORT.\nTCP connect to perforce.example.com failed.\ > nperforce.example.com: service unknown.\n']}, u'stat': u'fail', u'err': > {u'msg': u'One or more fields had errors', u'code': 105}, u'deprecated': > {u'in_version': u'1.5'}} > > Error uploading diff > > The generated diff file was empty. This usually means no files were > modified in this change. > > Try running with --output-diff and --debug for more information. > > Your review request still exists, but the diff is not attached. > > $ post-review --debug --summary=p4-testing-change --output-diff > >>> RBTools 0.3.2 > >>> Home = /home/build > >>> svn info > >>> p4 info > >>> repository info: Path: repoman.example.com:1666, Base path: None, > Supports changesets: True > >>> HTTP GETting api/ > >>> HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/ > >>> Using the new web API > >>> Generating diff for changenum default > >>> p4 opened -c default > >>> Processing edit of //depot/Iocaine/main/Product/build.xml > >>> Writing "//depot/Iocaine/main/Product/build.xml#197" to > "/tmp/tmpDCtOBl" > >>> p4 print -o /tmp/tmpDCtOBl -q > //depot/Iocaine/main/Product/build.xml#197 > >>> diff -urNp /tmp/tmpDCtOBl > /home/build/build_client/Iocaine/main/Product/build.xml > >>> Using changenums on Review Board 1.5.2. Falling back to the deprecated > 1.0 API > --- //depot/Iocaine/main/Product/build.xml //depot/Iocaine/main/ > Product/build.xml#197 > +++ //depot/Iocaine/main/Product/build.xml 2011-03-30 06:09:25 > @@ -1,4 +1,5 @@ > <project name="Iocaine" default="all-nodist" basedir="."> > +<project name="Iocaine" default="all-nodist" basedir="."> > <property environment="env" /> > > <property name="src_dir" value="src/" /> > $ > > > what does "check $P4PORT.\nTCP connect to perforce.example.com > failed." mean? > > -- > Want to help the Review Board project? Donate today at > http://www.reviewboard.org/donate/ > Happy user? Let us know at http://www.reviewboard.org/users/ > -~----------~----~----~----~------~----~------~--~--- > To unsubscribe from this group, send email to > reviewboard+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/reviewboard?hl=en > > > > > -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~----------~----~----~----~------~----~------~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
