brats: fix upgrade from postgres 13 test - #2804
Conversation
- this is necessary to get brats passing on Resolute - it's ok for it to run under BPM on all stemcell lines, since we're controlling the manifest and there will not be other copies of BPM to conflict - up the compile timeout a little, hopefully 30 minutes is enough even when when CI is overloaded
Postgres 10 does not compile on Resolute. This test was pulling in a version of postgres 13 that itself pulled in Postgres 10 for ugprade purposes. Switching to a version where postgres 13 does not include postgres 10.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
WalkthroughThe default inner BOSH startup timeout increased from 25 minutes to 30 minutes. The PostgreSQL 13 manifest now uses the Merge Risk: ⚪ Minimal · up to This localized test and manifest update changes which PostgreSQL version is used for upgrade coverage without introducing an actionable merge-blocking risk. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
|
This upcoming test addition might be worth cribbing from |
2 participants
What is this change about?
Postgres 10 does not compile on Resolute. This test was pulling in a version of postgres 13 that itself pulled in Postgres 10 for upgrade purposes. Switching to a version where postgres 13 does not include postgres 10.
What tests have you run against this PR?
I've manually validated the steps this test goes through using the manifests from the repo.
Does this PR introduce a breaking change?
No