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

Draft
Niols wants to merge 8 commits from pixelfed-ci into main
Owner
No description provided.
Niols added 6 commits 2024-11-17 00:06:52 +01:00
This is in particular useful for debugging, and it should not hurt the
non-interactive variant of the tests.
Last fixes to the test
All checks were successful
/ check-pre-commit (pull_request) Successful in 22s
d6dd77ae11
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
Author
Owner

@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 added 1 commit 2024-11-17 11:17:47 +01:00
[TEST] Add --remote-debugging-port
Some checks failed
/ check-pre-commit (pull_request) Successful in 39s
/ check-pixelfed-garage (pull_request) Failing after 53m52s
6de5a4b31b
I don't see why this would do anything, but this is recommended when
getting the error

selenium.common.exceptions.SessionNotCreatedException: Message: session not created: DevToolsActivePort file doesn't exist

(see https://git.fediversity.eu/Fediversity/Fediversity/actions/runs/12/jobs/1)

Personally, I think it comes from the fact that the CI machines are sooo
slow that things don't work properly.
Author
Owner

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 added 1 commit 2024-11-27 11:42:54 +01:00
Pixelfed on Firefox
Some checks failed
/ check-pre-commit (pull_request) Failing after 0s
/ check-pixelfed-garage (pull_request) Failing after 42m16s
499e5eb5ac
Niols added 1 commit 2024-11-27 11:47:24 +01:00
Sleep much longer
Some checks failed
/ check-pre-commit (pull_request) Successful in 21s
/ check-pixelfed-garage (pull_request) Failing after 0s
7512d8a6e9
Niols force-pushed pixelfed-ci from 7512d8a6e9 to 51e6bc7ca6 2024-11-27 14:39:02 +01:00 Compare

@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?
Author
Owner

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.
Some checks failed
/ check-pre-commit (pull_request) Has been cancelled
Required
Details
/ check-pixelfed-garage (pull_request) Has been cancelled
This pull request has changes conflicting with the target branch.
  • .forgejo/workflows/ci.yaml
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin pixelfed-ci:pixelfed-ci
git checkout pixelfed-ci
Sign in to join this conversation.
No reviewers
No milestone
No project
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.