Appveyor build fails whereas local build succeeds

godrose's Avatar

godrose

15 Jan, 2019 06:14 PM

The appveyor build for the project https://ci.appveyor.com/project/LogoFX/samples-specifications fails whereas the local build is just fine.
What could account for this issue (it used to work for the previous code commit)

  1. Support Staff 1 Posted by Owen McDonnell on 15 Jan, 2019 06:42 PM

    Owen McDonnell's Avatar

    Can you go to last successful build and hit RE-BUILD COMMIT and let us know the result.

  2. 2 Posted by godrose on 15 Jan, 2019 07:23 PM

    godrose's Avatar

    Same result. Might be something with the env/machine?

  3. Support Staff 3 Posted by Owen McDonnell on 16 Jan, 2019 04:18 PM

    Owen McDonnell's Avatar

    I can't see anything obvious that could be causing this. The builds look exactly the same but some UI tests are now failing.

    Can you try switching to Previous Visual Studio 2017 image for one build and see if the result is the same.

  4. 4 Posted by godrose on 17 Jan, 2019 01:09 PM

    godrose's Avatar
  5. Support Staff 5 Posted by Owen McDonnell on 18 Jan, 2019 06:43 PM

    Owen McDonnell's Avatar

    It must be a problem of resource usage that is coming close to some boundary that causes failure.

    I forked your repo and tried some builds with APPVEYOR_BUILD_WORKER_CLOUD: GCE set as an environment variable so that the build runs on our Google compute engine build worker cloud, which has slightly more performant machines and the build succeeded.

    You could try the same and/or try running your tests with parallelism disabled. See Changing Default Behaviour here

  6. 6 Posted by godrose on 19 Jan, 2019 08:02 PM

    godrose's Avatar

    > It must be a problem of resource usage that is coming close to some boundary that causes failure.

    Could be yet the usage hasn't changed since the last working commit so it's highly unlikely

    > I forked your repo and tried some builds with APPVEYOR_BUILD_WORKER_CLOUD: GCE set as an environment variable so that the build runs on our Google compute engine build worker cloud, which has slightly more performant machines and the build succeeded.

    Ok, I will try this approach

    > You could try the same and/or try running your tests with parallelism disabled. See Changing Default Behaviour

    This suite doesn't run in parallel. It can't run in parallel - the tests are all E2E with single instance app which is started and stopped for every test/scenario. Again it's highly unlikely that this is the root cause in this case.

  7. 7 Posted by godrose on 19 Jan, 2019 08:09 PM

    godrose's Avatar

    GCE approach was successful.
    Can this approach be used as permanent one or is it just a temporary measure?

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac