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

Tempesta unittests crash #2222

Closed
KonsKo opened this issue Aug 23, 2024 · 1 comment · Fixed by #2236
Closed

Tempesta unittests crash #2222

KonsKo opened this issue Aug 23, 2024 · 1 comment · Fixed by #2236
Assignees
Milestone

Comments

@KonsKo
Copy link
Contributor

KonsKo commented Aug 23, 2024

Scope

HEAD 6a11731

Server: bare metal, SUT, Linux sut 5.10.35.tfw-1d07dc5 #1 SMP Thu Jun 27 15:40:11 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  • Reboot the machine
  • run make clean
  • run make -j
  • run make test

Unit Tests are working endlessly (as by hand, as with our CI). If they are interrupted, Tempesta will not be started until a machine is rebooted.

When Tempesta cannot start after the failed unittests log_tempesta_cannot_start.txt

Dmesg logs for the failed unittests
dmesg-Aug-23-2024.txt

Testing

Unittests

Documentation

If Tempesta FW behavior or configuration is changed, then please update the Wiki. Don't forget about our documentation guidelines.

@krizhanovsky krizhanovsky added this to the 0.9 - LA milestone Aug 26, 2024
@krizhanovsky
Copy link
Contributor

This is about Tempesta FW hang on a baremetal setup, so we need to fix it in Beta, so move to 0.8

@krizhanovsky krizhanovsky modified the milestones: 0.9 - LA, 0.8 - Beta Aug 26, 2024
@krizhanovsky krizhanovsky removed the test label Aug 26, 2024
EvgeniiMekhanik added a commit that referenced this issue Sep 6, 2024
There is no crash in unittests described in #2222
- everything is ok, but test works too long (about 30
minutes), because of a lot of cpu in system. Fix test
- now if count of cpu is greater then 32 count of
workers == count of cpu not count of cpu * 10.

Closes #2222
EvgeniiMekhanik added a commit that referenced this issue Sep 13, 2024
There is no crash in unittests described in #2222
- everything is ok, but test works too long (about 30
minutes), because of a lot of cpu in system. Fix test
- now if count of cpu is greater then 32 count of
workers == count of cpu not count of cpu * 10.

Closes #2222
EvgeniiMekhanik added a commit that referenced this issue Oct 15, 2024
There is no crash in unittests described in #2222
- everything is ok, but test works too long (about 30
minutes), because of a lot of cpu in system. Fix test
- now if count of cpu is greater then 32 count of
workers == count of cpu not count of cpu * 10.

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

Successfully merging a pull request may close this issue.

3 participants