After I have managed to set up my environment for Jenkins development, I
started to implement a test case for the problem in
test/hudson/tasks/ArtifactArchiverTest.java. I have attached the file. The
test seems to work fine, but I am unhappy with some details. Maybe you have
some hints for me?


   1. The test runs very long. This is not very surprising, as it first has
   to generate a 8GB file, then copy it, and finally check it. However, I
   think some speedup should be possible when generating the file. My idea was
   to generate a large file with arbitrary data and to only put in some
   generated data for comparison at the files very end. To quickly generate
   such a file, the recommended way is to create a RandomAccessFile with the
   wanted size, then seek to the required position and write the data there.
   However, in the test, I only have the "FilePath" of the file available,
   which doesn't allow me to do so. I tried to use FilePath.act (as you can
   see in the commented out code), but to no effect. What am I doing wrong?
   2. Also, it would be a good idea to check whether there is enough space
   left on the device to store the large file twice before actually executing
   the test at all. How can I do that? I didn't find any hint on that.
   3. I'm using eclipse as an IDE. I tried to execute the tests as Junit
   tests, but that fails due to some markers in the whole project (69 errors),
   so that it doesn't start the unit test. Are there any tricks to get rid of
   these problems, or to starte the junit tests anyway? Is eclipse still used
   by Jenkins devels, or is another IDE preferred?

Olaf

2015-03-24 13:17 GMT+01:00 Daniel Beck <[email protected]>:

>
> > You mean you are unsure about the regressions of updating ant to 1.9.4,
> or do you see other possible regressions?
>
> Yes, both in the changed Tar…Streams and the rest of Ant as used by
> Jenkins. Updating Ant seemed like the way to go and IIRC there's also a
> bunch of other classes added since we copied the classes over that are
> needed by the Streams. However I haven't investigated any further.
>
> I haven't looked further for possible problems, or performed extensive
> tests with the patched build. So this could work without any problems.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/QmTnfDlMWpE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/B2FA3874-49D9-49FA-8468-86B5BDA236E5%40beckweb.net
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAKCL2smoR7uNehMym48OUmLrVHCAFe-6t0V54njGqejMA1aPeA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: ArtifactArchiverTest.java
Description: Binary data

Reply via email to