You can do one of 2 things (or both):

a. BAIL_OUT, or

b. check $@ outside of the eval with an ok.

In some case, you may actually want it to time out.

However, that you're timing tells me that what is timing out should probably mocked. It also tells me that you may want to have a more robust wrapper around whatever it is that is timing out - because it may time out when run for real. Throwing Exception::Class is always good - and you can even test that you handle things like timeouts properly using Test::Exception.

A quick and easy way to mock whatever it is that is timing out is to use a typeglob:

# mock returned data
*Package::method = sub { return 'some expected data' };
[download]

# mock a timeout, but wrap this in an eval/alarm
my $a_long_time = 900; # seconds
*Package::method = sub { sleep $a_long_time; return; };
[download]

# mock a die from timeout, but wrap this in an eval/alarm
*Package::method = sub { die "Timed out!\n"; };
[download]

# mock a timeout exception, but wrap this in an eval/alarm
*Package::method = sub { throw My::Exception::Timeout; };
[download]