Home → Problems →

Build hangs for small Ruby library

• Edit

Daniel Berger

18 May, 2015 03:11 PM

Hi,

I'm just testing out appveyor with a very small Ruby library that has some minimal setup. The problem is that it just hangs at various points when running the install script. How do I fix this?

I've attached the appveyor.yml file that matches the settings I'm using. My project is at https://ci.appveyor.com/project/djberg96/win32-ipc.

Also, is there a way to preserve a VM? I really don't need a pristine environment for testing small libraries, so provisioning a new VM for every build feels like massive overkill for my needs, and it takes a long time, too.

Thanks,

Dan

• appveyor.yml 412 Bytes

1. Support Staff 1 Posted by Feodor Fitsner on 18 May, 2015 05:40 PM

   

   There is no way to preserve VM between builds though you can use build cache (I see you're already trying it for Ruby). How many times did you get these timeouts?

   • Edit

2. 2 Posted by Daniel Berger on 18 May, 2015 06:20 PM

   

   I've been getting timeouts pretty much every time with the current configuration. Currently it looks like it's been stuck on "gem install ffi" for about 20 minutes.

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 18 May, 2015 06:22 PM

   

   I think gem update --system might be an issue. Try removing it. We don't know why - probably there is some conflict with another software/lib on the server.

   • Edit

4. 4 Posted by Daniel Berger on 18 May, 2015 06:45 PM

   

   Tried removing it, though I'm not sure how that would conflict with anything given that it's a pristine VM. Anyway, now it's just hung on another part of the install script.

   • Edit

5. Support Staff 5 Posted by Feodor Fitsner on 18 May, 2015 06:57 PM

   

   Seems like I found something related to SignalR. Going to look into that.

   • Edit

6. 6 Posted by Daniel Berger on 18 May, 2015 08:31 PM

   

   Ok, please keep me posted, and let me know if there's a workaround in the meantime.

   • Edit

7. Support Staff 7 Posted by Feodor Fitsner on 18 May, 2015 09:09 PM

   

   I'm afraid right now the only workaround here is re-build. Though we have to investigate what's so special about your project making it hang so frequently.

   • Edit

8. 8 Posted by Daniel Berger on 18 May, 2015 09:19 PM

   

   Hah, I deliberately chose one of my simplest libraries for my first project just so I could learn Appveyor. I hope it gets worked out.

   In the meantime, I'll keep trying, disabling as much as I can that I don't actually need to see if that helps any.

   • Edit

9. 9 Posted by deivid.rodrigue... on 18 May, 2015 10:31 PM

   

   Feodor, in case it might help your investigation, I'm having the same issue: https://ci.appveyor.com/project/deivid-rodriguez/byebug/build/264/job/sk5g4d9np0ped4y2. Should I try removing `gem update --system` as well or this is definitely something else?

   • Edit

10. Support Staff 10 Posted by Feodor Fitsner on 18 May, 2015 11:00 PM

    

    Yes, try removing it.

    When did you start getting that?

    - Feodor

    • Edit

11. 11 Posted by deivid.rodrigue... on 19 May, 2015 01:02 AM

    

    Thanks Feodor. It seems that I started getting it when I added that line, but it's been passing & failing intermitently so I was not sure that was the problem. In any case, removing the line fixed it for now. If it starts failing again I'll let you know.

    • Edit

12. 12 Posted by Daniel Berger on 19 May, 2015 12:18 PM

    

    I switched to a powershell script, removed the gem update command, and now skip the gem installs if they're already installed (since I have a build cache). This helped, and it completed the first environment matrix, but hung on the second one.

    • Edit

13. 13 Posted by Daniel Berger on 19 May, 2015 04:59 PM

    

    It seems to be working better now (without the gem update call), though how much of that is because of the build cache, I couldn't say.

    • Edit

14. 14 Posted by Daniel Berger on 20 May, 2015 02:00 PM

    

    I tried another small github project. That one hangs on the install script, too, so it's not gem update causing it.

    https://ci.appveyor.com/project/djberg96/ptools

    • Edit

15. Support Staff 15 Posted by Feodor Fitsner on 20 May, 2015 05:42 PM

    

    Will take a look. Could you drop appveyor.yml please?

    • Edit

16. 16 Posted by Daniel Berger on 20 May, 2015 06:25 PM

    

    I would if I could. I'm on the "Export YAML" tab, but it won't export the yaml file, nor does it show me one.

    • Edit

17. Support Staff 17 Posted by Feodor Fitsner on 20 May, 2015 06:25 PM

    

    OK, what are the commands/scripts then?

    • Edit

18. 18 Posted by Daniel Berger on 20 May, 2015 06:27 PM

    

    Powershell:

        $env:path = "C:\Ruby" + $env:ruby_version + "\bin;" + $env:path
        $tpath = "C:\Ruby" + $env:ruby_version + "\lib\ruby\" + $env:ruby_dir + "\test"
        if ((test-path $tpath) -eq $True){ rm -recurse -force $tpath }
        if ((gem query -i win32-file) -eq $False){ gem install win32-file }
        if ((gem query -i test-unit -v ">= 3.0") -eq $False){ gem install test-unit }

    • Edit

19. 19 Posted by Daniel Berger on 21 May, 2015 03:18 PM

    

    Any luck? Do you still believe this is a SignalR issue?

    • Edit

20. Support Staff 20 Posted by Feodor Fitsner on 22 May, 2015 04:02 AM

    

    Will dig more next week.

    • Edit

21. 21 Posted by Daniel Berger on 09 Jun, 2015 12:51 PM

    

    Still having an issue. I tried suppressing the output of gem update, thinking maybe it was not liking so much output to stdout, but that doesn't appear to have mattered.

    https://ci.appveyor.com/project/djberg96/win32-ipc/build/job/8x8628461ke44rxd

    I've attached the yml file. Would it help to use a proxy? If so, what should I set it to?

    • appveyor-win32-ipc.yml 1.01 KB
    • Edit

22. Support Staff 22 Posted by Feodor Fitsner on 11 Jun, 2015 02:00 AM

    

    I'll look into that.

    • Edit

23. 23 Posted by Daniel Berger on 14 Jul, 2015 04:06 PM

    

    Still having some issues, though now instead of hanging it's giving me very strange errors on the last build. The first 3 build fine.

    http://blogs.msdn.com/b/oldnewthing/archive/2004/12/22/329884.aspx

    • Edit

24. Support Staff 24 Posted by Feodor Fitsner on 14 Jul, 2015 04:35 PM

    

    It's gem : ERROR: You must specify a gem name in the last build.

    • Edit

25. 25 Posted by Daniel Berger on 14 Jul, 2015 04:41 PM

    

    Oops, pasted the wrong link in that last post:

    https://ci.appveyor.com/project/djberg96/win32-ipc/build/job/gcp4wwb7s7yf1i1l

    • Edit

26. Support Staff 26 Posted by Feodor Fitsner on 14 Jul, 2015 04:43 PM

    

    Yeah, found the link in the original post.

    It starts from invalid option: --no-document in gem update command.

    • Edit

27. 27 Posted by Daniel Berger on 14 Jul, 2015 04:44 PM

    

    Oh, it's an older version of rubygems, which doesn't support that option.

    • Edit

28. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:57 AM.