When trying to install www-client/chromium on a new system, it fails its test phase for me. Of the 108 tests that the build system lists as failing, most look to me like threading-related tests? (The build log was so large that I had to both split and compress it to get it under the 1000KB threshold: even app-arch/lrzip-next with max-compression settings couldn't get the full log small enough to attach as a single file.) [ FAILED ] 108 tests, listed below: [ FAILED ] CheckDeathTest.Basics [ FAILED ] CheckDeathTest.PCheck [ FAILED ] CheckDeathTest.CheckOp [ FAILED ] CheckDeathTest.CheckOpStrings [ FAILED ] CheckDeathTest.CheckOpPointers [ FAILED ] CheckDeathTest.OstreamVsToString [ FAILED ] CheckDeathTest.NotReached [ FAILED ] CheckDeathTest.CheckFailuresAreNoreturn [ FAILED ] CheckDeathTest.DumpWillBeCheck [ FAILED ] CheckDeathTest.DumpWillBeNotReachedNoreturn [ FAILED ] CheckDeathTest.CheckDerefOfNullPointer [ FAILED ] CheckDeathTest.CheckDerefOfConstNullPointer [ FAILED ] CheckDeathTest.CheckNotFatalUntil [ FAILED ] CheckDeathTest.CheckOpNotFatalUntil [ FAILED ] CheckDeathTest.NotReachedNotFatalUntil [ FAILED ] CheckDeathTest.CorrectSystemErrorUsed [ FAILED ] EnumSetDeathTest.CrashesOnOutOfRange [ FAILED ] EnumSetDeathTest.EnumWithNegatives [ FAILED ] EnumSetDeathTest.EnumWithOnlyNegatives [ FAILED ] EnumSetDeathTest.VariadicConstructorCrashesOnOutOfRange [ FAILED ] EnumSetDeathTest.FromRangeCrashesOnBadInputs [ FAILED ] EnumSetDeathTest.PutCrashesOnOutOfRange [ FAILED ] EnumSetDeathTest.PutRangeCrashesOnBadInputs [ FAILED ] LinkedListDeathTest.ChecksOnInsertBeforeWhenInList [ FAILED ] LinkedListDeathTest.ChecksOnInsertAfterWhenInList [ FAILED ] BindDeathTest.NullCallback [ FAILED ] BindDeathTest.NullCallbackWithoutBoundArgs [ FAILED ] ProtectedMemoryDeathTest.FailsIfDefinedOutsideOfProtectMemoryRegion [ FAILED ] SafeRefDeathTest.ArrowOperatorCrashIfBadPointer [ FAILED ] SafeRefDeathTest.StarOperatorCrashIfBadPointer [ FAILED ] StructuredSharedMemoryDeathTest.DuplicateRegion [ FAILED ] OptionalRefDeathTest.ArrowOnEmpty [ FAILED ] OptionalRefDeathTest.StarOnEmpty [ FAILED ] OptionalRefDeathTest.ValueOnEmpty [ FAILED ] RawRefDeathTest.CopyConstructAfterMove [ FAILED ] RawRefDeathTest.MoveConstructAfterMove [ FAILED ] RawRefDeathTest.CopyAssignAfterMove [ FAILED ] RawRefDeathTest.MoveAssignAfterMove [ FAILED ] RawRefDeathTest.CopyConstructAfterMoveUpCast [ FAILED ] RawRefDeathTest.MoveConstructAfterMoveUpCast [ FAILED ] RawRefDeathTest.FromPtrWithNullptr [ FAILED ] RawRefDeathTest.CopyAssignAfterMoveUpCast [ FAILED ] RawRefDeathTest.MoveAssignAfterMoveUpCast [ FAILED ] RawRefDeathTest.DerefAfterMove [ FAILED ] RawRefDeathTest.ArrowAfterMove [ FAILED ] RawRefDeathTest.SwapAfterMove [ FAILED ] RawRefDeathTest.EqualsAfterMove [ FAILED ] RawRefDeathTest.NotEqualsAfterMove [ FAILED ] RawRefDeathTest.LessThanAfterMove [ FAILED ] RawRefDeathTest.GreaterThanAfterMove [ FAILED ] RawRefDeathTest.LessThanOrEqualAfterMove [ FAILED ] RawRefDeathTest.GreaterThanOrEqualAfterMove [ FAILED ] CheckedContiguousIteratorDeathTest.OutOfBounds [ FAILED ] HeapArrayDeathTest.TakeFirstWithOverSize [ FAILED ] CallbackDeathTest.RunNullCallbackChecks [ FAILED ] WeakPtrDeathTest.ArrowOperatorChecksOnBadDereference [ FAILED ] WeakPtrDeathTest.StarOperatorChecksOnBadDereference [ FAILED ] ObserverListThreadSafeDeathTest.CrossThreadRemovalRestricted [ FAILED ] TestFutureDeathTest.GetShouldCheckIfTimeoutHappens [ FAILED ] TestFutureDeathTest.TakeShouldCheckIfTimeoutHappens [ FAILED ] TestFutureWithoutTaskEnvironmentDeathTest.WaitShouldDcheckWithoutTaskEnvironment [ FAILED ] AlternateTestParams/PartitionAllocDeathTest.CheckTriggered/0, where GetParam() = 2-byte object <00-00> [ FAILED ] AlternateTestParams/PartitionAllocDeathTest.CheckTriggered/1, where GetParam() = 2-byte object <01-00> [ FAILED ] AlternateTestParams/PartitionAllocDeathTest.CheckTriggered/2, where GetParam() = 2-byte object <00-01> [ FAILED ] AlternateTestParams/PartitionAllocDeathTest.CheckTriggered/3, where GetParam() = 2-byte object <01-01> [ FAILED ] BarrierCallbackTest.ErrorToCallCallbackWithZeroCallbacks [ FAILED ] BarrierClosureTest.ChecksIfCalledForZeroClosures [ FAILED ] CallbackHelpersTest.SplitOnceCallback_FirstCallback [ FAILED ] CallbackHelpersTest.SplitOnceCallback_SecondCallback [ FAILED ] CallbackHelpersTest.SplitSplitOnceCallback_FirstSplit [ FAILED ] CallbackHelpersTest.SplitSplitOnceCallback_SecondSplit [ FAILED ] SafeRefTest.InvalidAfterMoveConstruction [ FAILED ] SafeRefTest.InvalidAfterMoveAssignment [ FAILED ] SafeRefTest.InvalidAfterMoveConversionConstruction [ FAILED ] SafeRefTest.InvalidAfterMoveConversionAssignment [ FAILED ] SupportsUserDataTest.ReentrantSetUserDataDuringRemoval [ FAILED ] TimeBase.AddSubInfinities [ FAILED ] LibcppHardeningTest.Assertions [ FAILED ] Base64Test.Overflow [ FAILED ] IDMapTest.RemovedValueHandling [ FAILED ] SpanTest.Indexing [ FAILED ] SpanTest.CopyFrom [ FAILED ] SpanTest.CopyPrefixFrom [ FAILED ] SpanTest.SplitAt [ FAILED ] SpanTest.TakeFirst [ FAILED ] SpanTest.TakeFirstElem [ FAILED ] PlatformSharedMemoryRegionTest.CreateReadOnlyRegionDeathTest [ FAILED ] PlatformSharedMemoryRegionTest.DuplicateWritableRegionDeathTest [ FAILED ] PlatformSharedMemoryRegionTest.UnsafeRegionConvertToReadOnlyDeathTest [ FAILED ] PlatformSharedMemoryRegionTest.ReadOnlyRegionConvertToReadOnlyDeathTest [ FAILED ] PlatformSharedMemoryRegionTest.ReadOnlyRegionConvertToUnsafeDeathTest [ FAILED ] PlatformSharedMemoryRegionTest.UnsafeRegionConvertToUnsafeDeathTest [ FAILED ] RefCountedOverflowTest.NonThreadSafeStartFromZero [ FAILED ] RefCountedOverflowTest.NonThreadSafeStartFromOne [ FAILED ] RefCountedOverflowTest.ThreadSafeStartFromZero [ FAILED ] RefCountedOverflowTest.ThreadSafeStartFromOne [ FAILED ] PersistentMemoryAllocatorTest.DelayedAllocationTest [ FAILED ] CheckedObserverListTest.CheckedObserver [ FAILED ] CheckedObserverListTest.MultiObserver [ FAILED ] SequencedTaskRunnerCurrentDefaultHandleTest.OverrideWithNull [ FAILED ] SingleThreadTaskRunnerCurrentDefaultHandleTest.OverrideWithNull [ FAILED ] TaskEnvironmentTest.ParallelExecutionFenceNonMainThreadDeath [ FAILED ] TokenType.TokenFromNullUnguessableToken [ FAILED ] ValuesTest.ListFrontWhenEmpty [ FAILED ] ValuesTest.ListBackWhenEmpty [ FAILED ] BackupRefPtrTest.Advance [ FAILED ] BackupRefPtrTest.AdvanceAcrossPools [ FAILED ] BackupRefPtrTest.IndexOperator 108 FAILED TESTS
Created attachment 920193 [details] www-client:chromium-133.0.6943.126:20250303-190356.log.1.lz
*** Bug 950571 has been marked as a duplicate of this bug. ***
Created attachment 920194 [details] www-client:chromium-133.0.6943.126:20250303-190356.log.2.lz
Created attachment 920195 [details] emerge-info.txt
This is unusual. I see a number of tests that report that the exit code was "correct" but they couldn't match "Check failed" in the output as expected. There are other tests that just seem to have failed. We run the tests for every Chromium release that ends up in ::gentoo - I've never seen this before. Typically we see odd memory allocation failures that just work if the tests are re-run. If you still have the directory around, you could try running `ebuild chromium-133.0.6943.126 test` as root from `/var/db/repos/gentoo/www-client/chromium`, I'm interested if the same tests fail consistently. Otherwise, does it work if you run it again, perhaps with less threads? And are there any `oomkiller` messages in `dmesg` after running the test suite and seeing these failures?
Running "ebuild /usr/portage/www-client/chromium/chromium-133.0.6943.126.ebuild test" on the same work-dir again results in "108 FAILED TESTS". (Since submitting this bug in the first place I also tried versions 133.0.6943.141 and 134.0.6998.35, both of which also had "108 FAILED TESTS".) No "oomkiller" messages in dmesg, but I do see a lot of lines like [2888266.152684] traps: base_unittests[6227] trap int3 ip:564f66386be1 sp:7fffca0fde90 error:0 in base_unittests[564f64f39000+1713000] And near but not quite at the bottom one instance of [2888304.730095] base_unittests[10110]: segfault at 0 ip 000055d51de247ad sp 00007ffdd2440520 error 6 in base_unittests[55d51d4a4000+1713000] likely on CPU 6 (core 12, socket 0) [2888304.730117] Code: d9 00 48 85 c0 74 e6 48 89 c7 e8 ee 09 d9 00 80 7d ef 00 79 09 48 8b 7d d8 e8 7f 23 ae 00 bf 0b 00 00 00 31 f6 e8 13 0d d9 00 <c7> 04 25 00 00 00 00 ad de 00 00 b8 01 00 00 00 48 83 c4 20 5b 41 I then reran the test phase with "MAKEOPTS=-j5", and again got "108 FAILED TESTS".
