Skip to content

Some attachments are not displayed. #240

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

Open
netolyrg opened this issue Oct 11, 2024 · 5 comments
Open

Some attachments are not displayed. #240

netolyrg opened this issue Oct 11, 2024 · 5 comments

Comments

@netolyrg
Copy link

Describe the bug
I am facing the “attachments” problem for Report Portal in all tests: on some runs, the attachments are not displayed and the log is broken into several identical parts (2-8 logs). There are no errors in the server logs.

I don't understand how to debug such a problem. I can gather more information about the environment if someone can help solve this problem.

Steps to Reproduce

  1. Launch 2 or more runs of the same test consecutively

Expected behavior
All attachments are visible in all launches.

Actual behavior
On some runs, the attachments are not displayed.

Package versions
Include version info of the following packages: reportportal-client == 5.5.6

Additional context
Report Portal 5.11.0
Environment: K8s, storage type: (minio, single), 100+ distributed sync clients.

1
2

@netolyrg netolyrg added the bug label Oct 11, 2024
@HardNorth
Copy link
Member

@netolyrg We had such issue on server side in service-api 5.10.0, but this was fixed in 5.10.1. Can you provide any more details?

  1. Which test framework do you use? And the agent version? If you are not using any Agent please confirm that you use RPClient class instance (different client implementations use different HTTP clients under the hood).
  2. How big is your attachments? It doesn't look big, but just confirm.
  3. Did you adjust log_batch_size: int and log_batch_payload_size: int arguments?
  4. Do you see any errors in console log, or on service-api side?
  5. How was the load on the server when such issues happens?

@netolyrg
Copy link
Author

Hi!
serviceapi: v5.11.0

  1. We use RPClient v5.5.6
  2. Not so big, average size < 1MB (png screenshot)
  3. Yes, but it did't help and due to our test launcher architecture we can't increase log_batch_size more than 1.
  4. No, as far as I know, but I'll check it (as an AQA I don't have access to logs)
  5. It happens on all load levels.

@HardNorth
Copy link
Member

@netolyrg I'm sorry, you answers are extremely general, I can't nail any problem with them.

@netolyrg
Copy link
Author

@HardNorth What additional information I can provide? Logs from service api, exact attachments sizing, load stats? Anything missed?

@rplevka
Copy link
Contributor

rplevka commented Oct 14, 2024

logs from the api service would definitely be helpful.
re:

the log is broken into several identical parts (2-8 logs).

Are you trying to say that you expected only 1 such log record to be displayed?
Can you also check the rabbitmq service logs? How's the service health? isn't it being OOMkilled or something?
It appears to me like the workers might process the request but might be killed before they ACK the message?

@HardNorth HardNorth added help wanted and removed bug labels Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy