Skip to content

Conversation

@cjwatson
Copy link
Contributor

https://bugs.debian.org/1103066 reported test failures on Debian's i386 architecture. After some digging I found that tests were hitting ENOMEM depending on which other tests had been run previously, suggesting test isolation problems; i386 has a more limited address space than most other architectures so is more likely to run into this sort of thing. Forcing thread pools to be shut down between tests seems to avoid this problem.

cjwatson and others added 2 commits May 21, 2025 18:23
https://bugs.debian.org/1103066 reported test failures on Debian's i386
architecture.  After some digging I found that tests were hitting
`ENOMEM` depending on which other tests had been run previously,
suggesting test isolation problems; i386 has a more limited address
space than most other architectures so is more likely to run into this
sort of thing.  Forcing thread pools to be shut down between tests seems
to avoid this problem.
@sijis sijis force-pushed the tests-shut-down-thread-pools branch from 5c5d4d5 to ed22a0c Compare May 21, 2025 23:23
@sijis sijis merged commit da7f5e9 into errbotio:master May 21, 2025
5 checks passed
@sijis
Copy link
Contributor

sijis commented May 21, 2025

@cjwatson thank you!

@cjwatson cjwatson deleted the tests-shut-down-thread-pools branch May 22, 2025 09:01
kayman-mk pushed a commit to Hapag-Lloyd/errbot that referenced this pull request Jul 2, 2025
* Close and join thread pools between tests

https://bugs.debian.org/1103066 reported test failures on Debian's i386
architecture.  After some digging I found that tests were hitting
`ENOMEM` depending on which other tests had been run previously,
suggesting test isolation problems; i386 has a more limited address
space than most other architectures so is more likely to run into this
sort of thing.  Forcing thread pools to be shut down between tests seems
to avoid this problem.

* docs: add info to CHANGES

---------

Co-authored-by: Sijis Aviles <sijis.aviles@gmail.com>
(cherry picked from commit da7f5e9)
kayman-mk pushed a commit to Hapag-Lloyd/errbot that referenced this pull request Jul 2, 2025
* Close and join thread pools between tests

https://bugs.debian.org/1103066 reported test failures on Debian's i386
architecture.  After some digging I found that tests were hitting
`ENOMEM` depending on which other tests had been run previously,
suggesting test isolation problems; i386 has a more limited address
space than most other architectures so is more likely to run into this
sort of thing.  Forcing thread pools to be shut down between tests seems
to avoid this problem.

* docs: add info to CHANGES

---------

Co-authored-by: Sijis Aviles <sijis.aviles@gmail.com>
(cherry picked from commit da7f5e9)
kayman-mk pushed a commit to Hapag-Lloyd/errbot that referenced this pull request Jul 2, 2025
* Close and join thread pools between tests

https://bugs.debian.org/1103066 reported test failures on Debian's i386
architecture.  After some digging I found that tests were hitting
`ENOMEM` depending on which other tests had been run previously,
suggesting test isolation problems; i386 has a more limited address
space than most other architectures so is more likely to run into this
sort of thing.  Forcing thread pools to be shut down between tests seems
to avoid this problem.

* docs: add info to CHANGES

---------

Co-authored-by: Sijis Aviles <sijis.aviles@gmail.com>
(cherry picked from commit da7f5e9)
kayman-mk pushed a commit to Hapag-Lloyd/errbot that referenced this pull request Jul 2, 2025
* Close and join thread pools between tests

https://bugs.debian.org/1103066 reported test failures on Debian's i386
architecture.  After some digging I found that tests were hitting
`ENOMEM` depending on which other tests had been run previously,
suggesting test isolation problems; i386 has a more limited address
space than most other architectures so is more likely to run into this
sort of thing.  Forcing thread pools to be shut down between tests seems
to avoid this problem.

* docs: add info to CHANGES

---------

Co-authored-by: Sijis Aviles <sijis.aviles@gmail.com>
(cherry picked from commit da7f5e9)
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

Successfully merging this pull request may close these issues.

3 participants