ostree

Commit Graph

Author	SHA1	Message	Date
Simon McVittie	9d94fc40c8	Make corrupt-repo-ref.js executable Debian's Lintian packaging consistency check complains that it isn't executable but has a #! line. In fact it's reasonable to run this script directly, so make it executable, and put it in a _scripts variable so it will be installed executable. Closes: #652 Approved by: cgwalters	2017-01-19 13:54:59 +00:00
Giuseppe Scrivano	49de180191	corrupt-repo-ref.js: more aggressive file corruption changing only a byte may not generate a corrupted file, so play very safe and change 10 bytes. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>	2014-10-22 20:02:06 +02:00
Colin Walters	3802a0679b	tests/pull-corruption: Ensure we corrupt an object to be pulled This test had some nondeterminism because we chose a random object to corrupt, but because there were multiple commits, it was possible that we chose an object that was not being pulled. Fix this by writing some custom GJS code to find an explicitly random object that exists in a given ref, an change a random byte offset. This adds a lot more randomness to the testing too.	2014-01-19 13:19:10 -05:00

Author

SHA1

Message

Date

Simon McVittie

9d94fc40c8

Make corrupt-repo-ref.js executable

Debian's Lintian packaging consistency check complains that it isn't
executable but has a #! line. In fact it's reasonable to run this
script directly, so make it executable, and put it in a _scripts
variable so it will be installed executable.

Closes: #652
Approved by: cgwalters

2017-01-19 13:54:59 +00:00

Giuseppe Scrivano

49de180191

corrupt-repo-ref.js: more aggressive file corruption

changing only a byte may not generate a corrupted file, so play very
safe and change 10 bytes.

Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>

2014-10-22 20:02:06 +02:00

Colin Walters

3802a0679b

tests/pull-corruption: Ensure we corrupt an object to be pulled

This test had some nondeterminism because we chose a random
object to corrupt, but because there were multiple commits, it
was possible that we chose an object that was not being pulled.

Fix this by writing some custom GJS code to find an explicitly random
object that exists in a given ref, an change a random byte offset.
This adds a lot more randomness to the testing too.

2014-01-19 13:19:10 -05:00

3 Commits