vatsrahul1001 commented on PR #60738:
URL: https://github.com/apache/airflow/pull/60738#issuecomment-3816733830

   > @vatsrahul1001 @choo121600 I noticed that a few CRUD tests are failing on 
Chromium in CI, while the same tests pass on Firefox and WebKit. All tests are 
also passing locally for all browsers. It seems like CI is sometimes unable to 
locate elements within the timeout in Chromium. Could you please suggest the 
best way to handle this? Would increasing timeouts be acceptable here, or is 
there a preferred approach for this? Also, please let me know if any other 
changes are required in the code.
   
   @vishakha1411 As per the stacktrace from 
[failure](https://github.com/apache/airflow/actions/runs/21434504965/job/61725112861?pr=60738)
 I see even after clicking on edit button edit form is not visible as per 
failure screenshot
   <img width="766" height="432" alt="image" 
src="https://github.com/user-attachments/assets/f2e3f098-1ce7-4643-bf19-4bcb937fb962";
 />
   
   ```
     131 |     await expect(editButton).toBeVisible({ timeout: 5000 });
     132 |     await editButton.click();
   > 133 |     await expect(this.connectionIdInput).toBeVisible({ timeout: 3000 
});
         |                                          ^
     134 |   }
   ```
   
   For debugging purposes, always try to look at the failure report. You can 
download the report from upload result 
[steps](https://github.com/apache/airflow/actions/runs/21434504965/job/61725112861?pr=60738).
   
   There could be two issues here: either the edit button is not getting 
clicked correctly, or it's taking time to open the edit button. Yes, you can 
try increasing the timeout, and also confirm if the edit button is getting 
clicked correctly or not.
   
   As you mentioned, it works locally fine, but I still suggest trying running 
test in UI mode, you can --ui-mode in breeze test command arg. It helps a lot 
in debugging


-- 
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]

Reply via email to