Skip to contentSkip to conversation

local.conf.sample.extended: Document how to limit parallel fetch tasks

PATCH In review Richard Purdie 2 participants 2 messages Feb 19, 2020

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 local.conf.sample.extended: Document how to limit parallel fetch tasks

[YOCTO #13235]

---
 meta/conf/local.conf.sample.extended | 8 ++++++++
 1 file changed, 8 insertions(+)
meta/conf/local.conf.sample.extended +8 -0
index fcf4a9b7c1a..443b4e83f9a 100644
@@ -23,6 +23,14 @@
 #
 # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
 # be appropriate for example.
+#
+# Some users are behind firewalls or use servers where the number of parallel connections
+# is limited. In such cases you can limit the number of fetch tasks which run in parallel by
+# setting the option below, in this case limiting to a maximum of 4 fetch tasks in parallel:
+#
+#do_fetch[number_threads] = "4"
+#
+
 
 #DISTRO_FEATURES = "alsa bluetooth ext2 irda ipv4 ipv6 pcmcia usbgadget usbhost wifi nfs zeroconf pci"
 
Signature · 1 line
2.25.0
#1 lore raw

✗ patchtest: failure for local.conf.sample.extended: Document how to limit parallel fetch tasks (rev2)

== Series Details ==

Series: local.conf.sample.extended: Document how to limit parallel fetch tasks (rev2)
Revision: 2
URL : https://patchwork.openembedded.org/series/22768/
State : failure

== Summary ==

Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:

* Issue Series does not apply on top of target branch [test_series_merge_on_head]
Suggested fix Rebase your series on top of targeted branch
Targeted branch master (currently at 8f29d82202)

If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).

---

Guidelines:     https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite:     http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe