monotone on Debian

monotone on Debian Commit Details

Date:2015-11-15 18:53:11 (2 years 1 month ago)
Author:Markus Wanner
Branch:org.debian.monotone
Commit:98fefd4007588d60f3762e023838508758ef0200
Parents: 1d4120a334276bd506a5b0106ab8ccb07f588342
Message:Change patch 51-sigpipe-test.diff a bit and finalize 1.1-7.

Changes:
Mchangelog (1 diff)
Mpatches/51-sigpipe-test.diff (4 diffs)

File differences

changelog
1
2
3
4
5
6
7
18
29
310
monotone (1.1-7) unstable; urgency=medium
* Modify patch 51-sigpipe-test.diff: increase bytes written to 1M to
increase chances to overflow the pipe buffer even further.
-- Markus Wanner <markus@bluegap.ch> Sun, 15 Nov 2015 18:14:19 +0100
monotone (1.1-6) unstable; urgency=medium
* Patch Makefile.am to not rebuild NLS (i.e. pot and po files) so as
patches/51-sigpipe-test.diff
11
2
2
33
44
55
66
77
88
9
9
1010
1111
1212
......
1515
1616
1717
18
18
1919
2020
2121
2222
23
23
2424
2525
2626
......
2828
2929
3030
31
31
3232
3333
3434
......
3737
3838
3939
40
40
4141
4242
4343
Description: Attempt to fix 'log_quits_on_SIGPIPE' failure on powerpc
Double the number of commits in preparation for the SIGPIPE test, so
Quatruple the number of commits in preparation for the SIGPIPE test, so
we're not just writing (somewhere above) 256K but 512K.
.
This is a somewhat desperate but conservative attempt at fixing a
buildd issue that's hard to reproduce.
Bug-Debian: https://bugs.debian.org/797386
Forwarded: no
Last-Update: 2015-09-18
Last-Update: 2015-11-15
--- a/test/func/log_quits_on_SIGPIPE/__driver__.lua
+++ b/test/func/log_quits_on_SIGPIPE/__driver__.lua
-- out how much buffer space the kernel provides, so we resort to
-- writing a ridiculous amount of data. Typical pipe capacities are
--- 4K and 64K, so "ridiculous" in this case is "approximately 256K."
+-- 4K and 64K, so "ridiculous" in this case is "approximately 512K."
+-- 4K and 64K, so "ridiculous" in this case is "approximately 1M."
--
-- We would like to make that data realistic -- typical commits to the
-- monotone repository have between 100 and 200 characters of commit
--- log -- but in order to get the ridiculous 256K, we would need
+-- log -- but in order to get the ridiculous 512K, we would need
+-- log -- but in order to get the ridiculous 1M, we would need
-- several thousand commits, which would take too long to execute.
--- So instead we make four commits each with 64K commit messages.
--- (There is a temptation to make it sixteen; I can imagine someone
--- But the time this test takes is proportional to the number of
--- commits, so I won't. I tried having a bigger log message but that
--- crashed "mtn commit".)
+-- So instead we make eight commits each with 64K commit messages.
+-- So instead we make 16 commits each with 64K commit messages.
--
-- The following 1024-byte block of nonsense is courtesy of the Eater
-- of Meaning.
mtn_setup()
addfile("file", "fnord")
-for i = 1,4 do
+for i = 1,8 do
+for i = 1,16 do
writefile("file", "commit "..tonumber(i).."\n")
commit(nil, message)
end

Archive Download the corresponding diff file

Quick Links:     www.monotone.ca    -     Downloads    -     Documentation    -     Wiki    -     Code Forge    -     Build Status