-
Notifications
You must be signed in to change notification settings - Fork 4
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
Let's do the CI branch again #1017
Comments
Since the run hasn't been a "weekend run" for quite some time now, I took the liberty of shortening the name. The new CI branch is called |
@AmeliaNadal ping! |
@ClaraBuettner would you like to merge your stuff before me? I have to leave the office in 15 mins but would do this later when I come home. Approx. 10 pm |
Yes, we can change the order. I will do this in the description and write you when I'm done. |
I'm done as well @ClaraBuettner |
I'm done as well @nailend |
Running. SELECT name, setting, short_desc, vartype, max_val, boot_val, reset_val, pending_restart
FROM pg_settings
WHERE name = 'max_connections'; outputs:
|
|
|
We discussed about creating a new CI-branch which can run in parallel on the server in Flensburg. If you're not against, I will create a new branch from https://github.com/openego/eGon-data/tree/continuous-integration/run-everything-2022-11-01 , to avoid that all features which are already in that don't have to be merged again. I just created and pushed the branch https://github.com/openego/eGon-data/tree/continuous-integration/run-everything-2022-11-10 We would like to start the run on Friday. In order to not run into merge conflicts, I suggest the following order:
If I forgot anyone, please let me know. |
I'm done too. |
@ClaraBuettner is your recent manual quickfix for these lines required again? |
Yes, I think is is needed again. I will add this on a branch an merge it into the newest CI. |
👾 👾 👾 Launched 👾 👾 👾 |
Due to the recent issues with the last, newly created
continuous-integration/run-everything-over-the-weekend-2022-10-10
branch, we're creating a a new CI branch. Since the last one is rather recent the transition to the new one will not proceed according to the regular workflow, but will instead follow the TODOs below:dev
max_connections
is checked using a command mentioned in a comment of issue #799Please tick your box once your done with your TODO. And maybe ping the person responsible for your successor TODO via Element.
The text was updated successfully, but these errors were encountered: