Skip to content
This repository has been archived by the owner on Sep 6, 2023. It is now read-only.

Error creating execution #99

Open
GiladLB opened this issue Feb 2, 2021 · 3 comments
Open

Error creating execution #99

GiladLB opened this issue Feb 2, 2021 · 3 comments

Comments

@GiladLB
Copy link

GiladLB commented Feb 2, 2021

Hi, I have a bug when a test fails because it exceeds the timeout:

Timeout - Async callback was not invoked within the 60000 ms timeout specified by jest.setTimeout.Error: Timeout - Async callback was not invoked within the 60000 ms timeout specified by jest.setTimeout.

  at mapper (node_modules/@jest/core/node_modules/jest-jasmine2/build/queueRunner.js:27:45)

✖ Error Creating Execution: Error creating execution:Internal Server Error
{"success":false,"errorMessage":"failed to create execution (run result)"}
TestimApiError: Error creating execution:Internal Server Error
{"success":false,"errorMessage":"failed to create execution (run result)"}
at TestimExecutionsApi.createExecution (/home/gilad/projects/obligo/frontend/test/e2e/node_modules/@testim/root-cause-jest/node_modules/@testim/root-cause-core/lib/testim-services-api/testimExecutionsApi.js:45:19)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at RootCauseExecutionsApi.createExecution (/home/gilad/projects/obligo/frontend/test/e2e/node_modules/@testim/root-cause-jest/node_modules/@testim/root-cause-core/lib/testim-services-api/rootCauseExecutionsApi.js:49:9)
at Object.persist (/home/gilad/projects/obligo/frontend/test/e2e/node_modules/@testim/root-cause-jest/node_modules/@testim/root-cause-core/lib/persist.js:42:34)
at EnhancedDefault.onRunComplete (/home/gilad/projects/obligo/frontend/test/e2e/node_modules/@testim/root-cause-jest/lib/reporter/RunConclusion.js:58:13)
at EnhancedDefault.onRunComplete (/home/gilad/projects/obligo/frontend/test/e2e/node_modules/@testim/root-cause-jest/lib/reporter/default.js:82:9)
at ReporterDispatcher.onRunComplete (/home/gilad/projects/obligo/frontend/test/e2e/node_modules/@jest/core/build/ReporterDispatcher.js:88:9)
at TestScheduler.scheduleTests (/home/gilad/projects/obligo/frontend/test/e2e/node_modules/@jest/core/build/TestScheduler.js:350:5)
at runJest (/home/gilad/projects/obligo/frontend/test/e2e/node_modules/@jest/core/build/runJest.js:376:19) {
  code: 'E_CREATING_EXECUTION_FAILED',
  originalError: Error: 
  at TestimExecutionsApi.createExecution (/home/gilad/projects/obligo/frontend/test/e2e/node_modules/@testim/root-cause-jest/node_modules/@testim/root-cause-core/lib/testim-services-api/testimExecutionsApi.js:45:50)
  at runMicrotasks (<anonymous>)
  at processTicksAndRejections (internal/process/task_queues.js:97:5)
  at RootCauseExecutionsApi.createExecution (/home/gilad/projects/obligo/frontend/test/e2e/node_modules/@testim/root-cause-jest/node_modules/@testim/root-cause-core/lib/testim-services-api/rootCauseExecutionsApi.js:49:9)
  at Object.persist (/home/gilad/projects/obligo/frontend/test/e2e/node_modules/@testim/root-cause-jest/node_modules/@testim/root-cause-core/lib/persist.js:42:34)
  at EnhancedDefault.onRunComplete (/home/gilad/projects/obligo/frontend/test/e2e/node_modules/@testim/root-cause-jest/lib/reporter/RunConclusion.js:58:13)
  at EnhancedDefault.onRunComplete (/home/gilad/projects/obligo/frontend/test/e2e/node_modules/@testim/root-cause-jest/lib/reporter/default.js:82:9)
  at ReporterDispatcher.onRunComplete (/home/gilad/projects/obligo/frontend/test/e2e/node_modules/@jest/core/build/ReporterDispatcher.js:88:9)
  at TestScheduler.scheduleTests (/home/gilad/projects/obligo/frontend/test/e2e/node_modules/@jest/core/build/TestScheduler.js:350:5)
  at runJest (/home/gilad/projects/obligo/frontend/test/e2e/node_modules/@jest/core/build/runJest.js:376:19)
}
@benjamingr
Copy link
Contributor

Hey @GiladLB - I think I see the issue we're taking a look.

@benjamingr
Copy link
Contributor

Can you perhaps upload your .root-cause results.json file to a gist?

The backend is complaining about a foreign key constraint violation (meaning problematic IDs)

@GiladLB
Copy link
Author

GiladLB commented Feb 2, 2021

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

No branches or pull requests

2 participants