postman-app-support
postman-app-support copied to clipboard
Failed to run performance test
Is there an existing issue for this?
- [X] I have searched the tracker for existing similar issues and I know that duplicates will be closed
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."
Is there any version working that I could downgrade?
Thanks!
Steps To Reproduce
- 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
I have the same problem in 10.22.9
version
Same problem here in 10.22.9
.
Edit: The problem is happening only if there is folders inside the collection.
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.
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
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.
@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.
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.
For me works whole collection even it has tests within folders.
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
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.
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.
@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?
I prefer the old postman... This new one should renamed to bugman
这个就很操蛋
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".
这个就很操蛋
[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."]
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".
这个就很操蛋
The same version worked before, but suddenly it stopped working for a while. I opened the console and no error was reported.
Maybe if you use all your runner's limits (25/25) then you can't start a performance test? I have 40/25 runs
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
Same here, Postman just does not initiate a performing test, wichever the VU, Duration or Load profile. It just does not work.
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?
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?
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
I am experiencing exactly the same issue. When I try to perform a load test, it returns an error.
Please help me to be able to perform these load tests. Could it be a subscription issue where I need to pay?
@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?
@s93rum06 Could you please zip the entire logs
folder and send it?
@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
@deibyd hi . I have a similar problem, did you manage to figure it out?
@deibyd Hi, same issue.