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

CI Test Failure for MacOS #2251

Closed
lhw-1 opened this issue Mar 30, 2023 · 1 comment
Closed

CI Test Failure for MacOS #2251

lhw-1 opened this issue Mar 30, 2023 · 1 comment

Comments

@lhw-1
Copy link
Contributor

lhw-1 commented Mar 30, 2023

Please confirm that you have searched existing issues in the repo

Yes, I have searched the existing issues

Any related issues?

No response

Tell us about your environment

Ubuntu 20.04

MarkBind version

4.1.0

Describe the bug and the steps to reproduce it

On merging PR #2247 into the master branch, the CI for MacOS initially failed, with this test case resulting in an "Exceeded timeout of 5000 ms for a test" error.

After some investigation into the issue, it seems that the main problem is with the time taken to run each test being too long, and since this particular test took more than 5000 ms to run, the test returned an error.

photo_2023-03-30_17-23-43

However, it should be noted that the CI run for MacOS on the commit before this is as follows:

photo_2023-03-30_17-23-51

And the CI run for MacOS when the CI was run again is as follows:

photo_2023-03-30_17-23-48

The time taken to run the tests in these two cases (before and after this issue occurred) seem to be in the reasonable range. Unfortunately, there does not seem to be another instance of this issue, and it does not seem possible to reliably replicate this issue as of right now, given that the issue disappeared on re-running the CI tests.

We will keep this issue open for (1) documentation, and (2) replicate and possibly resolve this issue if it is encountered again in the future.

Expected behavior

The test should take a reasonable amount of time to run (between 200 - 300 ms) and should not result in a timeout error.

Anything else?

No response

@kaixin-hc
Copy link
Contributor

Understanding that this was not replicated before or after, to keep looking through open issues more manageable, I will close this issue; if it occurs again lets reopen and discuss this issue more.

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

No branches or pull requests

2 participants