Opened 7 years ago

Closed 7 years ago

#2003 closed defect (fixed)

Prevent different branch builds from colliding

Reported by: robe Owned by: robe
Priority: medium Milestone: Management 2.0
Component: buildbots Version:
Keywords: Cc:

Description

If changes are made to both PostGIS 2.0/2.1 at the same time, there is a high likeliness during regress that the two jobs collide with each other since they are trying to initialize the same clusters.

The init and start/stop should be revised to take as input postgis version number so that we can create data clusters specifically for said version to prevent job collision.

I think similar issue with the pgis_regress temp folder or whatever it's called. This will become more important as we test more permutations of libraries.

Change History (2)

comment:1 Changed 7 years ago by robe

Summary: Revise buildbots to initialize different pg clusters on different portsPrevent different branch builds from colliding

strk I revised to have initialize clusters based on port ad have the different pranches use different ports, however there is still the issue of the pgis_reg folder how do I control that to have each branch use a different one.

How do I override this again. I think that is why prmasey's harmless commits to both 2.0 and 2.1 caused bizarre regression failures. Sorry about that pramsey, if Debbie yelled at you :).

comment:2 Changed 7 years ago by robe

Resolution: fixed
Status: newclosed

Nevermind. Figured it out from looking at regress script. So I set

export PGIS_REG_TMPDIR=${WORKSPACE}/tmp/${POSTGIS_MAJOR_VERSION}_${POSTGIS_MINOR_VERSION}_pg${PG_VER}w${OS_BUILD}

before regress and that seems to work and should prevent each branch run from colliding into each other.

Note: See TracTickets for help on using tickets.