-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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 pipeline maybe flaky (HistoryRecordManagerTest#deleteSearchHistory) #7553
Comments
Maybe adding a retry like getsentry/sentry-unity#437 can help |
At first I think we should display what kind of error actually happens, because
is not very meaningful. Maybe there's just an await or something missing. |
So the stacktrace does not seem helpfull https://github.com/TeamNewPipe/NewPipe/runs/4617056002?check_suite_focus=true
|
Problem occurred again today: https://github.com/TeamNewPipe/NewPipe/actions/runs/1640905968/attempts/1 |
@XiangRongLin |
We could, but as far as i remember it's just a nicely visualized UI with no additional information compared to the logs. |
And - just for the protocol - it failed again: https://github.com/TeamNewPipe/NewPipe/actions/runs/1674370798/attempts/1 |
You are wrong
@XiangRongLin |
The current way the assertions are written make the error message useless. I opened a PR to replace them with AssertJ |
Uhm I don't think they are useless I think the displaying of the first line of the stacktrace and not the complete on is the problem. Edit: Read |
The current problem is - as mentioned in #7652 (comment) - caused by NewPipe/app/src/androidTest/java/org/schabi/newpipe/local/history/HistoryRecordManagerTest.kt Line 71 in dd9772c
So if we have a look at NewPipe/app/src/androidTest/java/org/schabi/newpipe/local/history/HistoryRecordManagerTest.kt Lines 69 to 72 in dd9772c
and at https://github.com/Stypox/NewPipe/blob/2963cd5c6e167640f790ceafafee9f4312fa0773/app/src/main/java/org/schabi/newpipe/database/history/dao/SearchHistoryDAO.java#L36-L38 it's likely the case that the actual returned data entities[0] is not entries[2] but entries[3] because the creation date is identical.
I think we should simply check if the list @Stypox |
Yes, I noticed while debugging #7597 that there could be problems in the tests, and tried to improve them, but at the end #7597 turned out to be a duplicate of an old issue already fixed by my PR so I stashed my changes. Since I had already written some more tests so I opened a new PR: #7700 |
Checklist
The CI pipeline failed on the android tests. It fixed itself after rerunning it, which could indicate a flaky test.
This Issue should serve as place to collect the logs and discuss the problem if it occurs more often. If it does not occur again this can be closed.
Logs
Log of failed CI job: logs_5027.zip
https://github.com/TeamNewPipe/NewPipe/runs/4571396354?check_suite_focus=true
The text was updated successfully, but these errors were encountered: