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

Let's do the CI branch again #1017

Closed
8 tasks done
gnn opened this issue Nov 1, 2022 · 14 comments
Closed
8 tasks done

Let's do the CI branch again #1017

gnn opened this issue Nov 1, 2022 · 14 comments

Comments

@gnn
Copy link
Collaborator

gnn commented Nov 1, 2022

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:

  • @IlkaCu merges her pending changes into dev
  • @gnn creates the new CI
  • @AmeliaNadal merges her pending changes into the new CI
  • @khelfen merges his pending changes into the new CI
  • @nailend & @birgits merges their pending changes into the new CI
  • @ClaraBuettner merge their pending changes into the new CI
  • the new CI gets started on one of the newly rented servers
  • the value of max_connections is checked using a command mentioned in a comment of issue #799

Please tick your box once your done with your TODO. And maybe ping the person responsible for your successor TODO via Element.

@gnn
Copy link
Collaborator Author

gnn commented Nov 1, 2022

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 continuous-integration/run-everything-2022-11-01.

@nesnoj
Copy link
Member

nesnoj commented Nov 1, 2022

@AmeliaNadal ping!

@nailend
Copy link
Contributor

nailend commented Nov 1, 2022

@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

@ClaraBuettner
Copy link
Contributor

@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.

@khelfen
Copy link
Contributor

khelfen commented Nov 1, 2022

I'm done as well @ClaraBuettner

@ClaraBuettner
Copy link
Contributor

I'm done as well @nailend

@gnn
Copy link
Collaborator Author

gnn commented Nov 1, 2022

Running.

SELECT name, setting, short_desc, vartype, max_val, boot_val, reset_val, pending_restart
FROM pg_settings
WHERE name = 'max_connections';

outputs:

name setting short_desc vartype max_val boot_val reset_val pending_restart
max_connections 2048 Sets the maximum number of concurrent connections. integer 262143 100 2048 f

@nesnoj
Copy link
Member

nesnoj commented Nov 2, 2022

osm.to-postgres in 2h20m ?? Woohoo! 🏎️

@nesnoj
Copy link
Member

nesnoj commented Nov 4, 2022

FATAL: sorry, too many clients already o_O

@ClaraBuettner
Copy link
Contributor

ClaraBuettner commented Nov 10, 2022

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.

@nesnoj
Copy link
Member

nesnoj commented Nov 10, 2022

I'm done too.
@IlkaCu my load area branch #1020 already contains your branch features/#1001-desaggregate-industry-demands so if you don't have any further local changes, you can skip this one.

@nesnoj
Copy link
Member

nesnoj commented Nov 10, 2022

@ClaraBuettner is your recent manual quickfix for these lines required again?

@ClaraBuettner
Copy link
Contributor

ClaraBuettner commented Nov 10, 2022

@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.
Done.

@nesnoj
Copy link
Member

nesnoj commented Nov 10, 2022

👾 👾 👾 Launched 👾 👾 👾

@nesnoj nesnoj closed this as completed Dec 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants