Searched refs:nasty (Results 1 – 25 of 70) sorted by relevance
123
2 > If you want some real nasty tests:
23 and nasty bugs.
34 Long term, all of the code that depends on the nasty features in the
81 C functions directly from Java without using the nasty/slow/gross JNI
6 ; PR6627 - This whole nasty sequence should be flattened down to a single
774 Predicate<? super Integer> nasty = Predicates.not(Predicates.and( in testCascadingSerialization() local780 assertEvalsToFalse(nasty); in testCascadingSerialization()783 SerializableTester.reserializeAndAssert(nasty); in testCascadingSerialization()
28 ; PR6627 - This whole nasty sequence should be flattened down to a single
44 * to do my version of the whole nasty INDENT/DEDENT issue just so I49 * The lexical rules for python are particularly nasty and it took me
126 # Put the nasty error message in config.log where it belongs
157 def nasty(): function162 self.assertRaises(ValueError, self.f.writelines, nasty())
19 * use those to be sure nothing nasty will happen if
20 * use those to be sure nothing nasty will happen if
179 -- the nasty division-by-1 cases373 -- some nasty division-by-1 cases [some similar above]
343 -- the nasty division-by-1 cases
320 -- the nasty division-by-1 cases
14 * use those to be sure nothing nasty will happen if
129 # Put the nasty error message in config.log where it belongs
45 weakref callback or __del__ method does something nasty on purpose: as52 shows how innocent it can be, and also how nasty. Variants of the three
108 someone reuses that field id, with nasty consequences.
83 been the cause of all the nasty connection refused errors in random
176 # Put the nasty error message in config.log where it belongs
375 One very nasty problem with ``select``: if somewhere in those input lists of376 sockets is one which has died a nasty death, the ``select`` will fail. You then