Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
At the moment build tests run with a concurrency > 30. This can cause issues with diskspace on the test bots. See #3086179-8: Fix spurious failures attempting to allocate a web server in the build tests
Proposed resolution
- Consider limiting concurrency ala nightwatch
- Consider not copying VCS files to the test build (or maybe make this optional)
Remaining tasks
Decide approach
User interface changes
None
API changes
None
Data model changes
None
Release notes snippet
N/a
Comment | File | Size | Author |
---|---|---|---|
#5 | 3086308-5.patch | 434 bytes | alexpott |
#2 | 3086308-2-con-15.patch | 2.84 KB | alexpott |
| |||
#2 | 3086308-2-con-5.patch | 2.83 KB | alexpott |
| |||
#2 | 3086308-2.patch | 2.76 KB | alexpott |
|
Comments
Comment #2
alexpottComment #4
heddnOne item of note about git clones. Those things are all shallow clones. So they shouldn't be using all that much space when compared with a tarball download or other means of getting various versions of drupal installed in a repeatable manner.
That said, #3082230: [meta] Convert some tests to Build tests demonstrates a way to get around the shallow clone. I guess my point is, whatever we decide on, we should error on the side of less concurrency as disk space will get utilized by these build tests.
Comment #5
alexpottI guess we can see that 15 passes and is the same as JS testing so let's start there. If this needs to be adjusted we can do that. But the patch shows that at the current levels the concurrency is too high.
Comment #6
heddnSeems reasonable to me. We can always adjust further later on.
Comment #10
catchCommitted/pushed to 9.0.x, 8.9.x, and 8.8.x, thanks!