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

[BUG]: GitHub CI Checks are failing due to timeout #5140

Open
MohitGupta121 opened this issue Aug 22, 2023 · 0 comments
Open

[BUG]: GitHub CI Checks are failing due to timeout #5140

MohitGupta121 opened this issue Aug 22, 2023 · 0 comments
Labels
bug End user-perceivable behaviors which are not desirable. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet.

Comments

@MohitGupta121
Copy link
Member

MohitGupta121 commented Aug 22, 2023

Describe the bug

Mostly Bazel tests (Robolectric) are failing in GitHub PR CI checks.

Here is the full Raw log of checks.

These are some sample logs from failing checks:

"Thread-95" Id=881 TIMED_WAITING
	at java.base@9.0.7.1/java.lang.Thread.sleep(Native Method)
	at android.net.TetheringManager.lambda$startPollingForConnector$1(TetheringManager.java:286)
	at android.net.TetheringManager$$Lambda$224/288120411.run(Unknown Source)
	at java.base@9.0.7.1/java.lang.Thread.run(Thread.java:844)

"pool-569-thread-4" Id=879 WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@17b0792
	at java.base@9.0.7.1/jdk.internal.misc.Unsafe.park(Native Method)
	-  waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@17b0792
	at java.base@9.0.7.1/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
	at java.base@9.0.7.1/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2062)
	at java.base@9.0.7.1/java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:435)
	at java.base@9.0.7.1/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1092)
	at java.base@9.0.7.1/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
	at java.base@9.0.7.1/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
	at java.base@9.0.7.1/java.lang.Thread.run(Thread.java:844)

This PR is facing this PR: #5131
Also this PR #5139 face same issue but after run-running the test passed.

Steps To Reproduce

N/A

Expected Behavior

Tests should be passed or give specific failure.

Screenshots/Videos

No response

What device/emulator are you using?

No response

Which Android version is your device/emulator running?

No response

Which version of the Oppia Android app are you using?

No response

Additional Context

No response

@MohitGupta121 MohitGupta121 added bug End user-perceivable behaviors which are not desirable. triage needed Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. and removed triage needed labels Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug End user-perceivable behaviors which are not desirable. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet.
Development

No branches or pull requests

1 participant