Allow failures behavior is problematic

dane's Avatar


20 Jun, 2014 04:33 PM

I'm having a lot of trouble getting the allow_failures behavior they way I'd like. As someone coming from travis I'm obviously biased by that experience so let me describe.

I use appveyor to build binary packages with node-pre-gyp. It is common for a build for one node.js version to fail while others might succeed. So I don't want a single build, say against node v0.11.x, to stop all the other jobs.

One request is that if one build fails and stops other jobs (independent of the allow_failures setting) it would be great, through the appveyor UI, to be able to click on a job and (re)start it. Currently it appears you can only do this (hitting the "new build" button) for jobs that once ran and not for jobs that never ran because other ones failed. If I try to click "new build" for a job that was blocked by another job failing I get the error of Project not found or access denied..

The above is a common desire because I'm having a lot of trouble figuring out the right syntax for allow_failures so that all jobs run no matter whether others fail. On recent example is node-srs. With this appveyor config ( I saw the build do this: That is not what I expected because 1) the overall color of the build is green (seemingly indicating that either all jobs succeeded or all were allowed to fail), and 2) only one job ran (despite the allow_failures setting) and I want all jobs to run.

I'm currently testing this modification:

So, to recap: I think the allow_failures syntax either is not working or is too hard to use. It should be much easier to achieve the travis behavior of all jobs running. I would really prefer that all jobs running be the default, but until then I'd love to hear ideas of what I'm doing wrong or what I'm missing.


  1. 1 Posted by dane on 20 Jun, 2014 04:44 PM

    dane's Avatar

    Latest build with:

        - platform: x86
          nodejs_version: 0.10
        - platform: x86
          nodejs_version: 0.11
        - platform: x64
          nodejs_version: 0.10
        - platform: x64
          nodejs_version: 0.11

    Does not quite work yet. It appears that a failing in one node v0.11.x version did not prevent node v0.10.x from building (yay) but did prevent the other node v0.11.x build from running. This is a problem because all node v0.11.x build are know to fail, but not till the very end due to this aws-sdk bug and before that failure I'm posting build artifacts that are important to work around the aws-sdk bug.

    Here is the build:

  2. Support Staff 2 Posted by Feodor Fitsner on 23 Jun, 2014 05:56 PM

    Feodor Fitsner's Avatar

    So, if I correctly understand the main issue right now is default "fail fast" strategy in build matrix where first failed job immediately fails the entire build with running/queued jobs. You need "run all" behavior where all jobs run no matter what and the build is considered failed if at least on job has failed. Correct?

  3. 3 Posted by dane on 24 Jun, 2014 03:24 AM

    dane's Avatar

    Yes, that's exactly what I'm looking for.

  4. Support Staff 4 Posted by Feodor Fitsner on 24 Jun, 2014 03:34 AM

    Feodor Fitsner's Avatar

    I see. Looks like it's better moving in this direction. I will add a new item - don't think it's hard to implement.

  5. 5 Posted by dane on 15 Jul, 2014 07:18 PM

    dane's Avatar

    Hello Feodor,

    Have you had a chance to fix this? It is still feeling quite problematic. Most recently I've seen this type of error ( randomly and that cancels all the other builds all of a sudden. Ideally I would only need to restart the one build that fails randomly due to a network problem.

    Thanks, Dane

  6. Support Staff 6 Posted by Feodor Fitsner on 15 Jul, 2014 08:39 PM

    Feodor Fitsner's Avatar

    Will try delivering that this week, sorry for the delay.

  7. 7 Posted by dane on 15 Jul, 2014 08:55 PM

    dane's Avatar

    Okay, thank you for the update!


  8. Support Staff 8 Posted by Feodor Fitsner on 17 Jul, 2014 09:02 AM

    Feodor Fitsner's Avatar

    Hi Dane,

    A new update with fast_finish feature (sorry for borrowing the name from Travis) has been just deployed. Now, unlike it was done before, all build jobs run to the end no matter what. To make a build fail immediately once one of the jobs fails add to appveyor.yml:

      fast_finish: true

    Sample output:

  9. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:46 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? 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