fediversity/fediversity
13
2
Fork 6
Code Issues 157 Pull requests 29 Projects 1 Activity Actions

WIP: (Re-)introduce a working CI test for Pixelfed #7

Closed
Niols wants to merge 8 commits from pixelfed-ci into main
pull from: pixelfed-ci
merge into: fediversity:main
Conversation 4 Commits 8 Files changed 3 +41 -18
Niols commented 2024-11-17 00:06:50 +01:00
Owner
Copy link
No description provided.
Niols force-pushed pixelfed-ci from d6dd77ae11 to e05d693cdf 2024-11-17 00:10:33 +01:00 Compare
Niols force-pushed pixelfed-ci from e05d693cdf to 29e0b52ef4 2024-11-17 00:11:42 +01:00 Compare
Niols commented 2024-11-17 01:37:03 +01:00
Author
Owner
Copy link

@koen @kevin> The actions runners take forever to run my tests. On the Tweag builders, then run in under 2 minutes. On my laptop, they run in 15 to 30 minutes depending on whether I'm also in a call at the same time, for instance. Here, they take nearly an hour! Is there any way we could get beefier machines? I know we can add more cores and more RAM, but the effect is only marginal; I'd rather have faster cores, but I don't know if that is possible?

@koen @kevin> The actions runners take forever to run my tests. On the Tweag builders, then run in under 2 minutes. On my laptop, they run in 15 to 30 minutes depending on whether I'm also in a call at the same time, for instance. Here, they take nearly an hour! Is there any way we could get beefier machines? I know we can add more cores and more RAM, but the effect is only marginal; I'd rather have faster cores, but I don't know if that is possible?
Niols commented 2024-11-18 12:48:17 +01:00
Author
Owner
Copy link

Something that deserves to be mentioned here is that the CI fails because the actions runners are so slow, I believe.

Specifically, Selenium tries to start the Chrome driver, and there is probably a timeout somewhere after which Chrome is still not detected, and Selenium crashes. I know how to increase the timeouts between steps of the Selenium scripts, but not the timeout related to starting the browser itself. Still, I will investigate.

Something that deserves to be mentioned here is that the CI fails because the actions runners are so slow, I believe. Specifically, Selenium tries to start the Chrome driver, and there is probably a timeout somewhere after which Chrome is still not detected, and Selenium crashes. I know how to increase the timeouts between steps of the Selenium scripts, but not the timeout related to starting the browser itself. Still, I will investigate.
Niols force-pushed pixelfed-ci from 6de5a4b31b to cfe4d57787 2024-11-19 13:18:03 +01:00 Compare
Niols force-pushed pixelfed-ci from cfe4d57787 to 508ad1ca66 2024-11-19 14:16:07 +01:00 Compare
Niols force-pushed pixelfed-ci from 508ad1ca66 to 29e0b52ef4 2024-11-23 18:31:53 +01:00 Compare
Niols force-pushed pixelfed-ci from 29e0b52ef4 to 3c537472a2 2024-11-26 13:44:28 +01:00 Compare
Niols force-pushed pixelfed-ci from 7512d8a6e9 to 51e6bc7ca6 2024-11-27 14:39:02 +01:00 Compare
fricklerhandwerk commented 2025-01-20 11:01:47 +01:00
Owner
Copy link

@Niols is this still relevant? We did get a beefier machine somewhere around that time, no?

@Niols is this still relevant? We did get a beefier machine somewhere around that time, no?
Niols commented 2025-01-23 12:56:07 +01:00
Author
Owner
Copy link

We got a beefier VM which I have successfully used for CI so far. There was also works to get a bare metal machine to get even more performances, but we never finished setting it up as a CI runner and everything. Now that we have a reasonable CI, the work remains to see what failures were due to low performances of the runner and what failures were due to the test being too flakey, so I'd say this is still relevant, and I should prioritise some time soon to make it run again.

We got a beefier VM which I have successfully used for CI so far. There was also works to get a bare metal machine to get even more performances, but we never finished setting it up as a CI runner and everything. Now that we have a reasonable CI, the work remains to see what failures were due to low performances of the runner and what failures were due to the test being too flakey, so I'd say this is still relevant, and I should prioritise some time soon to make it run again.
👍 1
Niols closed this pull request 2025-02-12 18:48:22 +01:00
Some checks are pending
/ check-pre-commit (pull_request) Has been cancelled
Required
Details
/ check-pixelfed-garage (pull_request) Has been cancelled
Details
/ check-data-model (pull_request)
Required
/ check-resources (pull_request)
Required
/ check-deployment-basic (pull_request)
Required
/ check-mastodon (pull_request)
Required
/ check-deployment-cli (pull_request)
Required
/ check-deployment-panel (pull_request)
Required
/ check-panel (pull_request)
Required
/ check-peertube (pull_request)
Required

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
0 points

fibonacci complexity: 0 points

  
0.5 points

fibonacci complexity: 0.5 points

  
1 point

fibonacci complexity: 1 point

  
13 points

fibonacci complexity: 13 points

  
2 points

fibonacci complexity: 2 points

  
21 points

fibonacci complexity: 21 points

  
3 points

fibonacci complexity: 3 points

  
34 points

fibonacci complexity: 34 points

  
5 points

fibonacci complexity: 5 points

  
55 points

fibonacci complexity: 55 points

  
8 points

fibonacci complexity: 8 points

  
api service

features that may relate more to a (to be created) API service

  
blocked

   
component: fediversity panel

   
component: nixops4

   
documentation

   
estimation high: >3d

   
estimation low: <2h

   
estimation mid: <8h

   
infinite points

fibonacci complexity: infinite points

  
productisation

features out-scoped with the decoupling of the productisation effort

  
project-management

Project management related tasks

  
question

   
role: application developer

   
role: application operator

   
role: hosting provider

   
role: maintainer

   
security

   
technical debt

   
testing

   
type unclear

   
type: bug

Anything that doesn't work as advertised

  
type: deliverable

   
type: key result

   
type: objective

   
type: task

   
type: user story

   
user experience
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: fediversity/fediversity#7
No description provided.
Delete branch "pixelfed-ci"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?