Unable to run percy snapshot locally and in CI

[AxonC]

I'm experiencing an issue trying to run Percy locally and in a CI environment.

If I use the --debug flag on the command it works fine (as in does all the steps including downloading Selenium etc.). The stack trace appears to suggest based upon the source code this is an error with communicating with the Percy API?

I've refreshed the token to eliminate that - same error with both tokens set in the environment variable.

Command run: npx percy snapshot . --verbose (verbose for extra logging).

Version: 1.0.0-beta.72
Node: v14.17.1

Azure DevOps Pipeline Log:
(Identical to local stack trace)

[percy:config] Found config file: .percy.yml (0ms)
[percy:config] Using config:
{
  version: 2,
  snapshot: {
    enableJavaScript: true,
    minHeight: 1024,
    widths: [
      375,
      1280
    ]
  },
  static: {
    include: '**/*.snapshot.html'
  }
} (17ms)
[percy:client] Creating a new build... (229ms)
[percy:cli:snapshot] Error: sha: must be filled; message: must be filled; committed-at: must be filled; parents: must be an array
    at handleFinished (/home/vsts/work/1/s/node_modules/@percy/client/dist/request.js:266:17)
    at IncomingMessage.<anonymous> (/home/vsts/work/1/s/node_modules/@percy/client/dist/request.js:282:27)
    at IncomingMessage.emit (node:events:402:35)
    at endReadableNT (node:internal/streams/readable:1343:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) (739ms)

[AxonC]

I realise this is the wrong place to raise this. I'll use the support channel. Thanks.

[Robdel12]

Hey @AxonC! This is a good place for it -- those support requests just make their way back to me and @wwilsman in the end.

It looks like the build is failing to be created, is there a proper git SHA in the CI env? Can you check the values of these env vars and make sure it's a proper full git SHA? https://github.com/percy/cli/blob/master/packages/env/src/environment.js#L96

Edit; actually I see you say this happens locally too. That is pretty interesting 🤨 What's the git situation like for this project?

[Robdel12]

When a build is created the API will try and talk to the source code integration (azure here), so that's why it'll fail everywhere. Hopefully we'll have an answer for what's going on by your morning! 😃

[AxonC]

I did some digging in our main release pipeline and it appears to have worked as recently as 26th Jan, not 17th December 21 as I previously mentioned as happening in our canary pipeline.

[AxonC]

Hi @Robdel12 I don't suppose you've managed to make any progress on a resolution here?

[Robdel12]

@AxonC This one is out of my hands and in the engineering teams hands -- @j000shDotCom should have some time this week to investigate and see what's going on with Azure.

[AxonC]

@Robdel12 Hi - not sure if any changes were made, but it now is running locally again!

However, in the pipelines, it is now producing a different error.

[percy:client] Creating a new build... (1ms)
[percy:core] Failed to create build (1255ms)
[percy:core] Error: 500 Internal Server Error
    at handleFinished (file:///home/vsts/work/1/s/node_modules/@percy/client/dist/utils.js:173:17)
    at IncomingMessage.<anonymous> (file:///home/vsts/work/1/s/node_modules/@percy/client/dist/utils.js:191:27)
    at IncomingMessage.emit (node:events:538:35)
    at endReadableNT (node:internal/streams/readable:1345:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) (1ms)
[percy:core] Uploading 0 snapshots...
[percy:core:browser] Closing browser (20ms)
[percy:core:browser] Browser closed (41ms)
[percy:core] Build not created (1ms)