-
Notifications
You must be signed in to change notification settings - Fork 1
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
Pull xvfb code from vscode CI #6
Comments
Thanks for keeping an eye on the NSLS-II kitchen, @klauer! We are already doing this: profile-collection-ci/azure-linux.yml Lines 123 to 126 in 726ebc6
However, I am not quite happy I have to do it in the same step as the test itself. I'd rather prefer to start it along with profile-collection-ci/azure-linux.yml Line 86 in 726ebc6
but it fails to propagate to the next steps. Maybe I just need to set the |
@mrakitin I see 😄 (I think @hhslepicka could benefit from what you decide on, so I'll ping him here.) |
You just need to set the environment for the display when you run the tests... The export there will never work as the steps for a Azure CI job are executed in a separated shell instance. |
Thanks @hhslepicka! Yes, I was burned by that at some point, but it makes sense. I'll test it using your example. |
@mrakitin it is working fine for me for a couple of months now... |
Neat, thanks for the suggestions, @hhslepicka! I think we are a bit far from clicking in CI, but medium- to long-term we will need that. A side note: |
@hhslepicka, are you still using |
@mrakitin I still use that for PyDM but for some internal tasks (Youtube Streaming) I switched to using |
Thanks, @hhslepicka! I'll post the link you previously shared with me regarding the Youtube streaming - https://github.com/hhslepicka/docker-streaming (so I don't forget). Do you mind sharing how you use |
@mrakitin here is basically what I do:
Very similar to how Herbstluftwm is used. |
Awesome, thanks! |
https://github.com/microsoft/vscode/blob/ab99fbebf87c30a65d2e1152ce63afb587160a57/build/azure-pipelines/linux/continuous-build-linux.yml#L2-L9
The text was updated successfully, but these errors were encountered: