action #53858
closedflaky test: 25-cache-service.t
Description
Observation¶
From https://travis-ci.org/okurz/openQA/jobs/554203447#L926
[2019-07-04 12:29:02.52016] [1535] [debug] [Job #36] Finished
# Failed test 'job enqueued'
# at ./t/25-cache-service.t line 533.
# Looks like you failed 1 test of 3.
# Failed test 'Test Minion Sync task'
# at ./t/25-cache-service.t line 541.
Can't call method "execute" on an undefined value at ./t/25-cache-service.t line 534.
Updated by coolo over 5 years ago
- Priority changed from Normal to Low
- Target version set to Ready
Updated by okurz over 5 years ago
- Related to action #54032: flaky test: t/full-stack.t "not ok 44 - Cache tests", subtest: "not ok 17 - test 6 is passed" at /opt/testing_area/openqa/t/lib/OpenQA/Test/FullstackUtils.pm line 120. added
Updated by okurz over 5 years ago
- Related to action #38276: Flaky 'test candidate list' at t/ui/18-tests-details.t added
Updated by okurz over 5 years ago
- Status changed from New to Feedback
- Assignee set to okurz
https://github.com/os-autoinst/openQA/pull/2259 to remove "travis_retry" again after test stabilization – and proper testing in the PR
Updated by okurz over 5 years ago
- Status changed from Feedback to Workable
- Assignee deleted (
okurz)
failed in 2/20 "unit- and integration tests" runs in https://travis-ci.org/os-autoinst/openQA/builds/571252085 so this is still a thing.
Updated by okurz over 5 years ago
- Related to action #55457: flaky test: t/api/11-bugs.t added
Updated by okurz over 5 years ago
- Related to action #37638: Flaky fullstack test: 'Test 3 is scheduled' at t/full-stack.t added
Updated by mkittler over 5 years ago
I have already investigated this ages ago (with no success). This ticket is likely a duplicate.
I guess links to Travis CI jobs are pointless. At least it seems that I get a completely different log when accessing it now.
Updated by okurz about 5 years ago
- Status changed from Workable to Blocked
- Assignee set to kraih
@kraih as you are currently working on cache and also the test, otherwise I would continue with the test
Updated by kraih about 5 years ago
I've been running this test a lot during my refactoring work and have not actually seen the error once. In fact the test seems very stable now. Maybe it has already been fixed?
Updated by okurz about 5 years ago
Well, maybe your tests have covered this. Then I suggest you remove the test from the "unstable" ones and we will see in other PRs if we were wrong :)
Updated by okurz about 5 years ago
- Status changed from Blocked to Feedback
- Assignee changed from kraih to okurz
- Target version changed from Ready to Current Sprint
Updated by okurz about 5 years ago
- Status changed from Feedback to Resolved
- Target version changed from Current Sprint to Done