Closed
Bug 1528316
Opened 6 years ago
Closed 6 years ago
[tc-index] api_test.js setup fails
Categories
(Taskcluster :: Services, defect)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1533937
People
(Reporter: dustin, Assigned: dustin)
Details
1) api_test.js (real)
"before each" hook: cleanup for "list top-level namespaces with continuation":
Error: Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/taskcluster/services/index/test/api_test.js)
Comment 1•6 years ago
|
||
I would like to work on this bug !some pointers to start would be appreciated
Assignee | ||
Comment 2•6 years ago
|
||
You are welcome to work on this bug. However, the information available is what you see above: this test occasionally fails with a timeout, with no further information on why. This is called "intermittent" or "flaky", and can be really tricky to fix. The process to fix is this:
- Find a way to reproduce the bug more frequently. Sometimes this just involves running the failing test repeatedly (e.g., if it fails once in 100 runs, then a few hundred runs will reproduce)
- Try to add some extra logging that will indicate what's going wrong when it fails. But adding too much logging will change the timing and make cause failures to be much less frequent.
- Modify the test, or (less commonly) the code being tested, to fix the issue.
You're welcome to get started, but I can't provide much guidance apart from that.
Assignee | ||
Comment 3•6 years ago
|
||
Also seeing
index_test.js (real)
✓ Run task and test indexing (482ms)
2) "before each" hook: cleanup for "Run task with a .extra and test indexing"
references_test.js
✓ references validate (148ms)
21 passing (6s)
2 failing
1) api_test.js (real)
"before each" hook: cleanup for "find (non-existing)":
ResourceNotFoundError: The specified resource does not exist.
RequestId:64f38d9a-5002-0031-3f10-d83d52000000
Time:2019-03-11T13:46:39.0698056Z
at /taskcluster/node_modules/fast-azure-storage/lib/table.js:401:27
at tryCallOne (/taskcluster/node_modules/promise/lib/core.js:37:12)
at /taskcluster/node_modules/promise/lib/core.js:123:15
at flush (/taskcluster/node_modules/asap/raw.js:50:29)
at process._tickCallback (internal/process/next_tick.js:61:11)
2) index_test.js (real)
"before each" hook: cleanup for "Run task with a .extra and test indexing":
ResourceNotFoundError: The specified resource does not exist.
RequestId:5915b7f1-7002-008c-1a10-d82bde000000
Time:2019-03-11T13:46:41.4901574Z
at /taskcluster/node_modules/fast-azure-storage/lib/table.js:401:27
at tryCallOne (/taskcluster/node_modules/promise/lib/core.js:37:12)
at /taskcluster/node_modules/promise/lib/core.js:123:15
at flush (/taskcluster/node_modules/asap/raw.js:50:29)
at process._tickCallback (internal/process/next_tick.js:61:11)
this seems more common when lots of tests run in parallel..
Assignee | ||
Comment 4•6 years ago
|
||
1) api_test.js (real)
listing things
list top-level namespaces with continuation:
AssertionError [ERR_ASSERTION]: 6 == 4
+ expected - actual
-6
+4
at Context.<anonymous> (test/api_test.js:123:14)
at process._tickCallback (internal/process/next_tick.js:68:7)
2) api_test.js (real)
"before each" hook: cleanup for "list top-level namespaces (without auth)":
ResourceNotFoundError: The specified resource does not exist.
RequestId:fd70587f-1002-00f1-5610-d8b716000000
Time:2019-03-11T13:46:41.4788250Z
at /taskcluster/node_modules/fast-azure-storage/lib/table.js:401:27
at tryCallOne (/taskcluster/node_modules/promise/lib/core.js:37:12)
at /taskcluster/node_modules/promise/lib/core.js:123:15
at flush (/taskcluster/node_modules/asap/raw.js:50:29)
at process._tickCallback (internal/process/next_tick.js:61:11)
Assignee | ||
Comment 5•6 years ago
|
||
Ah, https://github.com/taskcluster/taskcluster/pull/376/files#diff-077479985c386bbda30c095b626ad771 shows that the "unique table name" was commented out and made constant.
So that PR will probably fix this bug as well!
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•