Custom Query (3268 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (40 - 42 of 3268)

Ticket Resolution Summary Owner Reporter
#3029 fixed Suites keep stopping ros ChrisWells
Description

Hi,

I have some suites running for a long time (u-bl918, u-bm502, u-bm503, u-bm504, u-bm505, u-bm798) and they keep stopping, with the message in gcylc "stopped with running". When I do rose suite-run —restart on them, they start again, but they stop again sometime after. This is extending the time the suites will take to run (e.g. I just had to restart 5 out of 6, which had all stopped on Friday).

Do you know why this is happening, and how I can prevent it?

Cheers, Chris

#3035 answered Failing on Supermean um_support ChrisWells
Description

Hi,

I have a test atmos-only suite, u-bn514, which fails on Supermean with this error:

/usr/lib64/python2.6/site-packages/requests/packages/urllib3/connection.py:337: SubjectAltNameWarning: Certificate for xcslc1 has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/shazow/urllib3/issues/497 for details.)
  SubjectAltNameWarning
Task not supported on MONSooN
2019-10-08T14:33:26Z CRITICAL - failed/EXIT
/usr/lib64/python2.6/site-packages/requests/packages/urllib3/connection.py:337: SubjectAltNameWarning: Certificate for xcslc1 has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/shazow/urllib3/issues/497 for details.)
  SubjectAltNameWarningvv

which I don't understand. I got past the 1st of these by resetting the state of Supermean to "Succeeded" but I can't do that each cycle. Do you know how I should fix this?

Cheers, Chris

#3045 fixed archive_integrity failed on old files willie ChrisWells
Description

Hi,

I have some suites which all failed a few hours ago on archive_integrity, pointing out that some files are missing from MASS, but the files they mention aren't ones from the year the model is currently on; they're from around 50 years prior, which the model ran about a month ago.

E.g. in suite u-bm503, which is on 2274 currently, file moose:/crum/u-bm503/ap4.pp/bm503a.p42224feb.pp is missing. And u-bm502, on 2274 also, is missing bm502a.pd2222feb.pp.

The other suites affected are u-bm504, u-bm505, and u-bm798. All the failed archives seem to be from around 20th September.

I'm not sure why these missing files weren't flagged up before.

Do you know what I should do about this?

Cheers, Chris

Note: See TracQuery for help on using queries.