question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

FAIL  test/client.js
 ✖ (unnamed test)

  test/client.js                                          
  517 |       body                                        
  518 |     }, (err, { statusCode, headers, body }) => {  
> 519 |       t.error(err)                                
      | --------^                                         
  520 |       body                                        
  521 |         .on('data', () => {                       
  522 |           t.fail()                                

  test: test/client.js basic POST with empty stream
  stack: |
    test/client.js:519:9
    lib/api/api-request.js:132:14

  Error Origin:

  lib/llhttp/parser.js                                                                      
  187 |       const message = Buffer.from(inst.exports.memory.buffer, ptr, len).toString()  
  188 |       const code = constants.ERROR[err]                                             
> 189 |       return new HTTPParserError(message, code)                                     
      | -------------^                                                                      
  190 |     }                                                                               
  191 |   }                                                                                 
  192 | }                                                                                   

  stack: |
    Parser.execute (lib/llhttp/parser.js:189:14)
    Socket.onSocketData (lib/client.js:807:29)
  type: HTTPParserError
  code: HPE_INVALID_CONSTANT
  message: "HTTPParserError: "

 FAIL  test/client.js
 ✖ Cannot read property 'on' of undefined

  test/client.js                     
  519 |       t.error(err)           
  520 |       body                   
> 521 |         .on('data', () => {  
      | ---------^                   
  522 |           t.fail()           
  523 |         })                   
  524 |         .on('end', () => {   

  test: basic POST with empty stream
  stack: |
    test/client.js:521:10
    lib/api/api-request.js:132:14
  type: TypeError
  tapCaught: uncaughtException

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:12 (12 by maintainers)

github_iconTop GitHub Comments

1reaction
ronagcommented, Apr 6, 2021

Another one:

 FAIL  test/abort-controller.js
 ✖ should be equal

  test/abort-controller.js                                               
  65 |         })                                                        
  66 |         response.body.on('end', () => {                           
> 67 |           t.equal('hello', Buffer.concat(bufs).toString('utf8'))  
     | ------------^                                                     
  68 |         })                                                        
  69 |       })                                                          
  70 |                                                                   

  --- expected      
  +++ actual        
  @@ -1,1 +1,1 @@   
  -Upgrade Required 
  +hello            

  test: test/abort-controller.js Abort native-abortcontroller before sending
    request (no body)
  stack: |
    RequestResponse.<anonymous> (test/abort-controller.js:67:13)
0reactions
ronagcommented, Apr 6, 2021
Read more comments on GitHub >

github_iconTop Results From Across the Web

What are Flaky Tests? | TeamCity CI/CD Guide - JetBrains
Flaky tests are defined as tests that return both passes and failures despite no changes to the code or the test itself. Several...
Read more >
Flaky tests - GitLab Docs
What's a flaky test? It's a test that sometimes fails, but if you retry it enough times, it passes, eventually. What are the...
Read more >
What is a flaky test? Definition from WhatIs.com. - TechTarget
A flaky test is an analysis of web application code that fails to produce the same result each time the same analysis is...
Read more >
Flaky Tests: Getting Rid Of A Living Nightmare In Testing
A flaky test is one that fails to produce the same result each time the same analysis is run. The build will fail...
Read more >
How to Fix Flaky Tests - Semaphore CI
A test that intermittently fails for no apparent reason — or works in your local machine and fails with continuous integration — is...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found