x86 version of xunit

jaredpparsons's Avatar

jaredpparsons

03 Jun, 2014 09:54 PM

Is there any way to get AppVeyor to use the x86 version of xunit instead of the amd64 version (which appears to be the default)?

Several of my unit test assemblies can only run in x86 due to dependencies. When run in 64 bit mode they fail. Hence I need the x86 version of xunit.

This is not a blocking issue. I worked around this by checking the x86 runner into my github repository and manually invoke it for the tests. So I'm getting the coverage I need. Would just be nicer to have it as part of the built in setup if possible.

  1. Support Staff 1 Posted by Feodor Fitsner on 03 Jun, 2014 10:22 PM

    Feodor Fitsner's Avatar

    Yes, sure. This how we currently do for NUnit tests. Will do theSame for xUnit. 

    Apparently, looks like xUnit is more popular than NUnit :)

    - Feodor

  2. 2 Posted by jaredpparsons on 03 Jun, 2014 10:27 PM

    jaredpparsons's Avatar

    Thanks!

    I should have specified that I still build everything for AnyCPU, I just execute the tests in x86 mode.

  3. Support Staff 3 Posted by Feodor Fitsner on 03 Jun, 2014 10:29 PM

    Feodor Fitsner's Avatar

    Then we'll be running x86 and AnyCPU assemblies with x86 runner and x64 with x64, right?

    - Feodor

  4. 4 Posted by jaredpparsons on 03 Jun, 2014 10:55 PM

    jaredpparsons's Avatar

    Correct.

  5. 5 Posted by Anthony Seddon on 11 Jun, 2014 08:50 AM

    Anthony Seddon's Avatar

    We've got exactly the same problem as Jared.

    Do you have an ETA for the x86 version of xunit being available or a quick workaround?

    • Ant
  6. Support Staff 6 Posted by Feodor Fitsner on 11 Jun, 2014 07:43 PM

    Feodor Fitsner's Avatar

    As a quick workaround you can call x86 version of runner in your own test script. Copy the command from build console and replace runner with xunit.console.x86.exe or xunit.console.clr4.x86.exe.

    We will fix this issue today.

  7. 7 Posted by jaredpparsons on 11 Jun, 2014 07:58 PM

    jaredpparsons's Avatar

    Expanding on Feodor's suggestion. Here is a link to a concrete example of getting xunit to run in x86 mode by changing the appveyor.xml file.

    https://github.com/jaredpar/VsVim/blob/master/appveyor.yml

    I've been using this for a week now and it works like a champ.

  8. Support Staff 8 Posted by Feodor Fitsner on 13 Jun, 2014 05:08 AM

    Feodor Fitsner's Avatar

    xUnit selection has been implemented and deployed with the latest update.

  9. 9 Posted by phil on 14 Jun, 2014 05:27 AM

    phil's Avatar

    Perfect timing - I had this problem as well yesterday and now find that's been fixed!

    Keep up the good work!

  10. 10 Posted by Lilith River on 27 Aug, 2014 09:56 PM

    Lilith River's Avatar

    So, for example, I have an AnyCPU project that has native dependencies; I need to run the xunit tests in both a 32 and 64-bit process. How can I do that with the new update?

  11. Support Staff 11 Posted by Feodor Fitsner on 27 Aug, 2014 09:58 PM

    Feodor Fitsner's Avatar

    You should override automatic tests discovery with your own calls to xUnit runners.

  12. 12 Posted by Lilith River on 27 Aug, 2014 10:02 PM

    Lilith River's Avatar

    Like this?

    test_script:
      - xunit.console.exe Imazen.Test.WebP\bin\Release\Imazen.Test.Webp.dll /appveyor
      - xunit.console.x86.exe Imazen.Test.WebP\bin\Release\Imazen.Test.Webp.dll /appveyor
    
  13. Support Staff 13 Posted by Feodor Fitsner on 27 Aug, 2014 10:06 PM

    Feodor Fitsner's Avatar

    yep

  14. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:47 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

Recent Discussions

13 Apr, 2024 04:43 PM
12 Apr, 2024 04:56 PM
11 Apr, 2024 11:16 PM
09 Apr, 2024 10:59 PM
08 Apr, 2024 07:50 AM

 

06 Apr, 2024 04:06 AM
05 Apr, 2024 01:26 PM
05 Apr, 2024 10:39 AM
04 Apr, 2024 03:41 PM
31 Mar, 2024 05:51 PM
30 Mar, 2024 01:59 PM