Hi, I'm trying to use Jenkins to automate some hardware build and sim jobs. One of these jobs is to build an FPGA. I use Jenkins to call an FPGA build tool. The FPGA build tool runs processes in parallel (~10 jobs each hogging a CPU and ~10GB of RAM) in order to speedup build time. When I run the tool standalone it runs in ~10 hours. On Jenkins it can run for >24 hours (which is no use, I need this to run overnight). If I only have 1 run it runs OK in 10 hours.
When I look at what is going on it seems that some of the "parallel" jobs stall. There is a timeout (within the FPGA build tool - TCL internal to the tool) which isn't getting hit so it looks like Jenkins somehow stalls these jobs. I'm running the job on the same server that the Jenkins instance is running on. Does Jenkins somehow throttle jobs that consume large amount of memory? I mean is there some limit that I can change within Jenkins? There is one thing within the parallel builds in that when 1 finishes the stdout from the FPGA build tool switches from 1 of the parallel builds to another. There is also quite a lot of console output 10MB or so. Any help/thoughts appreciated, Mike. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAK2oGcrmAsW%2BUe1MJk%3Dk6PcisUMNYuaWSuWUVZCTYgX0R7EH0Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
