Project

General

Profile

Actions

Emulator Issues #12421

closed

Unit test failure on generic builds

Added by mystro256 about 3 years ago. Updated over 1 year ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
Yes
Regression start:
Fixed in:
5.0-16553

Description

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

I tested 7250d6e4e091f4b5b4f2289c2c732349b69a2e8a (a.k.a. used for 5.0-13603)

What's the problem? Describe what went wrong.

PageFaultTest unit test seems to fail with a segfault if ENABLE_GENERIC=ON via cmake. I'm not sure of the purpose of this test, so it's unclear if it's expected to fail in a generic build, or if this is a bug.
If this is expected to fail, I would think this test should be disabled for generic builds.

Please let me know if there's some way of providing any logs, but this is what I get when testing a generic build on x86_64:

  Start  1: BitFieldTest

1/24 Test #1: BitFieldTest ..................... Passed 0.00 sec
Start 2: BitSetTest
2/24 Test #2: BitSetTest ....................... Passed 0.00 sec
Start 3: BitUtilsTest
3/24 Test #3: BitUtilsTest ..................... Passed 0.00 sec
Start 4: BlockingLoopTest
4/24 Test #4: BlockingLoopTest ................. Passed 0.30 sec
Start 5: BusyLoopTest
5/24 Test #5: BusyLoopTest ..................... Passed 0.11 sec
Start 6: CommonFuncsTest
6/24 Test #6: CommonFuncsTest .................. Passed 0.16 sec
Start 7: CryptoEcTest
7/24 Test #7: CryptoEcTest ..................... Passed 0.46 sec
Start 8: EventTest
8/24 Test #8: EventTest ........................ Passed 1.04 sec
Start 9: FixedSizeQueueTest
9/24 Test #9: FixedSizeQueueTest ............... Passed 0.00 sec
Start 10: FlagTest
10/24 Test #10: FlagTest ......................... Passed 0.21 sec
Start 11: FloatUtilsTest
11/24 Test #11: FloatUtilsTest ................... Passed 0.10 sec
Start 12: MathUtilTest
12/24 Test #12: MathUtilTest ..................... Passed 0.00 sec
Start 13: NandPathsTest
13/24 Test #13: NandPathsTest .................... Passed 0.00 sec
Start 14: SPSCQueueTest
14/24 Test #14: SPSCQueueTest .................... Passed 0.02 sec
Start 15: StringUtilTest
15/24 Test #15: StringUtilTest ................... Passed 0.00 sec
Start 16: SwapTest
16/24 Test #16: SwapTest ......................... Passed 0.00 sec
Start 17: MMIOTest
17/24 Test #17: MMIOTest ......................... Passed 0.08 sec
Start 18: PageFaultTest
18/24 Test #18: PageFaultTest ....................***Exception: SegFault 0.14 sec
Start 19: CoreTimingTest
19/24 Test #19: CoreTimingTest ................... Passed 0.05 sec
Start 20: DSPAcceleratorTest
20/24 Test #20: DSPAcceleratorTest ............... Passed 0.00 sec
Start 21: DSPAssemblyTest
21/24 Test #21: DSPAssemblyTest .................. Passed 0.01 sec
Start 22: ESFormatsTest
22/24 Test #22: ESFormatsTest .................... Passed 0.00 sec
Start 23: FileSystemTest
23/24 Test #23: FileSystemTest ................... Passed 0.07 sec
Start 24: VertexLoaderTest
24/24 Test #24: VertexLoaderTest ................. Passed 10.63 sec
96% tests passed, 1 tests failed out of 24
Total Test time (real) = 13.41 sec
The following tests FAILED:
18 - PageFaultTest (SEGFAULT)
Errors while running CTest

What steps will reproduce the problem?

Add -DENABLE_GENERIC=ON to cmake when building, then build unit tests and this test will fail. E.g.:

cmake -DENABLE_GENERIC=ON .
cmake --build
cmake --build --target unittests

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

5.0-13603

Is the issue present in the latest stable version?

Yes in the beta, 5.0-13603.

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

Unknown if regression

What are your PC specifications? (CPU, GPU, Operating System, more)

Tested on a ppc64le (ppc 64bit little endian) and an x86_64 machine. I'm not sure how practical this use case is.

Actions #1

Updated by JosJuice about 3 years ago

  • Status changed from New to Accepted
  • Relates to maintainability changed from No to Yes
Actions #3

Updated by JosJuice over 1 year ago

  • Status changed from Accepted to Fixed
  • Fixed in set to 5.0-16553
Actions

Also available in: Atom PDF