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

Failed to finish nested step. Error: timeout of 30000ms exceeded. URL:... method: POST. Error starts randomly throwing in the middle of test execution. #160

Open
toduyemi opened this issue Nov 6, 2024 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@toduyemi
Copy link

toduyemi commented Nov 6, 2024

Describe the bug
Hi in the middle of a test execution, sometimes i'll start getting non-playwright errors like this. I can't find anything in the documentation. Usually if a test times out, the terminal prints a playwright error, fails the test which makes it difficult to understand why i'm getting this weird report portal exception about timeouts. If I click the link(s), it tells me I'm not authorized to view page.

The test execution always starts of normally but somewhere in there reportportal starts to throw exceptions. There is no documentation on how to troubleshoot such an issue. The behaviour has been unpredictable to my eyes but definitely has increased in frequency in the last week or two. To the point, I can't get through a whole test execution. The only thing that's changed is an increase in the number of tests.

Expected behavior
For the terminal to only print line results from playwright.

Screenshots

Screen.Recording.2024-11-04.at.3.36.57.PM.mov
Screenshot 2024-11-06 at 12 34 35 PM

Versions:

  • OS, Browser - macOS Sonoma Google Chrome
    "@playwright/test": "^1.47.2",
    "@reportportal/agent-js-playwright": "^5.1.9",
@toduyemi toduyemi added the bug Something isn't working label Nov 6, 2024
@toduyemi
Copy link
Author

toduyemi commented Nov 13, 2024

Screenshot 2024-11-13 at 3 11 20 PM After removing the timeout limit in the report portal config. I am now getting this. This error has also shown.
Error: Request failed with status code 500: {"errorCode":5000,"message":
"Unclassified error [Maximum upload size of 134217728 bytes exceeded; nested exception is org.apache.commons.fileupload.FileUploadBase$SizeLimitExceededException: 
the request was rejected because its size (448899054) exceeds the configured maximum (134217728)]"}
URL: http://localhost:8080/api/v2/superadmin_personal/log
method: POST

I've torn down and redeployed the docker-compose to no effect. I'd really appreciate some help troubleshooting this or at least a direction if more info is needed.

@AmsterGet
Copy link
Member

Hello @toduyemi !
I assume that timeout errors can be caused by uploading large files that are not within the acceptable size range defined by the ReportPortal server.
So, if you need to upload such files and there is no way to compress them, try increasing the allowable file size on the server side.
I'll share the link on how to do this a bit later.
I also suggest using the api/v2 endpoint to report data via the ReportPortal Async API for better performance.

@AmsterGet AmsterGet self-assigned this Nov 19, 2024
@AmsterGet
Copy link
Member

You can change the file upload limits by providing env variables to docker-compose for service api:
RP_UPLOAD_MAXUPLOADSIZE: 128MB
RP_UPLOAD_MAXFILESIZE: 64MB

@toduyemi
Copy link
Author

toduyemi commented Nov 26, 2024

@AmsterGet I tried the suggestion and I'm still getting this exception thrown.

I assume that timeout errors can be caused by uploading large files that are not within the acceptable size range defined by the ReportPortal server.
So, if you need to upload such files and there is no way to compress them, try increasing the allowable file size on the server side.

If files are being uploaded, they're files that RP uploads out-of-box. I haven't made any changes with regards to file uploads or test artifacts. I don't know what "such files" would be.

api:
    image: reportportal/service-api:5.12.1
    logging:
      <<: *logging
    depends_on:
      rabbitmq:
        condition: service_healthy
      gateway:
        condition: service_started
      postgres:
        condition: service_healthy
    environment:
      <<: *common-environment
      LOGGING_LEVEL_ORG_HIBERNATE_SQL: info
      RP_REQUESTLOGGING: "false"
      AUDIT_LOGGER: "OFF"
      MANAGEMENT_HEALTH_ELASTICSEARCH_ENABLED: "false"
      RP_ENVIRONMENT_VARIABLE_ALLOW_DELETE_ACCOUNT: "false"
      JAVA_OPTS: >
        -Xmx1g 
        -XX:+HeapDumpOnOutOfMemoryError 
        -XX:HeapDumpPath=/tmp  
        -Dcom.sun.management.jmxremote.rmi.port=12349 
        -Dcom.sun.management.jmxremote 
        -Dcom.sun.management.jmxremote.local.only=false  
        -Dcom.sun.management.jmxremote.port=9010 
        -Dcom.sun.management.jmxremote.authenticate=false 
        -Dcom.sun.management.jmxremote.ssl=false 
        -Djava.rmi.server.hostname=0.0.0.0
      RP_JOBS_BASEURL: http://jobs:8686
      COM_TA_REPORTPORTAL_JOB_INTERRUPT_BROKEN_LAUNCHES_CRON: PT1H
      RP_ENVIRONMENT_VARIABLE_PATTERN-ANALYSIS_BATCH-SIZE: 100
      RP_ENVIRONMENT_VARIABLE_PATTERN-ANALYSIS_PREFETCH-COUNT: 1
      RP_ENVIRONMENT_VARIABLE_PATTERN-ANALYSIS_CONSUMERS-COUNT: 1
      COM_TA_REPORTPORTAL_JOB_LOAD_PLUGINS_CRON: PT10S
      COM_TA_REPORTPORTAL_JOB_CLEAN_OUTDATED_PLUGINS_CRON: PT10S
      REPORTING_QUEUES_COUNT: 10
      REPORTING_CONSUMER_PREFETCHCOUNT: 10
      REPORTING_PARKINGLOT_TTL_DAYS: 7
      RP_UPLOAD_MAXUPLOADSIZE: 128MB
      RP_UPLOAD_MAXFILESIZE: 64MB
    volumes:
      - storage:/data/storage

Did I put the env variables in the correct place?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants