PR# 19287 Every compiled failed with bad error message after upgrading from 14.05
Problem Report Summary
Submitter: uwindl
Category: EiffelStudio
Priority: Low
Date: 2016/11/09
Class: Bug
Severity: Serious
Number: 19287
Release: 16.05
Confidential: No
Status: Open
Responsible: alexk_es
Environment: Windows 7 (64 bit)
Synopsis: Every compiled failed with bad error message after upgrading from 14.05
Description
After a long break I upgraded Eiffel Studio from 14.05 to 16.05 by first uninstalling the old version, then installing the current version. To my surprise I could neither open an old project, an new sample project, not could I create a new project. The error message was always the same: Whey trying to compile, a message popped up, saying some directory could not be created. However the directory complained about had always been created! Here is an example how the directory looked like (some German messages): --- c:\Users\Ulrich Windl\Documents\Eiffel User Files\16.05\projects\test_project>dir /S Datenträger in Laufwerk C: ist Windows Volumeseriennummer: 42BC-2012 Verzeichnis von c:\Users\Ulrich Windl\Documents\Eiffel User Files\16.05\projects\test_project 09.11.2016 08:03 <DIR> . 09.11.2016 08:03 <DIR> .. 09.11.2016 08:03 316 application.e 09.11.2016 08:03 <DIR> EIFGENs 09.11.2016 08:03 1.111 test_project.ecf 2 Datei(en), 1.427 Bytes Verzeichnis von c:\Users\Ulrich Windl\Documents\Eiffel User Files\16.05\projects\test_project\EIFGENs 09.11.2016 08:03 <DIR> . 09.11.2016 08:03 <DIR> .. 09.11.2016 08:03 <DIR> test_project 0 Datei(en), 0 Bytes Verzeichnis von c:\Users\Ulrich Windl\Documents\Eiffel User Files\16.05\projects\test_project\EIFGENs\test_project 09.11.2016 08:03 <DIR> . 09.11.2016 08:03 <DIR> .. 09.11.2016 08:03 <DIR> COMP 09.11.2016 08:03 <DIR> F_code 09.11.2016 08:03 <DIR> Partials 09.11.2016 08:03 <DIR> W_code 0 Datei(en), 0 Bytes Verzeichnis von c:\Users\Ulrich Windl\Documents\Eiffel User Files\16.05\projects\test_project\EIFGENs\test_project\COMP 09.11.2016 08:03 <DIR> . 09.11.2016 08:03 <DIR> .. 0 Datei(en), 0 Bytes Verzeichnis von c:\Users\Ulrich Windl\Documents\Eiffel User Files\16.05\projects\test_project\EIFGENs\test_project\F_code 09.11.2016 08:03 <DIR> . 09.11.2016 08:03 <DIR> .. 0 Datei(en), 0 Bytes Verzeichnis von c:\Users\Ulrich Windl\Documents\Eiffel User Files\16.05\projects\test_project\EIFGENs\test_project\Partials 09.11.2016 08:03 <DIR> . 09.11.2016 08:03 <DIR> .. 0 Datei(en), 0 Bytes Verzeichnis von c:\Users\Ulrich Windl\Documents\Eiffel User Files\16.05\projects\test_project\EIFGENs\test_project\W_code 09.11.2016 08:03 <DIR> . 09.11.2016 08:03 <DIR> .. 0 Datei(en), 0 Bytes Anzahl der angezeigten Dateien: 2 Datei(en), 1.427 Bytes 20 Verzeichnis(se), 183.583.023.104 Bytes frei --- Then I tried precompiling the libraries (actually all of them). Still when having finished that (EiffelStudio was still open), I could not create a new project (actually the example from above is the attempt). So I closed Estudio. Now when I finally managed to report this problem, I reopened estudio, and suddenly the project could be compiled!
To Reproduce
Not exactly sure what triggers the problem.
Problem Report Interactions
I have discovered another variant of this problem: When trying to compile finalized code, a pop-up says it couldn't create the F-Code directory (see screen shot). While the pop-up was still open, Windows explorer saw the F-Code directory already (see screen shot)! To add more surprise to this problem: When I used "Alt+F8: Find added classes and recompile" it worked, and after that compiling the finalized system also worked! It looks very much like an obscure bug to me; at least the error message pop-up is not telling the truth. Reliable software should not lie! I'd also wish there were some event log of EiffelStudio to help debugging this.
I had more strange effects: Sometimes a simple project failed to compile, missing the precompiled library, and in the next attempt, it worked. Could it be due to my working directory having a blank inside? I'll attach two screen shots to show the strange effects.
Sorry you had this experience. Unfortunately this is something we never encountered and I'm not sure what could have triggered it. One possibility would be that between the two sessions EiffelStudio was not running under the same credentials, but very unlikely from what you are describing. Let us know if this happens again