janhoy opened a new issue, #901:
URL: https://github.com/apache/solr-operator/issues/901

   Several e2e specs fail intermittently in CI on both Solr 9.11 and 10.1, 
independent of the change under test. Re-running the job usually passes.
   
   | Spec | Symptom | Recent failures (job) |
   |---|---|---|
   | SolrCloud - Storage › Persistent Data - Expansion › Fully Expands | After 
the rolling restart, querying a collection returns HTTP 500 after ~60s 
(`test_utils_test.go:312`) | 
[135061405283](https://github.com/apache/solr-operator/actions/runs/44376374678/job/135061405283),
 
[135077505967](https://github.com/apache/solr-operator/actions/jobs/135077505967),
 
[129048380312](https://github.com/apache/solr-operator/actions/jobs/129048380312),
 
[128914789734](https://github.com/apache/solr-operator/actions/jobs/128914789734)
 |
   | SolrCloud - Ingress › Can Remove Ingress and Services when changing 
addressability › Can adapt to changing needs | Headless service still exists 
right after the pod update (`solrcloud_ingress_test.go:134`, `Consistently` 
fails after 6ms) | 
[135061405283](https://github.com/apache/solr-operator/actions/runs/44376374678/job/135061405283),
 
[129222769333](https://github.com/apache/solr-operator/actions/jobs/129222769333),
 
[129197226011](https://github.com/apache/solr-operator/actions/jobs/129197226011)
 |
   | Backups › Local Directory - Single › Takes a backup correctly | Fails in 
`BeforeAll` | 
[132634657662](https://github.com/apache/solr-operator/actions/jobs/132634657662),
 
[129101306235](https://github.com/apache/solr-operator/actions/jobs/129101306235),
 
[129101299268](https://github.com/apache/solr-operator/actions/jobs/129101299268)
 |
   
   The Ingress failure is a timing assumption: line 134 calls 
`expectNoService`, which checks with `Consistently` right after the pod update, 
before the operator has had time to delete the headless service. Using the 
existing `eventuallyExpectNoService` there should fix it.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to