-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jet time-out issue cases #1695
Comments
It may be worth noting that these same tests timeout on S4, which has similar architecture to xjet. |
@jkbk2004 regional_atmaq regional_atmaq_faster are still failing. However, regional_noquilt, hafs_regional_datm_cdeps, regional_wofs are now passing on Jet. |
@jkbk2004 I'll give these a try on S4 as well. |
Running with the current develop, Test Directory: regional_atmaq I'm seeing a 137 exit code in
In regional_atmaq_faster, I'm seeing a memory error |
@FernandoAndrade-NOAA what about ulimit -s unlimited option in jet job card? |
Adding that option has at least caused the same insufficient virtual memory error to show up in |
@FernandoAndrade-NOAA can you try TPN=16 for those tests? |
Sure thing, it was also suggested to try ulimit -l unlimited, so I'll add that as well. I believe @zach1221 has previously tried a different TPN for jet. Zach do you remember if you had used 16 or 18? |
Both are unfortunately still failing after those adjustments. I am seeing slightly different err messages:
|
Hey, @FernandoAndrade-NOAA . Yes I attempted 18 in the past with no luck. |
@jkbk2004 I re-tested these on Rocky8 and they passed, specifically regional_noquilt, hafs_regional_datm_cdeps, and regional_wofs. It doesn't look like regional_atmaq_faster is in rt.conf anymore and regional_atmaq has been hashed out, but I ran the atmaq compile suite successfully. |
@jkbk2004 per our conversation, closing this issue. |
Description
Solution
Related to
The text was updated successfully, but these errors were encountered: