Script failed to start but AppVeyor report that build is successful

ruslan_baratov's Avatar

ruslan_baratov

21 Nov, 2015 11:13 PM

Hi,

Looks like there was some changes made in build machine environment. My old build was working but now it stopped:

Configs are the same:

I've figure out how to fix it but one problem still bothers me. As you can see in logs at line 15:

build.py python script failed to start but produce no error about it. Probably bad exit code is ignored or something, I think the status of the build should be FAILED there.

Thanks

  1. Support Staff 1 Posted by Feodor Fitsner on 22 Nov, 2015 02:03 AM

    Feodor Fitsner's Avatar

    You mean .py extension mapping? Yeah, it looks like it's gone after some Python reinstallation. Though I think it's better to explicitly call python.exe as there are multiple Python versions on build worker and it might be confusing if .py is mapped to specific version.

    - Feodor

  2. 2 Posted by ruslan_baratov on 22 Nov, 2015 02:18 AM

    ruslan_baratov's Avatar

    it's gone after some Python reinstallation

    Okay, that's what I was thinking. Anyway I've solved it.

    What about test SUCCESS status?

    I think result here should be "Build Failed".

  3. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:02 AM.

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

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