Skip to content

Spurious failures on AppVeyor due to ar.exe errors #40546

@alexcrichton

Description

@alexcrichton
Member

I've previously been classifying these errors under #40240 but now I'm thinking that's incorrect, I suspect these are totally separate errors.

https://ci.appveyor.com/project/rust-lang/rust/build/1.0.2397

[ 13%] Linking CXX static library ../../libLLVMMCDisassembler.a
C:/projects/rust/mingw64/bin/ar.exe: ../../libLLVMMCDisassembler.a: Permission denied
make[2]: *** [lib/MC/MCDisassembler/CMakeFiles/LLVMMCDisassembler.dir/build.make:205: lib/libLLVMMCDisassembler.a] Error 1
make[2]: *** Deleting file 'lib/libLLVMMCDisassembler.a'
make[1]: *** [CMakeFiles/Makefile2:2539: lib/MC/MCDisassembler/CMakeFiles/LLVMMCDisassembler.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 13%] Built target LLVMMCParser
make: *** [Makefile:150: all] Error 2
thread 'main' panicked at '
command did not execute successfully, got: exit code: 2

Activity

added
A-spuriousArea: Spurious failures in builds (spuriously == for no apparent reason)
on Mar 15, 2017
alexcrichton

alexcrichton commented on Mar 15, 2017

@alexcrichton
MemberAuthor

The first hit on Google is quite ominous. My preference for an attempt to fix this would be to switch to ninja as it's likely just flat out more reliable than makefiles on MinGW

alexcrichton

alexcrichton commented on Mar 15, 2017

@alexcrichton
MemberAuthor

Oh also we're going to want to switch the MSVC build to Ninja regardless, so we'll have it available anyway eventually on the bots.

mati865

mati865 commented on Mar 15, 2017

@mati865
Member

I've met it few times with MSYS2 and (almost?) always it was caused by CL RF line endings or too long paths or file names.
When compiling Rust from git I found there are files that windows explorer cannot remove since they are too long. Unfortunately I don't have list as I used MSYS2 rm -rf * to clean those files.

81 remaining items

added a commit that references this issue on Apr 26, 2017

Auto merge of #41420 - alexcrichton:mingw-6.3.0, r=petrochenkov

Mark-Simulacrum

Mark-Simulacrum commented on Apr 29, 2017

@Mark-Simulacrum
Member

This is, unfortunately, still a problem. See #41580 (comment).

Mark-Simulacrum

Mark-Simulacrum commented on Apr 29, 2017

@Mark-Simulacrum
Member

Possibly a false alarm. #41580 is targeting the beta branch, which presumably does not have the fix for this failure, in which case it's "normal" for it to fail spuriously. Will leave open for someone to confirm, though.

alexcrichton

alexcrichton commented on Apr 29, 2017

@alexcrichton
MemberAuthor

@Mark-Simulacrum ah yeah I think we're ok, #41420, the fix, is only on master not on beta

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-spuriousArea: Spurious failures in builds (spuriously == for no apparent reason)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Participants

      @alexcrichton@carols10cents@crlf0710@aidanhs@mati865

      Issue actions

        Spurious failures on AppVeyor due to ar.exe errors · Issue #40546 · rust-lang/rust