Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SITESPEED_OPTIONS : "--browsertime.connectivity.profile 3g " doesn't seem to work on gitlab #4021

Closed
2 tasks done
NOuennich opened this issue Dec 5, 2023 · 5 comments
Closed
2 tasks done
Labels

Comments

@NOuennich
Copy link

NOuennich commented Dec 5, 2023

Have you read the documentation?

URL

https://parkos.it/

What are you trying to accomplish

I'm running sitespeed with gitlab simple configuration https://docs.gitlab.com/ee/user/project/merge_requests/browser_performance_testing.html and I've used the option to use a specific profile which is 3g but when I check the settings I still get 'No connectivity settings'
Am I missing something ?

What browser did you use?

Chrome

How to reproduce

1. configure use this gitlab.yml 

stages:
  - tests

include:
  - template: Verify/Browser-Performance.gitlab-ci.yml  

browser_performance:
  stage: tests
  URL: https://example.com
  SITESPEED_OPTIONS : "--browsertime.connectivity.profile 3g "

2. run the pipeline
3. check the settings for connectivity or if the option exist in the job logs

Log output

No response

@NOuennich NOuennich added the bug label Dec 5, 2023
@soulgalore
Copy link
Member

Hi @NOuennich thanks for creating the issue. GitLab using Docker containers right for the CI? To get that to work the actual server needssudo modprobe ifb numifbs=1 and then the container needs to run with –cap-add=NET_ADMIN to be able to change the connectivity.

There are some documentation here:
https://www.sitespeed.io/documentation/sitespeed.io/connectivity/#throttle

@NOuennich
Copy link
Author

NOuennich commented Dec 5, 2023

I'm using the sitespeed.io container https://hub.docker.com/r/sitespeedio/sitespeed.io/ does it also need these additional steps ? I thought it's simply handled with the SITESPEED_OPTIONS in this case

@soulgalore
Copy link
Member

The actual physical server at GitLab needs to run sudo modprobe ifb numifbs=1 so you need to ask their support and then the container needs to run with –cap-add=NET_ADMIN to give the container rights to change the connectivity, you need to ask the GitLab support how that is setup today.

@NOuennich
Copy link
Author

Okey, thank you for your guidance.

@soulgalore
Copy link
Member

Closing, please let me know if you need any more info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants