Flaky test in B2B module

[hostep]

Preconditions and environment

• Magento 2.4-develop branch

Steps to reproduce

Run integration test for Magento\Company\LoggingTest around 58/59 seconds after the minute. (this is only guessing here, I just ran into this accidentally)

Expected result

Test never fails

Actual result

Test is flaky and seems to depend on 2 different minutes in timestamps:

PHPUnit 9.5.20 �[44m#StandWith�[0m�[43mUkraine�[0m

Warning:       Using a custom test suite loader is deprecated

..........................................F....II....             53 / 53 (100%)

Time: 05:29.716, Memory: 623.00 MB

There was 1 failure:

1) Magento\Company\LoggingTest::testEditCompanyActionLogging
Failed asserting that '2023-02-16 18:26:59' contains "2023-02-16 18:27".

/var/www/html/dev/tests/integration/testsuite/Magento/Company/LoggingTest.php:301
/var/www/html/dev/tests/integration/testsuite/Magento/Company/LoggingTest.php:88

FAILURES!
Tests: 53, Assertions: 134, Failures: 1, Incomplete: 2.

=== Memory Usage System Stats ===
Memory usage (OS):	787.79M (127.27% of 619.00M reported by PHP)
Estimated memory leak:	168.79M (21.43% of used memory)

See https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/36878/eef3786f3239a5598253a3f3f349ee87/Integration/console-error-logs.html

Additional information

Ran into this while working on #36878

Release note

Not important to include in release notes

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @hostep. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Delta. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Delta]

Hi @hostep ,

Thanks for reporting and collaboration.

Verified the issue in Magento 2.4 dev b2b instance and the issue is not reproducible.

Steps to reproduce:

1.Run integration test for Magento\Company\LoggingTest
2.Verify the result

Please check and let us know if it is reproducible at your end

[hostep]

It might depend on the exact second you run the test, it it's close to the 59th or 60th second in a minute.

But anyways, this is an old report, no clue if this still happens occasionally in the github automated test runs, but it did happen when I reported it over a year ago.

But let's close this issue then, if we accidentally see it happening again, we can re-open it again.