Skip to content
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

Report portal connection error appears, when REPORT_PORTAL_BASE_URL=http://localhost:8080 #4

Closed
IegorZabielin-KSO opened this issue Apr 13, 2019 · 11 comments

Comments

@IegorZabielin-KSO
Copy link
Contributor

IegorZabielin-KSO commented Apr 13, 2019

  1. Spin up Report Portal locally.
  2. Create .env file, specify REPORT_PORTAL_BASE_URL=http://localhost:8080
  3. testcafe v.1.1.2. (also tried on 0.23.3).
  4. Trigger any test execution.

Actual result: Error is logged
Error connecting to ReportPortal, confirm that your details are correct.
Error: Request failed with status code 404: {"timestamp":1555152511909,"status":404,"error":"Not Found","message":"No message available","path":"/api/v1/fnn_test/user"}
at axios.then.catch (/Users/izabielin/Documents/GitHub/fnn-portal/node_modules/reportportal-client/lib/rest.js:27:23)
at
at process._tickDomainCallback (internal/process/next_tick.js:228:7)

Even with such error, test results are added on the Report Portal.

@redfox256
Copy link
Owner

Unable to replicate with the new fix v1.0.18 - please test

@IegorZabielin-KSO
Copy link
Contributor Author

Unfortunately it is reproduced
Screenshot at Apr 18 15-16-05

@redfox256
Copy link
Owner

There seems to be an issue with the reportportal-client being used. I will keep monitoring till fixed.

@kerly
Copy link

kerly commented May 10, 2019

I am noticing this same error when attempting to configure with an externally hosted reportportal (not localhost).

@IegorZabielin-KSO
Copy link
Contributor Author

@kerly yes, it is reproduced not only on localhost...unfortunately

@ampc
Copy link

ampc commented May 22, 2019

Also happening here 👍

 testcafe chrome tests/specs/login/login.spec.ts --reporter reportportal                                                                                                                          
Using locally installed version of TestCafe.
Running tests in: Chrome 74.0.3729 / Linux 0.0.0

[Login]
Error connecting to ReportPortal, confirm that your details are correct.
Error: Request failed with status code 404: {"timestamp":1558519345518,"status":404,"error":"Not Found","message":"No message available","path":"/api/v1/superadmin_personal/user"}
    at axios.then.catch (/home/ampc/repos/automated_tests/QA_Tests/e2e_smart/node_modules/reportportal-js-client/lib/rest.js:27:23)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  [ ✓ ] R-1001 | Login with correct credentials
  [ ✖ ] R-1002 | Login with wrong credentials

@aadhithlmi
Copy link

aadhithlmi commented May 28, 2019

Unfortunately I am also getting the same error

PS C:\Code\testcafe> testcafe chrome test01.js --reporter reportportal
Using locally installed version of TestCafe.
Running tests in: Chrome 74.0.3729 / Windows 10.0.0

[Getting Started]
Error connecting to ReportPortal, confirm that your details are correct.
Error: Request failed with status code 404: {"timestamp":1559081127097,"status":404,"error":"NotFound","message":"No message available","path":"/api/v1/axdynamics/user"}
at axios.then.catch (C:\Code\testcafe\node_modules\reportportal-js-client\lib\rest.js:27:23)
at process._tickCallback (internal/process/next_tick.js:68:7)
[ ✓ ] My first test

@kerly
Copy link

kerly commented Jun 18, 2019

I updated to the newest version of this package (1.0.22) and it looks like this is fixed now. Can others confirm?

@redfox256
Copy link
Owner

I've updated the reportportal-js-client library to the latest version v1.0.2 which mentions connection issue fixes.
Please can you confirm that it's fixed in the current version released v1.0.23

@kerly
Copy link

kerly commented Jun 19, 2019

I tried v1.0.23 and I'm not seeing the reported error anymore.

@IegorZabielin-KSO
Copy link
Contributor Author

@kerly, @redfox256 confirming issus is fixed in v1.0.23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants