sitespeedio / sitespeedio/sitespeed.io

Error: ENOENT: no such file or directory - This issue is observing while executing await commands.measure.stop() command for second time

Open
#4,192 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
5k
Forks
624
Avg merge
4h 8m
Merged PRs (30d)
2

Description

I have site speed script to run through Jenkins pipeline and while its running i'm getting following error. This issue is getting while trying to execute the await commands.measure.stop(); command for second time (line 50).

Error: ENOENT: no such file or directory,

Login transaction is successfully completed (line 34 - line 41). During the login transaction await commands.measure.stop();(line 39) executed without any errors for the 1st time.

i have uploaded the java script file i'm running as an attachment(Test.js)
Test.txt

i have attached the pipeline script which is currently running
pipeline.txt

image image

p.s - This script is working fine in local environment.(no issues)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the attached Test.js, especially lines 34–41 and line 50, and compare its second commands.measure.stop() call with the Jenkins configuration in pipeline.txt. Reproduce the script in Jenkins rather than locally, then trace the ENOENT location; done means both measurement stops complete without the missing-file error in the pipeline.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
ci-cd, cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.