Bug 1227462 - Stressapptest (Package): Process Error: Sat::Initialize() failed
Summary: Stressapptest (Package): Process Error: Sat::Initialize() failed
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other (show other bugs)
Version: Current
Hardware: x86-64 Other
: P5 - None : Minor (vote)
Target Milestone: ---
Assignee: Michal Suchanek
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-06 07:05 UTC by Bernhard JoRo
Modified: 2024-07-08 06:40 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard JoRo 2024-07-06 07:05:31 UTC 
Fresh installation of openSUSE Tumbleweed (KDE).
Installed stressapptest package.

stressapptest reports an error at execution.
This happens on all of my systems. I am using openSUSE Tumbleweed for about 2 years and stressapptest never worked. With Fedora on the identical system stressapptest works perfectly fine. I have to use a Fedora live system to test my hardware. 

Error message:

❯ stressapptest
2024/07/04-14:42:44(CEST) Log: Commandline - stressapptest
2024/07/04-14:42:44(CEST) Stats: SAT revision 1.0.11_autoconf, 64 bit binary
2024/07/04-14:42:44(CEST) Log: reproducible @ reproducible on Sun Nov 26 17:19:40 UTC 2023 from open source release
2024/07/04-14:42:44(CEST) Log: 1 nodes, 16 cpus.
2024/07/04-14:42:44(CEST) Process Error: Running DEBUG version of SAT, with significantly reduced coverage.
2024/07/04-14:42:44(CEST) Log: Command line option '-A' bypasses this error.
2024/07/04-14:42:44(CEST) Process Error: Sat::Initialize() failed
2024/07/04-14:42:44(CEST) 
2024/07/04-14:42:44(CEST) Status: FAIL - test encountered procedural errors
2024/07/04-14:42:44(CEST) 
2024/07/04-14:42:44(CEST) Process Error: Fatal issue encountered. See above logs for details.
Comment 1 Michal Suchanek 2024-07-07 15:07:02 UTC 
(In reply to Bernhard JoRo from comment #0)

> 2024/07/04-14:42:44(CEST) Log: Command line option '-A' bypasses this error.

Fedora is using an older version. If you can run theirs this is likely an upstream regression. Please report the issue upstream if you do not like the provided workaround.
Comment 2 Bernhard JoRo 2024-07-08 06:40:11 UTC 
Thank you for your reply.

The identical error occurred with the previous version 1.0.9. 

The provided option -A uses the "degraded mode" and therefore a less thorough hardware testing. 

The versions in Fedora 1.0.9 and Arch (AUR) 1.0.11 work perfectly fine on all of my tested systems. It is no hw compatibility issue. 

Please check if there is something wrong with the build options (debug?). 
Thanks.