postmanlabs / postman-app-support

Postman is an API platform for building and using APIs. Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster.
https://www.postman.com
5.78k stars 837 forks source link

Failed to run performance test #12608

Open thachun opened 5 months ago

thachun commented 5 months ago

Is there an existing issue for this?

Describe the Issue

I am trying to run the performance test on a collection but unfortunately I got an error saying: "Failed to start run Postman encountered an error due to which the run could not be started. Please try again." image

Is there any version working that I could downgrade?

Thanks!

Steps To Reproduce

  1. Just run a performance test on a collection and see a popup error message at the right corner.

Screenshots or Videos

No response

Operating System

Windows

Postman Version

10.22.9

Postman Platform

Postman App

User Account Type

Signed In User

Additional Context?

No response

ilies-t commented 5 months ago

I have the same problem in 10.22.9 version

mateussaggin commented 5 months ago

Same problem here in 10.22.9.

Edit: The problem is happening only if there is folders inside the collection.

nikithaachhini23 commented 5 months ago

Hi @thachun

Could you please provide information on whether you're running performance run on a folder directly (or) on a collection with folders?

Screen recording of the flow would be much appreciated.

atehvg commented 5 months ago

Same thing is happening when I run a folder inside a collection. Running the collection with folders doesn't have issues. Running Version 10.22.9.

Edit: added version number

thachun commented 5 months ago

Hi @thachun

Could you please provide information on whether you're running performance run on a folder directly (or) on a collection with folders?

Screen recording of the flow would be much appreciated.

I did not see any folder in my collection. I just create a new collection again and it works :-). Something wrong with the old collection that honestly, I have no idea.

gintsgints commented 5 months ago
image
nikithaachhini23 commented 5 months ago

@thachun Thank you for providing the screenshot. Running folders inside a collection (or) running a collection as a whole with requests and folders will work. Let me know if you're facing any issues there.

As @atehvg informed running a performance run directly on a folder is an issue which we're currently looking into and will have it fixed in the upcoming release.

habibsc commented 5 months ago

I'm having this same issue if I try to run the Performance test from a Folder inside a Collection. Running the Performance test directly from a Collection, with requests not inside a Folder, worked a expected. Still using Postman 10.22.6 here.

gintsgints commented 5 months ago

For me works whole collection even it has tests within folders.

cpinkerton-kpler commented 5 months ago

Same issue on v10.22 - trying to run a Performance test on a sub-folder of a Collection. Running the Functional test works on the same folder. Running the Performance test on a whole Collections works

nikithaachhini23 commented 3 months ago

Hey @thachun @atehvg Could you try updating the app to the latest version and check? (latest version should be 10.24.0). It works even on 10.23.0

Running performance test directly on folders with in collection should work now.

SavioHolanda commented 3 months ago

Estou na versão v10.24.11 e está ocorrendo o mesmo problema.

Solução que fiz: Criei uma nova coleção e coloquei as requisições para essa nova coleção e com voltou a funcionar.

nikithaachhini23 commented 3 months ago

@SavioHolanda Are you saying that on v10.24.11 running a performance test directly on folders is not working? I verified that it works. Could you please share a recording?

hfcipriano commented 2 months ago

I prefer the old postman... This new one should renamed to bugman

Linghucong1999 commented 1 month ago

image 这个就很操蛋

albaraX commented 1 month ago

I have same problem. An earlier advices doesn't work. Postman v. 11.0.11. Testing collection aren't contain any folder and I create a new collection in current version of Postman. I've tried run testing with 1 VU (2 mins). Anyway got error "Failed to start run".

image 这个就很操蛋

s93rum06 commented 1 month ago
[18176][1715471123192][main][info]["Booting Postman 11.0.12, win32-10.0.19045 on x64"]
[18176][1715471123194][main][info]["EventBus~initialize - Success"]
[18176][1715471123196][main][info]["Proxy configuration has not been setup"]
[18176][1715471123196][main][info]["CloudProxyManager~init - Success"]
[18176][1715471123215][main][info]["performShellDataMigration: Migration has already been done. Bailing out"]
[18176][1715471123216][main][info]["UpdateHandler~init - Success"]
[18176][1715471123218][main][info]["LeaderSelection: Initialized successfully"]
[18176][1715471123218][main][info]["VersionDependencyService: Initialized successfully"]
[18176][1715471123240][main][info]["GPU detected VID 4318 DID 7944 ACTIVE false"]
[18176][1715471123240][main][info]["GPU detected VID 5140 DID 140 ACTIVE false"]
[18176][1715471123243][main][info]["newAccountRegionPreferenceService~getPreferenceWithFallback - Preference not found in storage."]
[18176][1715471123244][main][info]["newAccountRegionPreferenceService~getToggleMenuTemplate - Using preference:","useUSRegion"]
[18176][1715471123256][main][info]["shellController~init: Success"]
[18176][1715471123267][main][info]["shellMeta~init: Success"]
[18176][1715471123267][main][info]["partitionMigrationService: State of V7 partition:"]
[18176][1715471123268][main][info]["partitionMigrationService: V7 partitions",[]]
[18176][1715471123268][main][info]["partitionMigrationService~rectifyNamespaceOfScratchPadPartition: There is no partition with scratchpad namespace"]
[18176][1715471123268][main][info]["partitionMigrationService~rectifyNamespaceOfScratchPadPartition: There is no transit partition which could have been used for scratchpad"]
[18176][1715471123268][main][info]["partitionMigrationService~init: Success"]
[18176][1715471123283][main][info]["partitionMigrationService~runV8PartitionsIntegrity: Two way migration~ removing the following partitions from v8",[]]
[18176][1715471123288][main][info]["userPartitionService~getRecentV8UserPartition: recent v8 user context partition ","8120dbe8-f271-4a9d-9519-8394b751ab87"]
[18176][1715471123288][main][info]["userPartitionService~_rectifyTheActivePartitionOfApplication: Setting the active partition to ","8120dbe8-f271-4a9d-9519-8394b751ab87"]
[18176][1715471123296][main][info]["userPartitionService~init: Success"]
[18176][1715471123311][main][info]["userPartitionService: State of v8 partition system:"]
[18176][1715471123314][main][info]["shell~init~getPartitionToLoad: loading active partition"]
[18176][1715471123316][main][info]["userPartitionService: List of partitions:",[{"partitionId":"8120dbe8-f271-4a9d-9519-8394b751ab87","namespace":"users","userId":"34858560","teamId":"0","lastUpdated":"2024-05-11T23:35:52.352Z"},{"partitionId":"3162e21b-a368-44b2-a4cb-8e30a5eef382","namespace":"scratchPad","userId":0,"teamId":0,"isDirty":false}]]
[18176][1715471123316][main][info]["userPartitionService: users global meta:",{}]
[18176][1715471123320][main][info]["Main:windowManager~newRequesterWindow: Fetch and update runtime config: us"]
[18176][1715471124618][main][info]["RuntimeIPCAgent~started: Success"]
[18176][1715471125740][main][info]["Main~getRemoteInitPath:: "]
[18176][1715471126240][main][info]["UpdateHandler~app-update-events - Received event",{"name":"checkForElectronVersionUpdated","namespace":"appUpdate"}]
[18176][1715471126255][main][info]["windowManager: First requester booted successfully."]
[18176][1715471126255][main][info]["windowManager~restoreWindows: Restoring requester windows"]
[18176][1715471126255][main][info]["Main~AppEvents - Received booted event for process requester.Version 11.0.12 UI Version: 11.0.12-ui-240509-0541 Desktop Platform Version: 11.0.12"]
[18176][1715471126361][main][info]["Main~getRemoteInitPath:: "]
[18176][1715471126595][main][info]["Main~getPlatformLaunchPerfMetrics"]
[18176][1715471127716][main][info]["Main - model-events~user - (user, bootstrapUser) received"]
[18176][1715471127716][main][info]["model-events~user - bootstrapUser received"]
[18176][1715471127730][main][info]["INTERCEPTOR CONNECTIVITY: Attempting to start websocket server on port 15611"]
[18176][1715471162394][main][info]["ExecutionProcess ~ First boot"]
[18176][1715471162805][main][info]["ExecutionSystem execution ~ ipc connection successfully established"]
[18176][1715471162805][main][info]["[ExecutionProcessLauncher] Spawned the execution process, pid: ",12984]
[18176][1715471162817][main][info]["ExecutionSystem execution ~ ipc connection successfully established"]
[18176][1715471165490][main][error]["ExecutionProcess ~ Boot error",{"name":"Error","message":"Unhandled error. ({\n  subsystem: 'system.startup',\n  error: {\n    message: \"Cannot destructure property 'memory' of '(intermediate value)' as it is undefined.\",\n    stack: \"TypeError: Cannot destructure property 'memory' of '(intermediate value)' as it is undefined.\\n\" +\n      '    at ExecutionEngine._getNumberOfPossibleGroups (C:\\\\Users\\\\jerry\\\\AppData\\\\Local\\\\Postman\\\\app-11.0.12\\\\resources\\\\app.asar\\\\services\\\\automation-testing\\\\ScenarioManager\\\\ExecutionEngine\\\\Engine.js:127:13)\\n' +\n      '    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)\\n' +\n      '    at async ExecutionEngine.setup (C:\\\\Users\\\\jerry\\\\AppData\\\\Local\\\\Postman\\\\app-11.0.12\\\\resources\\\\app.asar\\\\services\\\\automation-testing\\\\ScenarioManager\\\\ExecutionEngine\\\\Engine.js:154:49)\\n' +\n      '    at async onStartup (C:\\\\Users\\\\jerry\\\\AppData\\\\Local\\\\Postman\\\\app-11.0.12\\\\resources\\\\app.asar\\\\services\\\\automation-testing\\\\ScenarioManager\\\\index.js:38:5)\\n' +\n      '    at async startup (C:\\\\Users\\\\jerry\\\\AppData\\\\Local\\\\Postman\\\\app-11.0.12\\\\resources\\\\app.asar\\\\services\\\\automation-testing\\\\lib\\\\system\\\\_life-cycle.js:30:5)\\n' +\n      '    at async C:\\\\Users\\\\jerry\\\\AppData\\\\Local\\\\Postman\\\\app-11.0.12\\\\resources\\\\app.asar\\\\services\\\\automation-testing\\\\lib\\\\system\\\\_life-cycle.js:219:7\\n' +\n      '    at async C:\\\\Users\\\\jerry\\\\AppData\\\\Local\\\\Postman\\\\app-11.0.12\\\\resources\\\\app.asar\\\\preload\\\\desktop\\\\node-process\\\\IPC.js:1:2486'\n  },\n  source: 'ExecutionSystem:LifeCycle',\n  message: 'Error in starting up the ExecutionSystem',\n  severity: undefined,\n  timestamp: '2024-05-11T23:46:05.497Z'\n})","stack":"Error [ERR_UNHANDLED_ERROR]: Unhandled error. ({\n  subsystem: 'system.startup',\n  error: {\n    message: \"Cannot destructure property 'memory' of '(intermediate value)' as it is undefined.\",\n    stack: \"TypeError: Cannot destructure property 'memory' of '(intermediate value)' as it is undefined.\\n\" +\n      '    at ExecutionEngine._getNumberOfPossibleGroups (C:\\\\Users\\\\jerry\\\\AppData\\\\Local\\\\Postman\\\\app-11.0.12\\\\resources\\\\app.asar\\\\services\\\\automation-testing\\\\ScenarioManager\\\\ExecutionEngine\\\\Engine.js:127:13)\\n' +\n      '    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)\\n' +\n      '    at async ExecutionEngine.setup (C:\\\\Users\\\\jerry\\\\AppData\\\\Local\\\\Postman\\\\app-11.0.12\\\\resources\\\\app.asar\\\\services\\\\automation-testing\\\\ScenarioManager\\\\ExecutionEngine\\\\Engine.js:154:49)\\n' +\n      '    at async onStartup (C:\\\\Users\\\\jerry\\\\AppData\\\\Local\\\\Postman\\\\app-11.0.12\\\\resources\\\\app.asar\\\\services\\\\automation-testing\\\\ScenarioManager\\\\index.js:38:5)\\n' +\n      '    at async startup (C:\\\\Users\\\\jerry\\\\AppData\\\\Local\\\\Postman\\\\app-11.0.12\\\\resources\\\\app.asar\\\\services\\\\automation-testing\\\\lib\\\\system\\\\_life-cycle.js:30:5)\\n' +\n      '    at async C:\\\\Users\\\\jerry\\\\AppData\\\\Local\\\\Postman\\\\app-11.0.12\\\\resources\\\\app.asar\\\\services\\\\automation-testing\\\\lib\\\\system\\\\_life-cycle.js:219:7\\n' +\n      '    at async C:\\\\Users\\\\jerry\\\\AppData\\\\Local\\\\Postman\\\\app-11.0.12\\\\resources\\\\app.asar\\\\preload\\\\desktop\\\\node-process\\\\IPC.js:1:2486'\n  },\n  source: 'ExecutionSystem:LifeCycle',\n  message: 'Error in starting up the ExecutionSystem',\n  severity: undefined,\n  timestamp: '2024-05-11T23:46:05.497Z'\n})\n    at new NodeError (node:internal/errors:372:5)\n    at EventEmitter.emit (node:events:516:17)\n    at sendEvent (C:\\Users\\jerry\\AppData\\Local\\Postman\\app-11.0.12\\resources\\app.asar\\services\\automation-testing\\lib\\communication.js:19:19)\n    at broadcastError (C:\\Users\\jerry\\AppData\\Local\\Postman\\app-11.0.12\\resources\\app.asar\\services\\automation-testing\\lib\\communication.js:164:3)\n    at C:\\Users\\jerry\\AppData\\Local\\Postman\\app-11.0.12\\resources\\app.asar\\services\\automation-testing\\lib\\system\\_life-cycle.js:221:7\n    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)\n    at async C:\\Users\\jerry\\AppData\\Local\\Postman\\app-11.0.12\\resources\\app.asar\\preload\\desktop\\node-process\\IPC.js:1:2486"}]
[18176][1715471183990][main][info]["ExecutionProcess ~ Already booted"]
[18176][1715471202169][main][info]["ExecutionProcess ~ Already booted"]
[18176][1715471578625][main][info]["WindowManager~closeHandler - Closed Window (id: 1 )"]
[18176][1715471578649][main][info]["Quitting app"]
[18176][1715471578649][main][info]["ExecutionProcessLauncher ~ No actively running power-save-blocker"]
[18176][1715471578653][main][info]["ExecutionSystem execution ~ ipc connection closed."]
Linghucong1999 commented 1 month ago

I have same problem. An earlier advices doesn't work. Postman v. 11.0.11. Testing collection aren't contain any folder and I create a new collection in current version of Postman. I've tried run testing with 1 VU (2 mins). Anyway got error "Failed to start run".

image 这个就很操蛋

The same version worked before, but suddenly it stopped working for a while. I opened the console and no error was reported.

albaraX commented 1 month ago

Maybe if you use all your runner's limits (25/25) then you can't start a performance test? I have 40/25 runs

Linghucong1999 commented 1 month ago

Maybe if you use all your runner's limits (25/25) then you can't start a performance test? I have 40/25 runs

i use 1/1 run,is still the case

arr19422 commented 1 month ago

Same here, Postman just does not initiate a performing test, wichever the VU, Duration or Load profile. It just does not work.

nikithaachhini23 commented 1 month ago

Apologies for the delay in responding back. We're looking into this issue.

Are all of you running the performance run on windows machine using the latest version?

s93rum06 commented 1 month ago

3 days ago, Yes. not today v11.1.

[18176][1715471123192][main][info]["Booting Postman 11.0.12, win32-10.0.19045 on x64"]
[18176][1715471123194][main][info]["EventBus~initialize - Success"]

Apologies for the delay in responding back. We're looking into this issue.

Are all of you running the performance run on windows machine using the latest version?

Linghucong1999 commented 1 month ago

Apologies for the delay in responding back. We're looking into this issue.

Are all of you running the performance run on windows machine using the latest version?

yap image

deibyd commented 1 month ago

I am experiencing exactly the same issue. When I try to perform a load test, it returns an error.

image

image

Please help me to be able to perform these load tests. Could it be a subscription issue where I need to pay?

nikithaachhini23 commented 1 month ago

@deibyd Its not a subscription issue. Seems like a windows specific issue which the team will be looking into. We'll ensure to fix this issue soon. Could you please provide the logs if possible?

nikithaachhini23 commented 1 month ago

@s93rum06 Could you please zip the entire logs folder and send it?

deibyd commented 1 month ago

@deibyd Its not a subscription issue. Seems like a windows specific issue which the team will be looking into. We'll ensure to fix this issue soon. Could you please provide the logs if possible? postman-logs.zip

tagtag21 commented 1 month ago

@deibyd hi . I have a similar problem, did you manage to figure it out?

VlogP commented 1 month ago

@deibyd Hi, same issue.

deibyd commented 1 month ago

No, I haven't fixed it yet; it still occurs. I have passed the log to @nikithaachhini23. Maybe he can tell us the status and what he has discovered. Thank you very much in advance, nikithaachhini23. We remain attentive to anything else you need. I think it would be a good idea for others to also attach their logs.

albaraX commented 1 month ago

Can't attach a hole logs for some reason, but here is a part of them:

[3376][1714656247782][execution-node-process][error][["Error while getting available memory",{"code":1,"killed":false,"signal":null,"cmd":"systeminfo | find \"Available Physical Memory\""}]]
[3376][1714656247783][execution-node-process][error]["Failed to get platform specs",{"code":1,"killed":false,"signal":null,"cmd":"systeminfo | find \"Available Physical Memory\"","name":"Error","message":"Command failed: systeminfo | find \"Available Physical Memory\"\n","stack":"Error: Command failed: systeminfo | find \"Available Physical Memory\"\n\n at ChildProcess.exithandler (node:child_process:407:12)\n at ChildProcess.emit (node:events:527:28)\n at maybeClose (node:internal/child_process:1092:16)\n at ChildProcess._handle.onexit (node:internal/child_process:302:5)"}]
[3376][1714656247784][execution-node-process][error][{"subsystem":"system.startup","error":{"message":"Cannot destructure property 'memory' of '(intermediate value)' as it is undefined.","stack":"TypeError: Cannot destructure property 'memory' of '(intermediate value)' as it is undefined.\n at ExecutionEngine._getNumberOfPossibleGroups

[20112][1716816819308][main][error]["ExecutionProcess ~ Boot error",{"name":"Error","message":"Unhandled error. ({\n subsystem: 'system.startup',\n error: {\n message: \"Cannot destructure property 'memory' of '(intermediate value)' as it is undefined.\",\n stack: \"TypeError: Cannot destructure property 'memory' of '(intermediate value)' as it is undefined.\\n\" +\n ' at ExecutionEngine._getNumberOfPossibleGroups

tagtag21 commented 1 month ago

My logs with the problem logs.zip

nikithaachhini23 commented 1 month ago

Thanks a lot guys for your inputs and efforts in providing us logs. Appreciate your patience with us.

So far my analysis:

  1. While using the postman app on a different language say Japanese via app general settings. Running a performance test on windows machine might not be working. Are you guys using the app in a different language?
  2. Based on the logs, there's an issue while retrieving available memory from the user's windows machine to run a performance test. We have got all the logs data we need. Thanks again!

We're definitely considering this as a priority issue and will be looking into it soon. Rest assured we'll fix it as soon as we can and update you.

VictorStala commented 1 month ago

Hello, I've ran into the problem described above aswell. These are the commands mentioned for testing on the ticket #12852 so here are the results, hope this helps! mem-test

albaraX commented 1 month ago

Hello, I've ran into the problem described above aswell. These are the commands mentioned for testing on the ticket #12852 so here are the results, hope this helps! mem-test

Right now run those commands and got same response, but I have a bit more free memory

tagtag21 commented 1 month ago

Hello! My results Screenshot_5 Screenshot_4

NazeehAlhosary commented 1 month ago

@deibyd Hi, I have the latest version (v11.1.14), and I still have the same issue.

johseffer commented 1 month ago

same here

image

image

postfrzero commented 1 month ago

Hey folks, we've identified an issue which could be leading to these errors and we're working on rolling out a Canary app build which could resolve this while the changes are integrated into the mainline app. Either @nikithaachhini23 or I will post an update here as soon as we have something tangible.

Thairam commented 4 weeks ago

same here.

manuelmilian commented 3 weeks ago

same here, Postman v11.2.0 on Windows 11

tagtag21 commented 2 weeks ago

@postfrzero Hello!

Please write when the fix is ​​planned?

issamansur commented 2 weeks ago

I wanted to start test today, but had same issue. Version: 11.2.12 (latest) I have no folders in collection

P.S.: interesting, that at start I had this error image After reloading page of runner had this: image

qa-oks commented 2 weeks ago

The same issue, version 11.2.12. Is there any information about the fixing? Seems like the problem is kind of critical for a lot of people here

filippoitaliano commented 2 weeks ago

I have the same issue. I think it's also worth mentioning I experience this same behavior on Windows 11 and also on the latest macOS, both with the latest version of Postman. Right now I'm using version 10.24.2 to be able to run Performance tests.

seifeddine55 commented 2 weeks ago

Our team have the same error using 11.12.1 but for 10.24.25 it's working. Any thought about this kind of behavior

issamansur commented 2 weeks ago

Guys, please, can you send link/site , where I can download stable version of postman with working performance test (10.24.2-10.24.25)?

filippoitaliano commented 2 weeks ago

@issamansur Postman portable from Portapps is the one i'm using. It bundles version 10.24. Don't take this as a recommendation. Please do your research on https://github.com/portapps reliability 🙏.

issamansur commented 2 weeks ago

@issamansur Postman portable from Portapps is the one i'm using. It bundles version 10.24. Don't take this as a recommendation. Please do your research on https://github.com/portapps reliability 🙏.

Thank you so much!