Project

General

Profile

coordination #71926

Updated by okurz over 3 years ago

## Observation 

 In https://app.circleci.com/pipelines/github/os-autoinst/openQA/4353/workflows/072d1477-46e0-4ae1-88f1-90740da73506/jobs/41809 

 ``` 
 [14:37:26] t/14-grutasks.t ........................................... ok     274117 ms ( 0.22 usr    0.00 sys + 260.33 cusr    9.39 csys = 269.94 CPU) 
 ``` 

 but locally I have: 

 ``` 
 [21:33:58] t/14-grutasks.t .. 34/? [2020-09-26 21:34:04.39357] [15810] [error] Gru job error: No job ID specified. 
 [2020-09-26 21:34:04.44377] [15814] [error] Gru job error: Job 98765 does not exist. 
 [2020-09-26 21:34:04.51354] [15817] [error] Gru job error: Finalizing results of 1 modules failed 
 [21:33:58] t/14-grutasks.t .. ok       5976 ms ( 0.08 usr    0.01 sys +    3.34 cusr    0.90 csys =    4.33 CPU) 
 [21:34:04] 
 All tests successful. 
 Files=1, Tests=36,    6 wallclock secs ( 0.10 usr    0.01 sys +    3.34 cusr    0.90 csys =    4.35 CPU) 
 Result: PASS 
 ``` 

 so two differences: Insane long runtime within circleCI compared to just 6s locally but locally I have errors which do not fail the test. I can reproduce my local observations in 20 reruns with the same observation. ~~I I wonder if this is reproducible for anyone else.~~ Comparably small runtime was confirmed by others. 


 else. 

 ## Acceptance criteria 

 * **AC1:** No unhandled error messages in non-verbose output shown 
 * **AC2:** Runtime within CI is comparable to local runtime, e.g. less than 30s 

 ## Suggestions 

 * DONE: ~~Crosscheck Crosscheck locally if anyone can reproduce the observation from CI *or* my (okurz's) local one~~ same for others one 
 * If the error messages are expected, catch them with Test::Output, otherwise prevent them (or even better fail tests if there is any unexpected output) 
 * In case excessive runtime is reproducible in any environment, e.g. only within CI, with Devel::Cover, in a container, etc., then find a way to reduce runtime significantly

Back