The Good News and The Bad News ... !!!

Anonymous
Topic 12482

Thanks for the report.

We invented a syntax check that looks at the temp files before processing them to reduce the number of uploads of broken results. It may either be too paranoid or there is another bug in our code.

Thanks for participating in this alpha test!

BM

Bernd Machenschalk
Bernd Machenschalk
Joined: 15 Oct 04
Posts: 2,684
Credit: 25,950,161
RAC: 34,820

The Good News and The Bad News ... !!!

I just managed to reproduce the problem on one of my machines, so it's most likely a bug in our code (or maybe the M$ libs as this happens on Windows only). Will require another round of Apps then (sic!).

BM

BM

Bruce Allen
Bruce Allen
Joined: 15 Oct 04
Posts: 958
Credit: 170,849,008
RAC: 0

The error message in the

The error message in the first post is extremely useful to us -- this is a *reproducable* bug in our analysis code, which only appears under Windows and not under Linux or Mac. Two people are currently (as I type) working on this.

So please don't give up on E@H. While you may be losing a few credits, you are helping us to track down and fix things in the science part of the code, which is extremely valuable to us.

Cheers,
Bruce

Bernd Machenschalk
Bernd Machenschalk
Joined: 15 Oct 04
Posts: 2,684
Credit: 25,950,161
RAC: 34,820

> It has, so far taken about

> It has, so far taken about 6hours CPU time and is just over 80% done. Would
> these timings seem OK? ...I thought it seemed a bit long

Sounds quite ok to me. Modern machines only running E@H are meant to deliver 2-3 WUs per day, so 8-12h looks quite normal.

BM

BM

Bernd Machenschalk
Bernd Machenschalk
Joined: 15 Oct 04
Posts: 2,684
Credit: 25,950,161
RAC: 34,820

Poor Boy, Of course we sort

Poor Boy,

Of course we sort out the bugs and problems of our Apps that happen all the time before putting them on the server for the larger public. So the bugs that remain to our test users are ones that occur only on certain types of machines or with certain data.

The scheduler we set up prefers to send work to you according to the files you already have to possibly avoid downloading new large data chunks. However this also means that the workunits you get are similar to the ones you already have crunched.

These two facts lead to the effect you are seing now: having stumbled over a data-driven bug you will likely get another Result that shows the same problem. The way to avoid this would be to reset the project, causing a new download of a (most likey) different data set.

However we are very glad that this problem showed up, it is reproducable and I myself and some other people around me too are working hard to solve it, so that the users (and of course our results) are not affected by it in the public case.

At least, that's what testing is for.

Thanks a lot for your cooperation!

BM

BM

Bernd Machenschalk
Bernd Machenschalk
Joined: 15 Oct 04
Posts: 2,684
Credit: 25,950,161
RAC: 34,820

We have just found the bug in

We have just found the bug in the code and are about building new apps now. Shouldn't take too long...

BM

BM

Bernd Machenschalk
Bernd Machenschalk
Joined: 15 Oct 04
Posts: 2,684
Credit: 25,950,161
RAC: 34,820

> We have just found the bug

Message 2181 in response to message 2180

> We have just found the bug in the code and are about building new apps now.
> Shouldn't take too long...

Out now.

BM

BM

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.