On Sun, Jan 10, 2016 at 8:42 PM, Rene Rivera wrote:

On Sat, Jan 9, 2016 at 9:01 PM, Edward Diener wrote:

...

Trying to open the regression test results for 'develop' page gives:

"Error extracting file: Error code 3 - A severe error in the zipfile format was detected."

This has happened numerous times before. Can this be fixed, not only now but permanently ? Surely there must be some way of determining why the zipfile format has a severe error and preventing this in the future.

Every time I try and replicate this it works (and temporarily fixes the problem as a side effect). So it's been, so far, impossible to determine the cause of the problems.

PS. Although, one time it was caused by ultra large results (from long logs), IIRC. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

On Mon, Jan 11, 2016 at 5:03 AM, Jürgen Hunold wrote:

Hi Rene,

Am Sunday 10 January 2016, 20:43:38 schrieb Rene Rivera:

...

...

Every time I try and replicate this it works (and temporarily fixes the problem as a side effect). So it's been, so far, impossible to determine the cause of the problems.

PS. Although, one time it was caused by ultra large results (from long logs), IIRC

This might be coincidence, but AFAIK the test matrix went out of business shortly after Hana (and then Dll) were added. And I'm seeing quite a lot of (unexpected) errors from Hana here.

It looks like we've passed the > 4GiB limit on the report zips. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

On Mon, Jan 11, 2016 at 11:18 AM, Steven Watanabe wrote:

AMDG

...

On Mon, Jan 11, 2016 at 5:03 AM, Jürgen Hunold wrote:

...

Hi Rene,

Am Sunday 10 January 2016, 20:43:38 schrieb Rene Rivera:

...

...

Every time I try and replicate this it works (and temporarily fixes

On 01/11/2016 08:44 AM, Rene Rivera wrote: the

...

...

...

...

problem as a side effect). So it's been, so far, impossible to determine the cause of the problems.

PS. Although, one time it was caused by ultra large results (from long logs), IIRC

This might be coincidence, but AFAIK the test matrix went out of business shortly after Hana (and then Dll) were added. And I'm seeing quite a lot of (unexpected) errors from Hana here.

It looks like we've passed the > 4GiB limit on the report zips.

That would be on me. I didn't implement zip64 extensions, since the total archive size was around 200 MB back then.

Yeah.. Just found that code :-( Are you going to implement it? Or should I switch to something else? (like Python) -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

AMDG Rene, I'm sure I wrote some tests for the boost_report program, but I don't see them in the repository. Do you know what happened to them? In Christ, Steven Watanabe

Jürgen Hunold writes:

Hi Rene,

Am Sunday 10 January 2016, 20:43:38 schrieb Rene Rivera:

...

...

Every time I try and replicate this it works (and temporarily fixes the problem as a side effect). So it's been, so far, impossible to determine the cause of the problems.

PS. Although, one time it was caused by ultra large results (from long logs), IIRC

This might be coincidence, but AFAIK the test matrix went out of business shortly after Hana (and then Dll) were added. And I'm seeing quite a lot of (unexpected) errors from Hana here.

Hana has a huge number of tests, and the output could be gigantic when compile-time errors happen due to compiler spew. Hana is not supposed to compile on most compilers in the test matrix; would it be possible to somehow mark failures on these compilers as expected, or to skip running the tests altogether? Would that help in any way? Louis

On Mon, Jan 11, 2016 at 3:23 PM, Steven Watanabe wrote:

AMDG

On 01/11/2016 12:04 PM, Louis Dionne wrote:

...

Hana has a huge number of tests, and the output could be gigantic when compile-time errors happen due to compiler spew. Hana is not supposed to compile on most compilers in the test matrix; would it be possible to somehow mark failures on these compilers as expected, or to skip running the tests altogether? Would that help in any way?

You can mark a compiler as unsupported in status/expected-failures-markup.xml. The tests will still be run but won't be included in the report.

You can also use the Predef check tool to avoid running the tests at all. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

On 1/11/2016 2:04 PM, Louis Dionne wrote:

Jürgen Hunold writes:

...

Hi Rene,

Am Sunday 10 January 2016, 20:43:38 schrieb Rene Rivera:

...

...

Every time I try and replicate this it works (and temporarily fixes the problem as a side effect). So it's been, so far, impossible to determine the cause of the problems.

PS. Although, one time it was caused by ultra large results (from long logs), IIRC

This might be coincidence, but AFAIK the test matrix went out of business shortly after Hana (and then Dll) were added. And I'm seeing quite a lot of (unexpected) errors from Hana here.

Hana has a huge number of tests, and the output could be gigantic when compile-time errors happen due to compiler spew. Hana is not supposed to compile on most compilers in the test matrix; would it be possible to somehow mark failures on these compilers as expected, or to skip running the tests altogether? Would that help in any way?

You can definitely skip running tests in your jam file for all the compilers which cannot handle Hana. You can use predef-require to do this or you can use the Boost build 'alias' feature.

On Mon, Jan 11, 2016 at 7:30 PM, Steven Watanabe wrote:

AMDG

On 01/09/2016 08:01 PM, Edward Diener wrote:

...

Trying to open the regression test results for 'develop' page gives:

"Error extracting file: Error code 3 - A severe error in the zipfile format was detected."

This has happened numerous times before. Can this be fixed, not only now but permanently ? Surely there must be some way of determining why the zipfile format has a severe error and preventing this in the future.

Fixed.

Many thanks.. Looks good. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail