If offline, warn only once, but verbose

[Google Code Exporter]

If the user is offline or has no access to the repository, then make sure that 
the SatSolverUpdateTool only fails once. It should also print out a warning 
saying that it couldn't connect to the repo.
Assigned that to you Felix, since this was originally your file.
If you want, I can write that part, too.
(In the latter case, could you please word the "Warning!"-paragraph?)

Original issue reported on code.google.com by [e-mail] on 5 Jul 2012 at 6:32

[Google Code Exporter]

I have no idea how to implement that, since JUnit calls the tests separately.

A verbose warning could be:

Failed to connect to our repository to update the tests. This means that
a) you are offline or
b) we broke the repository.

If you are 100% certain that you are online and the problem still persists, 
file a ticket here: 
https://code.google.com/p/prog2tests/issues/entry?template=support
In that case, please include the following information: ***DEBUG_INFO***

The tests will still work, but you won't get updates until this issue is 
resolved, meaning that you will miss out on new tests or bugfixes.

Original comment by [e-mail] on 5 Jul 2012 at 6:40

• Changed state: Accepted

[Google Code Exporter]

I'll add it.

Original comment by [e-mail] on 5 Jul 2012 at 6:41

• Changed state: Started

[Google Code Exporter]

How about this message:

___________
Encountered difficulties connecting to repository.
WARNING: All further attempts to connect with the repository are SUPPRESSED, 
and your tests may be out-of-date.
Please make sure that you reconnect soon and update/verify your tests.
___________

Original comment by [e-mail] on 6 Jul 2012 at 11:50

[Google Code Exporter]

OK, but you should include the file name.

Original comment by [e-mail] on 6 Jul 2012 at 12:57

• Changed title: If offline, warn only once, but verbose

[Google Code Exporter]

Better?

___________
Encountered difficulties connecting to file "/some/file" of our repository.
Warning: All further attempts to connect with the repository are SUPPRESSED, 
and your tests may be out-of-date.
Please make sure that you reconnect soon and update/verify your tests.
___________

Original comment by [e-mail] on 6 Jul 2012 at 3:01

[Google Code Exporter]

New version published
=> Ticket closed

Original comment by [e-mail] on 6 Jul 2012 at 3:29

• Changed state: Fixed