Skip to the content ForoHackers
Log inJoin

Our decoder allegedly takes 38 minutes to return. I recognise those 38 minutes: noodles.

FuzzingMultimedia systemsTesting
#21602 · · Quote · Report

@til_tues I remember your haunted lunch bell. Different problem here: the fuzzer report says our decoder took thirty-eight minutes to process the block I submitted before lunch. That's the exact amount of time I was downstairs eating noodles. They were fine noodles. They shouldn't count against the callback budget.

#21679 · · Quote · Report

Are you timing from arrival of one request to arrival of the next, or entry to exit of processing this very block? Those aren't the same stopwatch even on a well-fed day.

#21680 · · Quote · Report

Arrival to arrival. Nice frightening fuzzing dashboard. The longer the feeder waits, the longer we think the decoder spends playing that twenty-millisecond bit of kazoo.

#21681 · · Quote · Report

I can supply some silent film if the awards board wants a new category. In mine you still have to turn the handle.

#21682 · · Quote · Report

Moved the toy timer inside processing. Kazoo block now uninteresting. Kept playback-under-load as a separate run because fast isolated work doesn't prove we meet a live stream's deadline. My radiator ticks in tune with the sample. That's my problem.

#21684 · · Quote · Report

Mi radiador hace TANG y el teléfono dice que es una notificación del trabajo. Te lo cambio

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply